Talk:Contributors/Roadmap
Add topicAppearance
Latest comment: 10 years ago by Jdforrester (WMF) in topic Legoktm's ideas
Legoktm's ideas
[edit]Random stuff I'd also like to see worked on...:
- Killing the monster that is EditPage.php (fixing it would be fine too I guess...)
- Live preview by default
- Sane edit notice system (aka not enwp's silly template titleblacklist system)
- Killing Extension:WikiEditor and putting it in core and extension-ify the legacy toolbar
Legoktm (talk) 22:07, 19 July 2014 (UTC)
- Hey!
- Killing the monster that is EditPage.php (fixing it would be fine too I guess...)
- Sounds like a good idea. Do you have particular thoughts other than "better"Â â is there an obvious way forward? Should we do an RfC? (Oy.)
- Live preview by default
- Hmm, sounds exceptionally API-expensiveâŠ
- Sane edit notice system (aka not enwp's silly template titleblacklist system)
- Yeah; adding a nicely-editable proper edit notice system is certainly something that I'd like to see.
- Killing Extension:WikiEditor and putting it in core and extension-ify the legacy toolbar
- Eh. I'd rather kill the legacy toolbar and make the concept of "the editor" a configurable thing, with core support for 1âŠn editors (with a primary).
- Killing the monster that is EditPage.php (fixing it would be fine too I guess...)
- Thoughts? Jdforrester (WMF) (talk) 16:26, 21 July 2014 (UTC)
- At first pass, separating the UI and backend logic would be a good start.
- It's just shifting the parse load from index.php to api.php AFAIS it.
- What's the use case of having multiple configurable editors? WikiEditor is already extendable, and most plugins (CodeEditor, reftoolbar) today just extend it.
- Legoktm (talk) 23:34, 21 July 2014 (UTC)
- @Legoktm: The use case is cleaner system-provided integration for VisualEditor, FCYEditor, etc⊠Jdforrester (WMF) (talk) 19:47, 22 July 2014 (UTC)