User:Jdlrobson/Quest/Frontend UI standardisation
Roadmap
editIcon standardisation
edit- Get mw-ui-icon into the [style guide]. [DONE]
- Make all projects not using OOJS UI use the same markup as the components in the styleguide.
- #Consolidate code between styleguide consumers and VisualEditor
Get consistent Forms across MediaWiki by applying MediaWiki UI
edit- Resolve bugs preventing [from being true]
- Setup beta feature for form standardisation so that community can give feedback and we can polish existing components.
- Implement mw-ui-select
- Implement mw-ui-radio
- Set $wgUseMediaWikiUIEverywhere = true
- #Consolidate code between styleguide consumers and VisualEditor
Consolidate code between styleguide consumers and VisualEditor
edit- Provide component api for building mediawiki ui elements using oojs ui - (using OOJS UI template widget?)
- Update all consumers of the styleguide to generate markup using the component api (see example code below)
- Consolidate markup between VisualEditor and Styleguide consumers
e.g. something like this
mw.ui.button( { constructive: true } );
$this->getSkin()->ui()->button( { constructive: true } );
MobileFrontend to use OOJS
edit- Make MobileFrontend use OO.EventEmitter and OO.inheritClass [DONE]
- Jon to explore using connect and OO.Registry in MobileFrontend
- Trevor to create an OOUI template widget that allows an OOUI widget to render a template
- Refactor View.js in MobileFrontend to use the OOUI template widget that Trevor is building
- Consolidate Dialog and Overlay code between Growth, Flow and MobileFrontend
Echo standardisation
edit- Rewrite Echo desktop overlay to use OOJS
- Move Echo mobile code in MobileFrontend into Echo, when they are built in a standard way
- (Other stuff - to be fleshed out)
Template standardisation
edit- Resolve template RFC, Get templates in core
(Hopefully this will full out of the other work)