User:This, that and the other/Twinkle update

Just clearing up thoughts on how to do it.

1. Y Get gadget functionality, etc. working
2. Make sure there aren't any obvious bugs in the new code
   • Test in IE9, Firefox (versions TBD), Chrome (all versions are pretty much the same, aren't they?), Opera, Safari
   • Search for any XXX comments and see if they are worth fixing
3. Do evangelism
   • Add info for technically-minded folk at
     WT:TW#Rewrite
     (i.e. new prefs mechanism, explanation of Wikipedia.page for developers of morebits-based scripts, and lots more goodness) (see below)
4. New documentation, etc.
   • Rewrite bits of
     WP:TW/DOC
     , etc.
   • Y Add anchors to
     WP:TW/DOC according to the module script file name (i.e. {{anchor
     |speedy}} for the CSD section)
   • Is there a page describing morebits.js? If so, rewrite it
5. The big switchover
   • Update MediaWiki:Gadget-Twinkle.js, and delete MediaWiki:Gadget-TwinkleTEST.js
   • Update MediaWiki:Gadget-Twinkle to read something like

     [[Wikipedia:Twinkle|Twinkle]], a set of tools that automates many common maintenance tasks, including reporting vandalism, warning vandals, requesting deletion, and welcoming new users.

   • Remove the old Friendly gadget — What about people who only have the Friendly gadget enabled and not Twinkle?
   • Update User:AzaToth/morebits.js and User:AzaToth/morebits.css from github
   • Make User:AzaToth/twinkle*.js (including User:AzaToth/twinkle.js), and User:Ioeth/friendly*.js, all contain the code in oldtwinkle.js in github
   • Check to make sure there is no bustage anywhere
   • Stick around on-wiki for a few hours, to handle the deluge of support requests, "help! what's happened???", "it doesn't work", etc.
6. Relax (as if...)

Suggested spiel for

WT:TW

Prompted by the short-lived switchover to MediaWiki's HTML5-compliant mode on Wikipedia (see

• 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
  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.