|Open||None||T49145 Formally deprecate jQuery UI after we've stopped using jQuery UI in extensions and core (replacing it with OOUI).|
|Open||None||T100270 Replace use of jQuery UI and MW UI with OOUI across all Wikimedia-deployed extensions and core|
|Open||None||T122014 Convert all extensions/skins to OOUI|
|Resolved||Jayprakash12345||T203839 Convert Extension:Cargo to OOUI|
@Jayprakash12345 - thanks for creating all these patches! I could never get myself to look into modifying the helper forms to use the new coding style, so I'm glad you've done the important work.
As you probably know, I've already checked in the patches for action=recreatedata and Special:DeleteCargoTable. I have some issues with the other two patches:
By the way, there's one more interface provided by Cargo that could be potentially switched over to OOUI - Special:Drilldown. It already includes autocompletion, though - is that the reason why you didn't include it in this set?
I think we should use a Red button. But I want to @Volker_E's answer on that from UI point of view.
- Special:ViewData - I prefer the label to be on the same line as the input in this particular form,
Nope, I had same question sometime before. But I got the answer from Volker_E, See T192099#4183399
I plan in the future to add autocompletion to some of these inputs.
You can do it, HTMLForm has many numbers of Autocomplete widget like title, username & email etc. But You can also implement custom Autocomplete. this will easy because there are already have numerous example. & also T188892 will be complete soon.
Is that the reason why you didn't include it in this set?
No, I had only checked Specials/* files. Now I got it.
Check Widget existence before OO.ui.infuse
I got an error on creating the new Table, The console says Widget is not found. This is because when we go to create a new table. $tableExists is return false. and OOUI\CheckboxInputWidget does not execute as expected. But OO.ui.infuse want to infuse "#createReplacement". And So the error comes. The above patch should fix it.
@Jayprakash12345 and @Volker_E - thanks for all your help with this. The changes to action=recreatedata, Special:DeleteCargoTable and Special:SwitchCargoTable have now been merged in. That may be it as far as Cargo's special pages, though - for Special:Drilldown and Special:ViewData, I think the autocompletion (or, in the case of Special:ViewData, planned autocompletion) is more complex than what HTMLForm/OOUI currently supports. I did, however, just check in some changes to Special:ViewData to make the inputs more closely resemble those of HTMLForm/OOUI (taller and wider).