Because I have decided so.
If you don't like it, please send your complaints now. It will be backward compatible though.
Where will the XML be located? Before it was located in a js/css file on the wiki being used correct? Will it be set inside Huggle3 or externally?
On Tue, Jan 22, 2013 at 9:03 AM, Petr Bena benapetr@gmail.com wrote:
Because I have decided so.
If you don't like it, please send your complaints now. It will be backward compatible though.
Huggle mailing list Huggle@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/huggle
huggle_xml.css
On Tue, Jan 22, 2013 at 3:04 PM, Samuel Damashek samuel.damashek@gmail.comwrote:
Where will the XML be located? Before it was located in a js/css file on the wiki being used correct? Will it be set inside Huggle3 or externally?
On Tue, Jan 22, 2013 at 9:03 AM, Petr Bena benapetr@gmail.com wrote:
Because I have decided so.
If you don't like it, please send your complaints now. It will be backward compatible though.
Huggle mailing list Huggle@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/huggle
-- Samuel Damashek
Developer of Fraction Simplifier, a free Google Chrome Extension. http://bit.ly/fractionsimplify
Huggle mailing list Huggle@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/huggle
Yeah, I'd prefer JSON as well.
* Easier to read/edit * Better support for different value types (arrays, booleans, strings, numbers)
Or a simplified form of JSON, YAML, which also supports inline comments (or strip comments from the JSON before parsing, like for .jshintrc in JSHint).
-- Krinkle
On Tue, Jan 22, 2013 at 9:57 AM, Platonides platonides@gmail.com wrote:
On 22/01/13 15:08, Petr Bena wrote:
huggle_xml.css
It's quite odd to store a xml with a css extension, and the wiki doesn't support good editing of xml either.
Why not use JSON, storing it on huggle.js?
Huggle mailing list Huggle@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/huggle
JSON is evil. I am already parsing it with another c# application. It's terrible, see yourlsef: https://github.com/benapetr/wikimedia-bot/blob/master/plugins/labs/labs/labs...
maybe it's good for java, I don't know, but it seems to me like a good language for serialized data, not for configuration which is different in every version
On Sat, Jan 26, 2013 at 3:11 AM, Krinkle krinklemail@gmail.com wrote:
Yeah, I'd prefer JSON as well.
- Easier to read/edit
- Better support for different value types (arrays, booleans, strings,
numbers)
Or a simplified form of JSON, YAML, which also supports inline comments (or strip comments from the JSON before parsing, like for .jshintrc in JSHint).
-- Krinkle
On Tue, Jan 22, 2013 at 9:57 AM, Platonides platonides@gmail.com wrote:
On 22/01/13 15:08, Petr Bena wrote:
huggle_xml.css
It's quite odd to store a xml with a css extension, and the wiki doesn't support good editing of xml either.
Why not use JSON, storing it on huggle.js?
Huggle mailing list Huggle@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/huggle
Huggle mailing list Huggle@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/huggle
I mean, it's cool to have it store arrays and such in different format. But what if array magically becomes a string? I can't handle so many exception there. Or, I can, but I am lazy...
The configuration of huggle is meant to be edited by humans. And JSON is stable only until someone manually start changing it. One removed quote, and whole config file is broken.
On Sat, Jan 26, 2013 at 9:02 AM, Petr Bena benapetr@gmail.com wrote:
JSON is evil. I am already parsing it with another c# application. It's terrible, see yourlsef: https://github.com/benapetr/wikimedia-bot/blob/master/plugins/labs/labs/labs...
maybe it's good for java, I don't know, but it seems to me like a good language for serialized data, not for configuration which is different in every version
On Sat, Jan 26, 2013 at 3:11 AM, Krinkle krinklemail@gmail.com wrote:
Yeah, I'd prefer JSON as well.
- Easier to read/edit
- Better support for different value types (arrays, booleans, strings,
numbers)
Or a simplified form of JSON, YAML, which also supports inline comments (or strip comments from the JSON before parsing, like for .jshintrc in JSHint).
-- Krinkle
On Tue, Jan 22, 2013 at 9:57 AM, Platonides platonides@gmail.com wrote:
On 22/01/13 15:08, Petr Bena wrote:
huggle_xml.css
It's quite odd to store a xml with a css extension, and the wiki doesn't support good editing of xml either.
Why not use JSON, storing it on huggle.js?
Huggle mailing list Huggle@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/huggle
Huggle mailing list Huggle@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/huggle
On 26/01/13 09:05, Petr Bena wrote:
I mean, it's cool to have it store arrays and such in different format. But what if array magically becomes a string? I can't handle so many exception there. Or, I can, but I am lazy...
The configuration of huggle is meant to be edited by humans. And JSON is stable only until someone manually start changing it. One removed quote, and whole config file is broken.
One slash missing in xml, and the whole xml file is broken :)
I don't know what kind of data you want to store in the config file, but I find strange that storing in JSON is much harder than in XML. What if you expected a string and now you have a list of tags?
Maybe the problem is the way you are trying to read the information.
PS: Have you seen the grammar at http://json.org/ ? You also have a list of implementations there which you could use.
nope, in xml everything is string :) also people on wiki are more familiar with xml than json
On Sat, Jan 26, 2013 at 2:23 PM, Platonides platonides@gmail.com wrote:
On 26/01/13 09:05, Petr Bena wrote:
I mean, it's cool to have it store arrays and such in different format. But what if array magically becomes a string? I can't handle so many exception there. Or, I can, but I am lazy...
The configuration of huggle is meant to be edited by humans. And JSON is stable only until someone manually start changing it. One removed quote, and whole config file is broken.
One slash missing in xml, and the whole xml file is broken :)
I don't know what kind of data you want to store in the config file, but I find strange that storing in JSON is much harder than in XML. What if you expected a string and now you have a list of tags?
Maybe the problem is the way you are trying to read the information.
PS: Have you seen the grammar at http://json.org/ ? You also have a list of implementations there which you could use.
Huggle mailing list Huggle@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/huggle
When is Huggle 3 expected?
On Sat, Jan 26, 2013 at 5:34 AM, Petr Bena benapetr@gmail.com wrote:
nope, in xml everything is string :) also people on wiki are more familiar with xml than json
On Sat, Jan 26, 2013 at 2:23 PM, Platonides platonides@gmail.com wrote:
On 26/01/13 09:05, Petr Bena wrote:
I mean, it's cool to have it store arrays and such in different format. But what if array magically becomes a string? I can't handle so many exception there. Or, I can, but I am lazy...
The configuration of huggle is meant to be edited by humans. And JSON is stable only until someone manually start changing it. One removed quote, and whole config file is broken.
One slash missing in xml, and the whole xml file is broken :)
I don't know what kind of data you want to store in the config file, but I find strange that storing in JSON is much harder than in XML. What if you expected a string and now you have a list of tags?
Maybe the problem is the way you are trying to read the information.
PS: Have you seen the grammar at http://json.org/ ? You also have a list of implementations there which you could use.
Huggle mailing list Huggle@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/huggle
Huggle mailing list Huggle@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/huggle
Easiest way to resolve conflicts is converting huggle.css to huggle_xml.css (if huggle_xml doesn't exist, then convert huggle.css) when you switch back to huggle 2x from huggle 3x you won't loose your configs
On Tue, Jan 22, 2013 at 3:03 PM, Petr Bena benapetr@gmail.com wrote:
Because I have decided so.
If you don't like it, please send your complaints now. It will be backward compatible though.