W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2009

Re: Using progress events for other purposes

From: Charles McCathieNevile <chaals@opera.com>
Date: Sun, 18 Oct 2009 17:48:04 +0200
To: "Charles McCathieNevile" <chaals@opera.com>, "Ian Hickson" <ian@hixie.ch>
Cc: "WebApps WG" <public-webapps@w3.org>
Message-ID: <op.u1z56e1ewxe0ny@widsith.local>
On Sun, 27 Sep 2009 21:04:04 +0200, Charles McCathieNevile  
<chaals@opera.com> wrote:

> On Sun, 27 Sep 2009 20:20:52 +0200, Ian Hickson <ian@hixie.ch> wrote:
>> On Sun, 27 Sep 2009, Charles McCathieNevile wrote:
>>> The alternative is to think now about extending Progress Events to deal
>>> with non byte-length progress (e.g. a series of transactions, each of
>>> which is very rapid alone but which add up to minutes).
>>> My preference would be to create new attributes for this case rather
>>> than overload the total/loaded attributes.

I propose to add the attributes totalItems and loadedItems to preogress  
events, as a way of dealing with use cases like showing progress in  
downloading an application cache. This allows for firing progress events  
which have total/loaded values on individual items, by defining them as  
referring to the current item in the presence of the totalIems /  

Does that work for the use case?

>>> I have raised ISSUE-105 for this question.



Charles McCathieNevile  Opera Software, Standards Group
     je parle français -- hablo español -- jeg lærer norsk
http://my.opera.com/chaals       Try Opera: http://www.opera.com
Received on Sunday, 18 October 2009 15:48:46 UTC

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