On Feb 25, 2014 12:55 AM, "Gryllida" <gryllida(a)fastmail.fm> wrote: collaboration of all teams to build a framework which lets people script the MediaWiki software including media viewer screen, log-in screens, article creation screens / wizard, an interactive thingie for working with templates [1] (taking an {{unblock}} request for example without having to memorize the template syntax). https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/168 software which are easy to maintain and share code with each-other? I don't. [The bouncing between mailing lists is making this thread confusing] Interactive templates (i.e. magic buttons on templates that edit wiki text to change a parameter in the template to change its "state") is a rather different type of thing than allowing js to (cleanly) hook into/extend js-based extensions at fixed points. A single framework for both those types of things does not make sense. (Unless you are talking on a generic js library level). In your original email, you list 3 things which fall into the hook category, followed by a fourth that could be interpreted as a hook thing unless one reads the link carefully, which is why I think Mark responded with "Hooks!". (Obviously that is just my intetpretation, I don't speak for him, so he would have to clarify if this interpretation is consistent with his views). As it stands (i dont live in js land, correct me if I'm wrong), its widely agreed having hooks for user-scripts to hook into js-based extensions like upload wizard and other parts of mw is a good thing. Its not neccesarily agreed that having support for magic wiki-text altering templates on the mediawiki level is a good thing. As far as i am aware, nobody is currently trying to make a framework for that use case on the mediawiki level (beyond generic support for js and js abstractions for api access) --bawolff

On Tue, 25 Feb 2014, at 17:52, Brian Wolff wrote: I'm not seeing decent JS "framework" either; where one wants to have the contributor move or create a page as a part of gadget work, he has to code a textbox-which-checks-and-probably-also-autocompletes-a-page-name manually with little means available of sharing his JS subroutine or object for other gadgets ­-- on multiple projects -- to reuse.