Hi.
I'm getting close to releasing JSWikiGantt extension and I'm wondering if this should go to SVN or not? And in effect should I ask for commit access to SVN or not. I have my own server so I can put my code there, but I'm not sure what are the habits with extensions.
Just to clarify what the extension is - it's basically a port of JSGantt to MediaWiki. It allows injecting Gantt diagrams as XML into articles. There's certainly a lot room for improvement (like e.g. an ability to have more then one diagram per page) and I still need to go for i18n, but that should be ready soon (I hope).
BTW are there any guidelines (or at least good examples) of i18n in JS? What I mean is - I need to use some (most) localized strings in JS and would like to use existing code (if possible) for pushing strings from PHP to JS.
I also have another extension for editing diagrams of certain type - namely calendar-diagrams for activities such as "Delegation", "Vacation", "Sick leave". From what I've read this probably shouldn't go to SVN or should it?
Oh, both extensions where written for 1.16, but I'm mostly using JS anyway so this probably shouldn't matter.
Regards, Nux.
2011/4/14 Maciej Jaros egil@wp.pl:
BTW are there any guidelines (or at least good examples) of i18n in JS? What I mean is - I need to use some (most) localized strings in JS and would like to use existing code (if possible) for pushing strings from PHP to JS.
[snip]
Oh, both extensions where written for 1.16, but I'm mostly using JS anyway so this probably shouldn't matter.
Use ResourceLoader, which handles i18n for you. ResourceLoader is new in 1.17 though, so code written with ResourceLoader will not work with 1.16 unless you go out of your way to make it dual-compatible.
See https://secure.wikimedia.org/wikipedia/mediawiki/wiki/ResourceLoader/Documen...
Roan Kattouw (Catrope)
Roan Kattouw (2011-04-14 13:30):
2011/4/14 Maciej Jarosegil@wp.pl:
BTW are there any guidelines (or at least good examples) of i18n in JS? What I mean is - I need to use some (most) localized strings in JS and would like to use existing code (if possible) for pushing strings from PHP to JS
[snip]
Oh, both extensions where written for 1.16, but I'm mostly using JS anyway so this probably shouldn't matter.
Use ResourceLoader, which handles i18n for you. ResourceLoader is new in 1.17 though, so code written with ResourceLoader will not work with 1.16 unless you go out of your way to make it dual-compatible.
See https://secure.wikimedia.org/wikipedia/mediawiki/wiki/ResourceLoader/Documen...
Sadly not an option for me. It must work on 1.16 as I cannot upgrade office wiki to 1.17 (some extensions like e.g. WYSWIG don't work there). Is there some more or less standard way to do it for 1.16?
BTW [[mw:Localisation]] is missing that info.
Regards, Nux.
Roan Kattouw (2011-04-14 13:30):
2011/4/14 Maciej Jarosegil@wp.pl:
BTW are there any guidelines (or at least good examples) of i18n in JS? What I mean is - I need to use some (most) localized strings in JS and would like to use existing code (if possible) for pushing strings from PHP to JS
[snip]
Oh, both extensions where written for 1.16, but I'm mostly using JS anyway so this probably shouldn't matter.
Use ResourceLoader, which handles i18n for you. ResourceLoader is new in 1.17 though, so code written with ResourceLoader will not work with 1.16 unless you go out of your way to make it dual-compatible.
See https://secure.wikimedia.org/wikipedia/mediawiki/wiki/ResourceLoader/Documen...
Sadly not an option for me. It must work on 1.16 as I cannot upgrade office wiki to 1.17 (some extensions like e.g. WYSWIG don't work there). Is there some more or less standard way to do it for 1.16?
BTW [[mw:Localisation]] is missing that info.
Regards, Nux.
Maciej Jaros (2011-04-14 16:03):
Roan Kattouw (2011-04-14 13:30):
2011/4/14 Maciej Jarosegil@wp.pl:
BTW are there any guidelines (or at least good examples) of i18n in JS? What I mean is - I need to use some (most) localized strings in JS and would like to use existing code (if possible) for pushing strings from PHP to JS
[snip]
Oh, both extensions where written for 1.16, but I'm mostly using JS anyway so this probably shouldn't matter.
Use ResourceLoader, which handles i18n for you. ResourceLoader is new in 1.17 though, so code written with ResourceLoader will not work with 1.16 unless you go out of your way to make it dual-compatible.
See https://secure.wikimedia.org/wikipedia/mediawiki/wiki/ResourceLoader/Documen...
Sadly not an option for me. It must work on 1.16 as I cannot upgrade office wiki to 1.17 (some extensions like e.g. WYSWIG don't work there). Is there some more or less standard way to do it for 1.16?
BTW [[mw:Localisation]] is missing that info.
Regards, Nux.
Never mind. Found it in CategoryTree if anyone would be looking for it...
Cheers, Nux.
On Thu, Apr 14, 2011 at 9:26 PM, Maciej Jaros egil@wp.pl wrote:
Hi.
I'm getting close to releasing JSWikiGantt extension and I'm wondering if this should go to SVN or not? And in effect should I ask for commit access to SVN or not. I have my own server so I can put my code there, but I'm not sure what are the habits with extensions. ...snip...
Yes, It's very nice when they are in our SVN server since you get the added benefit of code going via our Code Review system and other users can contribute when they see issues or want to improve on it.
More info about requesting commit access can be found here: http://www.mediawiki.org/wiki/Commit_access#Requesting_commit_access
wikitech-l@lists.wikimedia.org