W3C home > Mailing lists > Public > public-html@w3.org > April 2015

Re: A successor to framesets

From: Sean Hogan <shogun70@gmail.com>
Date: Thu, 2 Apr 2015 16:37:13 +1100
Message-ID: <CAHQTpmDmpWw8iPjm7i-NzOUfg65Z5hkCm45MCwOg--stUixwJQ@mail.gmail.com>
To: Andrea Rendine <master.skywalker.88@gmail.com>
Cc: Eihab Ibrahim <eihabibrahim@gmail.com>, "public-html@w3.org" <public-html@w3.org>
I'm surprised at your response.

How would you make the case for a solution to SPAs that is both
backwards-compatible and potentially declarative?

Would you just simply post a message saying it needs to be done and
provide some initial example code?

Would you hand-craft a few demos to make the point?

Or would you explore the idea by creating a polyfill / framework that
both allows you to test scenarios quicker, build demos, and one day
allow others to *experiment*?

In the past year I've done the first two, but now with a framework it
quicker to explore and demonstrate - a picture tells a thousand words.

The framework is just an implementation, the approach is the primary
thing. (Actually what's important is URLs, semantic HTML and simpler
markup). That's why people should watch and respond to the video.

>From the framework project page:

    <blockquote>
    WARNING: THIS PROJECT IS ALPHA SOFTWARE. ONLY USE IT FOR EXPERIMENTATION.
    </blockquote>

And the start of the video:

    <blockquote>
    Yes, it is another Javascript framework.
    But it's really more a way of thinking about web-sites.
    It's about URLs and semantic HTML
    and encouraging web-sites to emit simpler markup from the server
    and delegating completely a richer user interface to the browser.

    And maybe web-sites will end up looking more like APIs,
    just with a HTML content-type.
    And maybe APIs will look more like web-sites.

    And I think that on older browsers (like IE9) and smaller devices,
slower connections, strange browsers
    it will be more likely that the end-user gets some content in a
usable manner.
    </blockquote>



Can you suggest a better way of introducing this proposition?

regards,
Sean

On Wed, Apr 1, 2015 at 11:08 PM, Andrea Rendine
<master.skywalker.88@gmail.com> wrote:
> This is nothing more than a JS framework project about AJAX-powered template
> websites.
> For the sake of completeness and for those who do not have 25 minutes to
> waste:
> http://github.com/meekostuff/HyperFrameset
> the project page.
> Disgracefully, neither the video nor the project itself are April's fools.
>
> 2015-04-01 9:53 GMT+02:00 Eihab Ibrahim <eihabibrahim@gmail.com>:
>>
>> Hi Sean,
>>
>> It's a bit too early in the US for April fools' jokes, and I do not think
>> this is an appropriate platform for it.
>>
>> Respectfully,
>>
>> Eihab
>>
>> On Mar 31, 2015, at 10:56 PM, Sean Hogan <shogun70@gmail.com> wrote:
>>
>> HTML framesets were the original single-page-application.
>>
>> Despite the flaws (mostly not being content-first), at least servers
>> were emitting reasonably simple HTML including real hyperlinks and
>> forms.
>>
>> What would framesets be like if we designed them today?
>>
>> In the linked video I make the case for a successor to framesets.
>> It is 25 minutes but that is unavoidable.
>>
>>    https://youtu.be/qVdAc8_ppao
>>
>> The first half illustrates *why* this is important / better than
>> alternatives,
>> with actual demonstrations (which you should try for yourself to
>> ensure I'm not cheating).
>>
>> The second half provides some insight into how I've approached this,
>> again with demonstrations.
>>
>> I'll continue later with details of the differences / enhancements
>> required to make the frameset concept live up to today's expectations.
>>
>> regards,
>> Sean
>>
>>
>>
>
Received on Thursday, 2 April 2015 05:37:40 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:43 UTC