W3C home > Mailing lists > Public > www-forms@w3.org > March 2006

Re: "Tracking" submission progress?

From: John Boyer <boyerj@ca.ibm.com>
Date: Mon, 27 Mar 2006 11:49:45 -0800
To: "Allan Beaufour" <beaufour@gmail.com>
Cc: "Mark Birbeck" <mark.birbeck@x-port.net>, www-forms@w3.org, www-forms-request@w3.org, w3c-forms@w3.org
Message-ID: <OF1576687A.26033D53-ON8825713E.006C9934-8825713E.006CEF4C@ca.ibm.com>
Rather hoping for the event-based approach of having 
xforms-submit-progress where
the event context contains bytes received and, if available, download 
size.  Also need
upload size and progress.

If you have these available from event context, then you can easily hook 
the event
and use setvalue action to write them to any instance data you want, which 
can then
drive a range as you described.

This way, we only have to explain one way in which submission progress, 
and use of 
event context means you can get info about upload and download. 

Mark, is this part of your 1.1 submission spec?  I really hope so.

John M. Boyer, Ph.D.
Senior Product Architect/Research Scientist
Co-Chair, W3C XForms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com  http://www.ibm.com/software/

Blog: http://www.ibm.com/developerworks/blogs/boyer/index.jsp

"Allan Beaufour" <beaufour@gmail.com> 
Sent by: www-forms-request@w3.org
03/24/2006 03:47 AM

"Mark Birbeck" <mark.birbeck@x-port.net>
Re: "Tracking" submission progress?

On 3/24/06, Mark Birbeck <mark.birbeck@x-port.net> wrote:
> > How about adding a "progressvar" attribute to submission.
> We had been thinking just the same thing!

Heh. Brilliant minds get brilliant ideas ;-)

> Our approach was to do it via events though--have an
> "xforms-submit-progress" event that fires periodically, and one of the
> properties on the Event object would be the number of bytes transferred 
> far, and another would be how many bytes should be transferred in total. 
> could then use the event and the values to do whatever you wanted, such 
> your example of showing a progress bar.

That's also a good idea! How about having both?

I really like the simplicity in just adding a var and binding a range
to it. (there's a thing about how to make the range readonly, etc...
but still).

> (It's also worth noting that a progress event is one of the things that 
> WEBAPI group are talking about adding to good old XmlHTTPRequest.)

Oh well, "let's do it too!" :)

... Allan
Received on Monday, 27 March 2006 19:50:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:16 UTC