If the widget is not specific to MW we should not restrict its usage to MW.
Currently I think this would include:
and in VE-core that should be moved up:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T112468 Move non-MW specific widgets from mediawiki.widgets up into OOUI | |||
| Open | None | T91148 Consolidate MediaWiki core's date and time input widgets; consider moving (one of?) them upstream | |||
| Resolved | matmarex | T97425 Create a datepicker input widget | |||
| Open | Feature | None | T21992 Support client-side date/time formatting for user's timezone, language, and preferred format (JavaScript) |
LanguageSearchWidget is also dependent on jQuery.uls.data, or some list of autonyms, to be useful.
CalendarWidget and DateInputWidget depend on moment.js. Either we'd have to add is as a dependency to OOjs UI, or reimplement them not to require it (which would primarily mean including our own translations for month and day names, and date and number formatting routines).
LanguageSearchWidget is also dependent on jQuery.uls.data, or some list of autonyms, to be useful.
I guess we could put a brain-dead version in OOUI (without data), and then have MW-widgets replace it (somehow?) so that VE-core's use of it magically uses an MW-ified version. Or VE-MW could over-ride the VE-core functionality?
So what you're saying is that we should specify a dependency on jquery.uls,
but not bundle it with OOjs UI.
No, I was going to have OOUI's widget magically use the same data structure as jquery.uls.data, and let the platform infuse it with data.