W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

Re: Model-driven Views

From: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Fri, 29 Apr 2011 14:38:55 +0300
Message-ID: <4DBAA34F.2050703@helsinki.fi>
To: Garrett Smith <dhtmlkitchen@gmail.com>
CC: Rafael Weinstein <rafaelw@google.com>, public-webapps@w3.org
On 04/29/2011 04:11 AM, Garrett Smith wrote:
> On 4/28/11, Olli Pettay<Olli.Pettay@helsinki.fi>  wrote:
>> On 04/28/2011 04:46 AM, Rafael Weinstein wrote:
>>>> Would be good to know what are the use cases you had in mind.
>>> I'm never sure if I'm using the term "use case" correctly =-).
>>> Our primary motivator is the needs of web applications,
>> And what are those needs? It is hard to judge the proposal
>> if it is not known what kinds of problems it is trying to solve ;)
> Create HTML content that gets refreshed, using JSON?

That doesn't explain the feature set MDV supports.
Why, for example, JSON/Model data can't affect to what kinds
of elements the template creates. Or attributes.
Why certain functionality is in and other functionality is out.

So basically I'd like to see either some requirements document
or at least public discussion about the design of the API.


> Load chunks of
> samely structured content on-demand. Sample app I made for bittorrent
> when applying for a job: http://dhtmlkitchen.com/tmp/bittorrent/
> (waste of time, that was).
> For example of content that gets refreshed, a table refresh widget
> would update the data in the HTML TABLE by fetchng JSON.
> Content that is loaded on-demand but reused in a template could be a
> product-info panel or a tooltip. Each panel is tied to an actuator and
> is shown with unique data, but it is created from a template that has
> essentially the same structure.
Received on Friday, 29 April 2011 11:39:29 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:31 UTC