Dev Iteration 35

[Eli Cochran]

Just to clarify... new Progress for Uploader is a two step re- 
factoring, with only the first step being done during this iteration.

The steps are:
- pretty much a complete rewrite of how we manage the tracking of  
progress/status in Uploader
- implement Erin's new Progress design on top of the new status code.

Below is my list of the things still to do on Uploader. Almost all of  
this list is reflected in a bug, task or sub-task in JIRA but here it  
is in one place:

- re-factor internal status
- implement new Progress using new status
- surface error handling into user feedback
- expose server-side errors in client (this is going to be tricky  
because of a Flash problem)
- add automated testing
- ARIA markup
- additional keyboard support
- validate multi-instance support
- create a dialog flow version of the reference application
- simplify and re-factor code and API

Onward,
Eli


On Jun 4, 2008, at 9:59 AM, Michelle D'Souza wrote:

> Hi everyone,
>
> We are planning to keep this iteration super short (4 days) and sink
> up with the design iterations again. The two main goals of the
> iteration are to work on the Uploader's progress and get a start on
> the inline edit component.
>
> We have a JIRA filter where you can see our progress:
> http://issues.fluidproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=10064
>
> I'd like to schedule the dev iteration 36 planning meeting for next
> Tuesday after stand-up. 12:00 EDT  Let me know if this time is not  
> good.
>
> Michelle
>
> ------------------------------------------------------
> Michelle D'Souza
> Software Developer, Fluid Project
> Adaptive Technology Resource Centre
> University of Toronto
>
>
>
> _______________________________________________
> fluid-work mailing list
> fluid-work at fluidproject.org
> http://fluidproject.org/mailman/listinfo/fluid-work

. . . . . . . . . . .  .  .   .    .      .         .              .                     .

Eli Cochran
user interaction developer
ETS, UC Berkeley