Yes, moving transformations that currently the client does to the server is one of the approaches the service is doing. Well, it's doing some already but hopefully more soon.
I've started documenting the service at https://www.mediawiki.org/wiki/RESTBase_services_for_apps. And now for another service announcement: Following this discussion, during our prioritization meeting earlier we had a discussion about the missing role of a tech-product guy. (Was is tech-pro or pro-tech? I don't remember.) In any case it'll be more technical than a traditional PO role, or even the aforementioned tech-pro/pro-tech. To keep a long story from getting longer, I've volunteered to play that role for the near-term future. Side note: What this also means for the Android team, is that I'll have less time coding on the Android app, and split my time mostly between Mobile apps Node.js service lead and Android tech lead roles. I'm going to reach out more in the upcoming week(s) to figure out a few things: * Collect near-term requirements + add Phabricator tasks. * Prioritize them. * Reach out to the web team to learn what this team's plan is for their Node.js service and see if/how much we can share between apps and web. -Bernd On Fri, Jun 12, 2015 at 2:13 PM, Gergo Tisza <[email protected]> wrote: > On Fri, Jun 12, 2015 at 5:27 AM, Federico Leva (Nemo) <[email protected]> > wrote: > >> Gergo Tisza, 12/06/2015 03:51: >> >>> >>> Editors would write something like this in the source code: >>> '''Vincent Willem van Gogh''' {{#snippet|role=pronunciation|IPA=ˈvɪnsɛnt >>> ˈʋɪləm vɑn ˈɣɔx}}{{#snippet|role=birth and death|birth=30 March >>> 1853|death=29 July 1890}} was a major [[Post-Impressionist]] painter. >>> >> >> Really? Why not use the traditional way, i.e. a CSS class that can be >> applied to existing templates like noprint, nomobile and friends? > > > Transformations should ideally be done on the server, not on the client. > The latter means impairing performance by pushing unneeded content to the > client, having the client do complex DOM transformations, and storing the > necessary code on the client (which also means writing it in as many > languages as the types of clients we have). > > _______________________________________________ > Mobile-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/mobile-l > >
_______________________________________________ Mobile-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mobile-l
