Message: 2 Date: Fri, 01 Apr 2011 18:40:00 -0700 From: Ryan Kaldari rkaldari@wikimedia.org Subject: Re: [Wikitech-l] Focus on sister projects To: Conrad Irwin conrad.irwin@gmail.com Cc: Wikimedia developers wikitech-l@lists.wikimedia.org Message-ID: 4D967E70.2080108@wikimedia.org Content-Type: text/plain; charset=windows-1252; format=flowed
[...]
As long as we're on the subject of wiktionary, I notice that there's a lot of custom Javascript there for handling specialized editing tasks like editing glosses, managing translations, etc. It seems like some of this functionality could be improved further and developed into full-fledged extensions (making it easy for other wiktionaries to use as well). Would you have any interest in working up a couple Wiktionary project proposals for the upcoming Hackathon in Berlin?
Ryan Kaldari
This isn't just true of wiktionary. Lots of sister projects have specialized work flow tools in js. Wikinews has review related tools in js and a hack that adds a second "talk" namespace, Wikisource has the proofread page extension, but still much of there workflow is written in js, I'm sure many other projects have specialized stuff that should be in php extensions.
The issue is at the end of the day it is _significantly_ easier to write a js hack, then to manage to get a php extension written, reviewed and deployed.
-bawolff
What do you guys think would be more useful:
1. Helping sister projects write up proposals for the Berlin Hackathon 2. Creating "The Complete Idiot's Guide to Writing MediaWiki Extensions" and "The Complete Idiot's Guide to Writing MediaWiki Gadgets (in jQuery)"
Whichever one you guys prefer, I'll pitch to my Engineering Project Managers as a project for myself.
Ryan Kaldari
On 4/2/11 12:29 PM, bawolff wrote:
Message: 2 Date: Fri, 01 Apr 2011 18:40:00 -0700 From: Ryan Kaldarirkaldari@wikimedia.org Subject: Re: [Wikitech-l] Focus on sister projects To: Conrad Irwinconrad.irwin@gmail.com Cc: Wikimedia developerswikitech-l@lists.wikimedia.org Message-ID:4D967E70.2080108@wikimedia.org Content-Type: text/plain; charset=windows-1252; format=flowed
[...]
As long as we're on the subject of wiktionary, I notice that there's a lot of custom Javascript there for handling specialized editing tasks like editing glosses, managing translations, etc. It seems like some of this functionality could be improved further and developed into full-fledged extensions (making it easy for other wiktionaries to use as well). Would you have any interest in working up a couple Wiktionary project proposals for the upcoming Hackathon in Berlin?
Ryan Kaldari
This isn't just true of wiktionary. Lots of sister projects have specialized work flow tools in js. Wikinews has review related tools in js and a hack that adds a second "talk" namespace, Wikisource has the proofread page extension, but still much of there workflow is written in js, I'm sure many other projects have specialized stuff that should be in php extensions.
The issue is at the end of the day it is _significantly_ easier to write a js hack, then to manage to get a php extension written, reviewed and deployed.
-bawolff
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On 04/02/2011 04:08 PM, Ryan Kaldari wrote:
- Creating "The Complete Idiot's Guide to Writing MediaWiki Extensions"
and "The Complete Idiot's Guide to Writing MediaWiki Gadgets (in jQuery)"
+1 ... Beyond the guide we could win a lot by centralising some of the scripts and libraries on mediawiki.org and establishing best practices for things like gadget localisation.
--michael
On Sun, Apr 3, 2011 at 5:57 PM, Michael Dale mdale@wikimedia.org wrote:
On 04/02/2011 04:08 PM, Ryan Kaldari wrote:
- Creating "The Complete Idiot's Guide to Writing MediaWiki Extensions"
and "The Complete Idiot's Guide to Writing MediaWiki Gadgets (in jQuery)"
+1 ... Beyond the guide we could win a lot by centralising some of the scripts and libraries on mediawiki.org and establishing best practices for things like gadget localisation.
--michael
I believe Krinkle started doing that with gadgets when he was updating them to jQuery & Resourcelorder compatibility... Although I don't know how many sites load them remotely (like how many sites do with HotCat from commons[1]) or just copy and paste them onto their local sites.
[1]. http://www.mediawiki.org/wiki/MediaWiki:Gadget-HotCat.js
K. Peachey wrote:
On Sun, Apr 3, 2011 at 5:57 PM, Michael Dale mdale@wikimedia.org wrote:
On 04/02/2011 04:08 PM, Ryan Kaldari wrote:
- Creating "The Complete Idiot's Guide to Writing MediaWiki
Extensions" and "The Complete Idiot's Guide to Writing MediaWiki Gadgets (in jQuery)"
+1 ... Beyond the guide we could win a lot by centralising some of the scripts and libraries on mediawiki.org and establishing best practices for things like gadget localisation.
--michael
I believe Krinkle started doing that with gadgets when he was updating them to jQuery & Resourcelorder compatibility... Although I don't know how many sites load them remotely (like how many sites do with HotCat from commons[1]) or just copy and paste them onto their local sites.
[1]. http://www.mediawiki.org/wiki/MediaWiki:Gadget-HotCat.js
Yep, the most popular ones I've made central by either loading them from Commons, Meta-Wiki or MediaWiki.org (Usually Meta-Wiki for wmf specific, MediaWiki.org for universal ones, although some are on Commons or en.wikipedia for historical reasons[1] )
Gadgets that are very simple in nature (that aren't worth an http- request) I have put into the Snippets directory [2]. This includes popular things that are often in scripts like Common.js such as Main page -tab text fixer[3], redirecting User:Name/skin.js/css to the appropiate place [4], Unwatch from watchlist [5] and much more.
-- Krinkle
[1] Although they could be moved to Meta, right now I'm not because their developer would no longer be able to update them as they're usually sysop on commons or en.wiki. [2] http://www.mediawiki.org/wiki/Category:All_snippets http://www.mediawiki.org/wiki/Snippets [3] http://www.mediawiki.org/wiki/Snippets/Main_Page_tab MediaWiki 1.18 will make this script redundant. But any wiki running an older version (either wmf or not) will find this useful. [4] http://www.mediawiki.org/wiki/Snippets/Redirect_skin.js Although common.js exists now, skin.js/css is still used a lot. [5] http://www.mediawiki.org/wiki/Snippets/Unwatch_from_watchlist
On 2 Apr 2011 at 16:08, Ryan Kaldari wrote:
What do you guys think would be more useful:
- Helping sister projects write up proposals for the Berlin Hackathon
If it is going to get selected and have outcome for my favourite wiki, then yes ;-)
- Creating "The Complete Idiot's Guide to Writing MediaWiki Extensions"
and "The Complete Idiot's Guide to Writing MediaWiki Gadgets (in jQuery)"
To me this has great great value, and I hope that when you say complete you mean "COMPLETE!!!" and I would hope that you would encourage and give examples of good documentation. Some of us are not natural programmers, though we can adapt scripts to suit our needs, and when given I find the explanations very useful.
Regards, Andrew
Whichever one you guys prefer, I'll pitch to my Engineering Project Managers as a project for myself.
Ryan Kaldari
On 4/2/11 12:29 PM, bawolff wrote:
Message: 2 Date: Fri, 01 Apr 2011 18:40:00 -0700 From: Ryan Kaldarirkaldari@wikimedia.org Subject: Re: [Wikitech-l] Focus on sister projects To: Conrad Irwinconrad.irwin@gmail.com Cc: Wikimedia developerswikitech-l@lists.wikimedia.org Message-ID:4D967E70.2080108@wikimedia.org Content-Type: text/plain; charset=windows-1252; format=flowed
[...]
As long as we're on the subject of wiktionary, I notice that there's a lot of custom Javascript there for handling specialized editing tasks like editing glosses, managing translations, etc. It seems like some of this functionality could be improved further and developed into full-fledged extensions (making it easy for other wiktionaries to use as well). Would you have any interest in working up a couple Wiktionary project proposals for the upcoming Hackathon in Berlin?
Ryan Kaldari
This isn't just true of wiktionary. Lots of sister projects have specialized work flow tools in js. Wikinews has review related tools in js and a hack that adds a second "talk" namespace, Wikisource has the proofread page extension, but still much of there workflow is written in js, I'm sure many other projects have specialized stuff that should be in php extensions.
The issue is at the end of the day it is _significantly_ easier to write a js hack, then to manage to get a php extension written, reviewed and deployed.
-bawolff
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
wikitech-l@lists.wikimedia.org