[Wikitech-l] Mantle - coding sharing between Flow and MobileFrontend

2014-07-03 Thread Jon Robson
== The problem == MediaWiki has a huge UI standardisation problem. We use different libraries, different css styles and class names, some of which do the same thing. Recently the teams working on Flow and MobileFrontend noticed they were doing various things in a similar fashion. We were both

Re: [Wikitech-l] Mantle - coding sharing between Flow and MobileFrontend

2014-07-03 Thread Trevor Parscal
Jon, I know you mean well, and that you are passionate about solving this problem, but I do not believe this is the right approach. I've communicated that in another thread with a smaller group, and you did not respond to me. Now you are changing key details in the proposal, but the extension code

Re: [Wikitech-l] Mantle - coding sharing between Flow and MobileFrontend

2014-07-03 Thread Jon Robson
Trevor, That email you quote was about totally different code and a proposal to put it into Mantle and is off topic for this discussion.\T Trevor, please grab me in real life, so we can quell this misunderstanding asap, I feel for whatever reason I am not effectively communicating to you and

Re: [Wikitech-l] Mantle - coding sharing between Flow and MobileFrontend

2014-07-03 Thread Ryan Kaldari
This whole thread seems a bit silly to me. We put stuff that should be in core into extensions all the time (for lots of different reasons). For example: WikiEditor, VisualEditor, Echo, MobileFrontend, JsonConfig, etc. So why is Mantle such a bad idea? There's no consensus on implementing

Re: [Wikitech-l] Mantle - coding sharing between Flow and MobileFrontend

2014-07-03 Thread Trevor Parscal
Indeed, this thread is a bit silly. If someone wants to make an extension that provides a feature, and someone else wants to use it, there's nothing wrong with that. But why would such a thing need proposing? If the point of Mantle is only to provide a way to bring templates to the client, then

Re: [Wikitech-l] Mantle - coding sharing between Flow and MobileFrontend

2014-07-03 Thread Legoktm
On 7/3/14, 11:23 AM, Ryan Kaldari wrote: This whole thread seems a bit silly to me. We put stuff that should be in core into extensions all the time (for lots of different reasons). For example: WikiEditor, VisualEditor, Echo, MobileFrontend, JsonConfig, etc. I'd say that most of those are

Re: [Wikitech-l] Mantle - coding sharing between Flow and MobileFrontend

2014-07-03 Thread Erik Moeller
On Thu, Jul 3, 2014 at 9:09 AM, Jon Robson jrob...@wikimedia.org wrote: == The future == Mantle is only a short term measure. The hope is that all the code that goes here will eventually go into core. We hold the code here to exactly the same high standards that we hold core to, we are just

Re: [Wikitech-l] Mantle - coding sharing between Flow and MobileFrontend

2014-07-03 Thread Ryan Kaldari
What you're saying, Trevor, makes sense, and I agree that we shouldn't have a code purgatory. I won't presume to speak for Jon, but I imagine his somewhat provocative presentation of Mantle is due, at least in part, to frustration. About a year ago, the mobile web team was gung-ho to start moving

Re: [Wikitech-l] Mantle - coding sharing between Flow and MobileFrontend

2014-07-03 Thread Pine W
Sounds like there are some issues here that may need untangling. I'm pinging Erik. He's probably aware of this but I would like to hear his POV. Mobile is high on WMF's priority stack and it's high on my list of personal interests. Pine On Thu, Jul 3, 2014 at 1:46 PM, Ryan Kaldari

Re: [Wikitech-l] Mantle - coding sharing between Flow and MobileFrontend

2014-07-03 Thread Pine W
Sorry Erik, I missed your post in the discussion above and just saw it as I was working my way back through the stack of emails. Anyway, I hope this is on your radar. Pine On Thu, Jul 3, 2014 at 9:55 PM, Pine W wiki.p...@gmail.com wrote: Sounds like there are some issues here that may need

Re: [Wikitech-l] Mantle - coding sharing between Flow and MobileFrontend

2014-07-03 Thread Trevor Parscal
I spoke with Jon in person and I think we have reached some sort of understanding. The main point I think should be made public - something I communicated to Jon in person - is that me stepping away from VisualEditor for a couple of months to work on UI standardization and a new skinning system