W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2015

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

From: Andrea Rendine <master.skywalker.88@gmail.com>
Date: Tue, 24 Mar 2015 21:15:26 +0100
Message-ID: <CAGxST9nCyKfhi8-hEZ6YYGAQ1OCL9WpJ_CBk_gkrgt-7nbo_tg@mail.gmail.com>
To: Bobby Mozumder <mozumder@futureclaw.com>, WHATWG List <whatwg@whatwg.org>
I don't want to openly oppose to this project, as I'm anyway curious about
how it will be developed. It's only that I have seen a lot of elements used
outside their proper dynamics.
I don't see HTML as a templating language, but it's probably because I'm
tied to current use cases, so I don't see any further.
Anyway, yes, I write my pages so that their content is to remain when
served to client. Of course I would add more to the preexisting content,
given the circumstances, but not to change what's already there.
Besides, I invite you to consider, throughout the development process, a
possible role for <template> element. Instead of creating something
completely new, some features could be added to make it more complex and
more complete. It is now a container for markup that can be reused by
script to show content. Why not making it able to load its own content,
then?

2015-03-24 21:01 GMT+01:00 Bobby Mozumder <mozumder@futureclaw.com>:

>
> On Mar 24, 2015, at 8:19 AM, Andrea Rendine <master.skywalker.88@gmail.com>
> wrote:
>
> As an author I shall offer my 2 cents too.
> First off, I'm for native implementations and all that markup and CSS can
> do on _existing_ content.
> Thus said, I prefer having JS manipulating the content with AJAX than
> having the markup doing that.
> Apart from the concept that markup itself is being pushed too far, from an
> instrument capable of specifying properties for its content to something
> acting on its own, I think there's more potential for security issues than
> for genuine manipulation.
> Maybe things will move towards that end from now on, as websites have to
> look like web apps and this means that they have to be "apps executed on a
> browser platform", but I personally prefer an "ideal" model where
> - html provides static content, i.e. content which does not change when
> looking at the page structure itself
> - css provides ALL the graphic/presentational stuff and even some
> interface, (everyone can imagine what can be done with ":target" or
> ":checked" selectors...)
> - js provides dynamic content, i.e. whatever is to be considered part of
> the content itself when actions are executed or events are fired.
> Let's see what happens, then. This was just an idea.
>
>
>
> In this proposal, HTML would turn into a templating language.  A template
> is a perfectly valid document specification.  You see document templates
> everywhere, at the office supply store, in Adobe inDesign, and so on.
>
> Besides, when was the last time you actually wrote a static HTML file?
> Does anyone do that?
>
> For every web site, people actually write templates, not HTML code.
>
> This proposal standardizes on the idea of using HTML for templates.
>
> -bobby
>
> ---
> Bobby Mozumder
> *Editor-in-Chief*
> FutureClaw Magazine
> mozumder@futureclaw.com
> +1-240-745-5287
> www.futureclaw.com
> twitter.com/futureclaw <https://www.twitter.com/futureclaw>
> www.linkedin.com/in/mozumder
>
>
Received on Tuesday, 24 March 2015 20:16:02 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:29 UTC