Re: Widgets & ApplicationCache (was: Standards for Web applications on mobile devices: August 2011 updates)

Le samedi 17 septembre 2011 à 10:30 +0100, Marcos Caceres a écrit :
> shortcut: if you want to (incorrectly, IMO) continue to lump widgets
> and app cache, then do so making it clear that this is just one of the
> use cases for widgets and certainly NOT the primary use case…

My document focuses on technologies available to build client-side Web
applications for mobile devices; the 52 specifications that the document
mentions have all use cases that go well beyond that use case, but I
don't think the document would win in usefulness or clarity by stating
so for each of these specifications.

>  And please add a separate section just for Widgets in your document
> that explains the other cases.  

If by the other cases, you mean:

> They have been used as server side applications, standalone
> applications, daemons, and as an extension format.  

Server-side applications, daemons, and browser extensions are clearly
out of scope of the document, so I don't think it would make sense to
list them.

> I agree that there are similarities and overlap for this *one* use
> case; but again, the use cases of Widgets are far greater than
> ApplicationCache. To lump them together waters Widgets down to a
> confusing equivalent to AppCache.

The document specifically says that the two approaches are complementary
(not redundant), and summarizes what the two technologies provide.

I don't see why having them in the same section would mean they're
equivalent (again, no more than having SVG and CSS in the same section
would mean they're equivalent).

If you think the current description doesn't convey clearly enough the
differences between the two approaches, I'll be happy to review a better
description (either in reply to this mail, or directly in the wiki
http://www.w3.org/wiki/Standards_for_Web_Applications_on_Mobile ).

Dom

Received on Monday, 19 September 2011 08:06:40 UTC