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

Re: "Tracking" submission progress?

From: David Landwehr <david.landwehr@solidapp.com>
Date: Tue, 28 Mar 2006 07:44:47 +0200
Message-ID: <4428CD4F.4000004@solidapp.com>
To: John Boyer <boyerj@ca.ibm.com>
Cc: Allan Beaufour <beaufour@gmail.com>, Mark Birbeck <mark.birbeck@x-port.net>, www-forms@w3.org, www-forms-request@w3.org, w3c-forms@w3.org

It would be very good if the 'upload progress' and 'download received' 
was two different events, which will make it easier to write actions for 
controlling the UI.

Best regards,
David

John Boyer wrote:
>
> 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.
>
> Cheers,
> 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
>
> 	
> To
> 	"Mark Birbeck" <mark.birbeck@x-port.net>
> cc
> 	www-forms@w3.org
> Subject
> 	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 so
> > far, and another would be how many bytes should be transferred in 
> total. You
> > could then use the event and the values to do whatever you wanted, 
> such as
> > 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 the
> > WEBAPI group are talking about adding to good old XmlHTTPRequest.)
>
> Oh well, "let's do it too!" :)
>
> --
> ... Allan
>
>


-- 
--------------------------------------------
David Landwehr (david.landwehr@solidapp.com)
Chief Executive Officer, SolidApp
Web: http://www.solidapp.com
Office: +45 48268212
Mobile: +45 24275518
--------------------------------------------
Received on Tuesday, 28 March 2006 05:44:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:22:03 GMT