On Mon, Jul 22, 2013 at 3:00 PM, Roan Kattouw roan.kattouw@gmail.comwrote:
On Mon, Jul 22, 2013 at 9:51 AM, Eran Rosenthal eranroz89@gmail.com wrote:
Hi, When the ResourceLoader was deployed (or even before it) to production, there were migration development guides for gadget/extension developers:
http://www.mediawiki.org/wiki/ResourceLoader/Migration_guide_for_extension_d...
http://www.mediawiki.org/wiki/ResourceLoader/Developing_with_ResourceLoader
Such guides allowed easier adoption of ResourceLoader. We need something similar for the visual editor:
Yes we do :) . More generally, VE needs plugin infrastructure. Most of it is already there, and I'm working on the last bits of it.
- Migration - What are the recommended steps to make gadget/extension
VE adapted? [with answers to questions such as: how to get the
underlying
model - instead of $('#wpTextbox1').val() and what is this model [and
what
modifications to the underlying model are supported/to be avoided by gadgets/user scripts ] ]
- Development with the VE: guides with explanation for common editor
UI
customization, and what is recommended API for it (for example: add
custom
toolbar buttons).
These are excellent suggestions for documentation we should write once the plugin infrastructure work is done. I intend to do this in the next few weeks.
Roan
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Roan, how did that go? Any links? :-)
Sumana Harihareswara Engineering Community Manager Wikimedia Foundation