W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2009

Widget API Set/GetPreferences vs. HTML5 Key/Value Pairs Storage

From: <ivan.demarino@orange-ftgroup.com>
Date: Tue, 3 Feb 2009 12:19:55 +0100
Message-ID: <B877D90AB2240C4D84DF56169F1EAFED05EEF243@ftrdmel3>
To: <marcosscaceres@gmail.com>
Cc: <rafel.uddin@orange-ftgroup.com>, <mali.ext@orange-ftgroup.com>, <public-webapps@w3.org>, <mali.ext@orange-ftgroup.com>

Hello.

After some emails with Marcos Caceres we reached the conclusion that
part of the Specs of Widget APIs
(http://dev.w3.org/2006/waf/widgets-api/) overlaps/clashes with the
HTML5 standard draft about Key/Value Pairs Storage
(http://www.whatwg.org/specs/web-apps/current-work/#structured-client-si
de-storage).

Our suggestion is that we should go with the HTML5 standard, removing
those apis the Widget API Specs, because:
1) Most probably it will be supported from every browser soon anyway
2) There are Open Source browsers, like WebKit, were it's already
finding it's space (take a look to the WebKit source code)
3) It will allow developer to learn less apis for the same purpose
4) They do the same thing but...
5) The HTML5 draft already provides APIs for "enumeration", "cleaning"
and "iteration"
6) The Widget object will become more coherent, focusing on things like
"widget status" and "widget informations"
7) The OMTP BONDI initiative itself avoided to go into the "Persistent
Storage" aspect, because of the presence of Google (with Google Gears)
and HTML5 Proposal, as you can see from the "BONDI Interfaces Specs" at
http://www.omtp.org/Bondi/PublicDraft.aspx.

Please, let me know what you think.

Best Regards

---
Ivan De Marino
Orange Labs
Mobile and Web Software Engineer, R&D UK
tel. +44 20 8849 5806
mob. +44 7515 955 861
mob. +44 7974 156 216
ivan.demarino@orange-ftgroup.com
Received on Tuesday, 3 February 2009 11:20:34 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:29 GMT