- From: Scott Wilson <scott.bradley.wilson@gmail.com>
- Date: Thu, 19 Aug 2010 10:09:41 +0100
- To: Bernard Traversat <bernard.traversat@oracle.com>
- Cc: Rich Tibbett <richt@opera.com>, public-webapps@w3.org
On 16 Aug 2010, at 21:29, Bernard Traversat wrote: > On 8/16/10 2:34 AM, Rich Tibbett wrote: >> >> On 14/08/2010 03:12, Bernard Traversat wrote: >>> >>> Should we have a more explicit way to specify and notify users that some updates may require data conversion and >>> user data will be converted after the widget is updated? Due to the error-prone nature of such conversion, users >>> may want to back up their data before proceeding with an update. >> >> I'm not sure I understand what you mean. >> >> User data is not stored in a widget package itself. An update to an existing widget should be able to access the storage space used by previous versions of the same widget. >> >> If data conversion is required perhaps you have a use case we could look at. > The data conversion is the use case i was referring to. We should have a more explicit way to tell the end-users upfront that by installing the new update > his/her data will be converted with the potential risk of losing data and never going back to the older version. I think this UC is already covered by the Update Description Document; the widget author can put a warning in the details about the update, and the UA can then display that to the user. E.g. <update-info xmlns="http://www.w3.org/ns/widgets" src="http://evil-fruit-company.com/sins/unoriginal-patent.wgt" version="1.1"> <details> This update makes everything look really cool. Warning! This update will convert your existing data to a new format! </details> </update-info> > > Hth, > > B. >> >> Regards, >> >> Rich >
Received on Thursday, 19 August 2010 09:10:20 UTC