Re: [whatwg] HTML6 single-page apps without Javascript proposal now on Github

Hello!

By way of introduction, I'm an author who reads some of these mailing lists but (almost) never replies.



This proposal is quite interesting, wanted to throw in my two cents as well:



1. Would you consider writing a polyfill/Javascript framework for this? 
It seems to me that the fundamentals of the proposal could be fairly 
simply written into a small Javascript polyfill by intercepting a[mref] 
clicks and filling up <template>s. A working polyfill would give 
people a chance to play around with the proposal, give you (and others 
who like the idea) a working implementation of it in case it doesn't 
become a standard, and provide an otherwise-necessary polyfill for older
 browsers if it does become a standard.



2. You've mentioned before that this would be more useful for beginners 
(who only know HTML, not Javascript), but I don't necessarily agree. 
With this proposal you would need to explain how the browser downloads 
"JSON data" from the mref attribute's location, then somehow parses into
 a model, and then fills up and displays a template (making what the 
page is actually showing extremely different from what they write in 
their editor, not exactly intuitive). IMO the biggest hurdle for a 
beginner to get over would be conceptually understanding the models and 
templates, which HTML's declarative nature seems to make more difficult 
to understand. I would prefer having a Javascript library where the user
 could write something along the lines of "link.onclick = 
fillTemplate(loadData())", making what's actually happening when a user 
clicks a link much clearer. The person would still need to understand 
some Javascript, but not much more than what's necessary for the model 
attributes in your proposal currently.



I'm also curious as to how many beginners would *want* to do a SPA with 
templates and models like this, I would imagine that by the time you 
have a real need to load data from a backend API into models and 
templates without reloading the page that you'd have a workable 
understanding of Javascript enough to use an existing MVC framework of 
your choice.



Thanks,

Matthew Sotoudeh

> From: mozumder@futureclaw.com
> Date: Tue, 24 Mar 2015 22:10:12 -0400
> To: delfin@segonquart.net
> CC: whatwg@whatwg.org; master.skywalker.88@gmail.com
> Subject: Re: [whatwg] HTML6 single-page apps without Javascript proposal now	on Github
> 
> 
> > On Mar 24, 2015, at 9:51 PM, delfin <delfin@segonquart.net> wrote:
> > 
> > 
> > 
> > Hi all: 
> > 
> > I agree with you all you have quoted, Rendine. 
> > 
> > 	* Neal : " a problem in developing countries where low end devices are
> > the norm", is _de facto_ THE norme , and was the need of web
> > (standards).
> > 	* HTML6, if ever, must accomplish and adopt the so called
> > _retro-conditions_, HTML version 5 has.
> > 	* This conditions are, for example, that one can and must be able to
> > navigate through the Internet pages using an aged and abandoned
> > computer.
> 
> I mentioned it in the original message with the MREF property, you can use all of this on older browsers.
> 
> Older browsers will just ignore the <MODEL> elements and MODEL properties of elements, and will continue to function the same.  When you click on a link, instead of fetching the API endpoint that the MREF points to, it uses the canonical URL in the HREF property, like always.
> 
> This proposal should be backwards compatible on older browsers.  If it isn’t, let me know.
> 
> -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 Wednesday, 25 March 2015 02:57:54 UTC