Uploader Status

Eli Cochran eli at media.berkeley.edu
Tue Mar 17 14:39:57 UTC 2009


Upload with Error
Yesterday, I added error text for the Uploader for files that error  
during upload as per the Upload with Error storyboard.

I got pretty deep into implementing individual Retry buttons for each  
row, however I ran into two problems:
- Accessibility Design: our keyboard selection pattern for the file  
queue assumed that there was only one action that one could do on a  
row, delete. Adding the Retry button made things ... interesting. More  
like a table with rows and cells, I think but I need some help talking  
through it.
- Code: doing a uploadManager.start() for an individual file was  
having to touch more and more code, and at 11pm I panicked and backed  
out. I think that I was close but it didn't feel production worthy.

Next Steps: It would be pretty easy to implement the general Retry  
button for the whole queue based on the code that is already there. A  
general Retry is part of the design but I need to talk to Erin and  
Daphne about whether it is acceptable to have general retry without  
ind. file retry and I need to talk to Justin about slipping this in  
after feature freeze.

Cancel and Done
Last week, Colin and I were still debating whether the Cancel and Done  
buttons made sense as part of the template for the Uploader or if they  
were better implemented in an example. And since the only example of  
the Uploader we have is the Image Gallery, I tried implementing Done  
and Cancel as series of added listeners in the Image Gallery code. But  
some combination of stale code in the Image Gallery and stale code in  
my brain at midnight made that a non-starter, I just couldn't get the  
Image Gallery to pass in a listener correctly. The ones that are there  
don't actually seem to be working, but when I updated them the way I  
thought that they should work, it didn't work.

Next Steps: I'd like a little help figuring out what's happening with  
the listeners in Image Gallery and going over my approach. This would  
probably be better in a Springboard but I don't think we have time to  
pull one off.

The code that I used to implement Cancel and Done as buttons in the  
template is stored away in a patch. It wouldn't take much to clean it  
up and plug it in. But it's still debatable whether this is the right  
approach.

Flash 10 bugs in bug parade:
I'd like to go ahead and engage Markus from the OpenCast project on  
fixing these bugs. I think that we have enough information to have a  
reasonable conversation about the options. Colin, you and I should  
should sync up quick so that we have an understanding as to which  
options we'd like to pursue. However, Markus may have some ideas and  
suggestions for us as well.

On to bug parade.

- Eli




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

Eli Cochran
user interaction developer
ETS, UC Berkeley


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20090317/51b52fa2/attachment.html>


More information about the fluid-work mailing list