User:This, that and the other/Twinkle update

Just clearing up thoughts on how to do it.


 * 1) ✅ Get gadget functionality, etc. working
 * 2) Make sure there aren't any obvious bugs in the new code
 * 3) * Test in IE9, Firefox (versions TBD), Chrome (all versions are pretty much the same, aren't they?), Opera, Safari
 * 4) * Search for any XXX comments and see if they are worth fixing
 * 5) Do evangelism
 * 6) * Add info for technically-minded folk at WT:TW (i.e. new prefs mechanism, explanation of Wikipedia.page for developers of morebits-based scripts, and lots more goodness)
 * 7) New documentation, etc.
 * 8) * Rewrite bits of WP:TW, WP:TW/DOC, etc.
 * 9) * ✅ Add anchors to WP:TW/DOC according to the module script file name (i.e. for the CSD section)
 * 10) * Is there a page describing morebits.js? If so, rewrite it
 * 11) The big switchover
 * 12) * Update MediaWiki:Gadget-Twinkle.js, and delete MediaWiki:Gadget-TwinkleTEST.js
 * 13) * Update MediaWiki:Gadget-Twinkle to read something like
 * 14) * Remove the old Friendly gadget —
 * 15) * Update User:AzaToth/morebits.js and User:AzaToth/morebits.css from github
 * 16) * Make User:AzaToth/twinkle*.js (including User:AzaToth/twinkle.js), and User:Ioeth/friendly*.js, all contain the code in oldtwinkle.js in github
 * 17) * Check to make sure there is no bustage anywhere
 * 18) * Stick around on-wiki for a few hours, to handle the deluge of support requests, "help! what's happened???", "it doesn't work", etc.
 * 19) Relax (as if...)
 * 1) Relax (as if...)

Suggested spiel for WT:TW
Prompted by the short-lived switchover to MediaWiki's HTML5-compliant mode on Wikipedia (see Twinkle bug 441, and above), Twinkle developers have been working for some months on an overhaul of the tool, as well as AzaToth's   script library. This development has been taking place off-wiki, at a github repository, and has been largely done by UncleDouggie, Tcncv (the initiator, along with Douggie), AzaToth (Twinkle's inventor and owner), and This, that and the other.

Users of Twinkle will be able to take advantage of many improvements, including:
 * Transition to the MediaWiki API. Previously, Twinkle used to download the same editing form as is used by human editors, fill it out behind-the-scenes, and send the request back as if the "Save page" button had been clicked. This was unreliable – if the edit form changed, or if malformed editnotices were present, Twinkle failed. Now, Twinkle uses the MediaWiki API to edit pages, a more solid approach specially designed for programs and scripts like Twinkle.
 * New look. AzaToth created the old Twinkle look, with functional purpose only. Twinkle now has a refreshed look, based on jQuery UI.
 * Now works on Internet Explorer 9 (with very minor limitations, e.g. not being able to move the dialogs).
 * Lots of new features. You can now: tag a page with a protection lock using the RPP tool (for all users, not just admins); preview user warning templates before posting the warning; notify users about an AN/ANI discussion using the Talkback tool; enable a "userspace log" to keep track of your speedy and PROD nominations (huge thanks to Timotheus Canens for originally writing this).
 * Lots of new admin stuff. Admins can now: rest easy when protecting using the PP tool - it has been redesigned, and you have full control over what it does; opt not to delete the talk page and/or redirects when using the CSD tool; edit the deletion reason before deleting with the CSD tool.
 * And lots more minor annoyances and nits have been fixed.

Developers of scripts that use the  library should take note of the following two important points:
 * Obsolescence of  and replacement with
 * Changes to loading of morebits.js

For users and developers alike, if Twinkle stops working for you, or you have any other problems or questions, don't hesitate to ask them below. Thanks,