On Wed, Dec 2, 2015 at 1:58 PM, Grace Gellerman ggellerman@wikimedia.org wrote: <snip>
=== Reading Infrastructure ===
- Block: ApiSandbox is still blocked on whoever owns oojs-ui for
https://phabricator.wikimedia.org/T91148 - ACTION! let's figure out an alternative approach (James F suggests separate component in mw.Widgets)
</snip>
Could people weigh in on the ticket about what it might take to get this into mw.Widgets instead? James noted, as has been discussed on this list, that at the moment people are leery of adding any further bloat to oojs-ui (particularly if it's a nontrivial number of KB like this). A fuller solution would entail splitting out critical oojs-ui components in a manner where they're more easily loaded piecemeal, but it sounded like that's more involved.
I do wonder though if we've spent much time studying the ease of getting at least some part of oojs-ui split out or making it so that new stuff going forward is part of the oojs-ui family but it's not as monolithich?
-Adam
On Fri, Dec 4, 2015 at 12:59 PM, Adam Baso abaso@wikimedia.org wrote:
On Wed, Dec 2, 2015 at 1:58 PM, Grace Gellerman ggellerman@wikimedia.org wrote:
<snip>
=== Reading Infrastructure ===
- Block: ApiSandbox is still blocked on whoever owns oojs-ui for
https://phabricator.wikimedia.org/T91148 - ACTION! let's figure out an alternative approach (James F suggests separate component in mw.Widgets)
</snip>
Could people weigh in on the ticket about what it might take to get this into mw.Widgets instead?
Time for someone (probably me) to refactor the code for the change of namespace, decide what to do about the name collision and the parts that aren't really widgets, and put up a new patch. Then getting someone to review and merge.
Alternatively, someone could rework the "DateInputWidget" that's already in there into something that's compatible with an HTML5 <input type="datetime"> rather than only <input type="date">.
On 2015-12-04 18:59, Adam Baso wrote:
I do wonder though if we've spent much time studying the ease of getting at least some part of oojs-ui split out or making it so that new stuff going forward is part of the oojs-ui family but it's not as monolithich?
Not any more than what is written at https://phabricator.wikimedia.org/T113681#1673158, as far as I know.
OOjs UI doesn't have a dedicated team (or even a dedicated person) supporting it. The changes are mostly driven by whatever the VisualEditor or Design teams need, and what they are willing to implement themselves (and to a lesser extent, Multimedia team and random people like Brad or Florian). This makes it difficult to make any big changes happen.
wikitech-l@lists.wikimedia.org