> On Mar 23, 2015, at 5:33 AM, Nils Dagsson Moskopp <nils@dieweltistgarnichtso.net> wrote: > > XForms, Microdata and XSLT all do different things. Note that no widely > used browser supports XForms in its default configuration; while Chrome, > Firefox, Internet Explorer, Safari and Opera all support XSLT. Can you > explain the “clear usability & design issues” you have seen in XSLT? > > If so, please do. There’s no locally persistent model object. It’s not an MVC framework. It’s a view layer. And it’s not just me. There’s a reason Angular, React, Ember, and so on don't use XSLT in trying to solve the single-page app problem, probably because it doesn’t have a locally persistent model object. > I certainly did not. I would like to see an implementation of your > proposal and several demonstrations. Do you have something on hand? Are you familiar with MVC design patterns? This would be what it is. Sorry, don’t have an implementation on me. What’s the process going forward? Do people need to write a web browser for every proposal? > I agree in that buzz does not necessarily mean your proposal has merit. Did you ask the people talking about it? What were their opinions? -bobby --- Bobby Mozumder Editor-in-Chief FutureClaw Magazine mozumder@futureclaw.com <mailto:mozumder@futureclaw.com> +1-240-745-5287 www.futureclaw.com <http://www.futureclaw.com/> twitter.com/futureclaw <https://www.twitter.com/futureclaw> www.linkedin.com/in/mozumder <http://www.linkedin.com/in/mozumder>
Received on Monday, 23 March 2015 10:11:40 UTC