Uploader state control

[Eli Cochran]

Jacob,
You and I discussed this but maybe you didn't realize what I was  
talking about.

The state of the Uploader UI is complex and subtle. When I was  
developing it originally it made sense to use CSS to set the various  
states of things since the Uploader had so many varied states.

In terms of performance it rips since most browser CSS frameworks are  
very very fast.

I also felt that it actually would put more power in the hands of the  
developer since instead of changing a bunch of JS, you could just  
manipulate some CSS to get to the same effect.

However, as the Uploader has become both more modular in code and even  
more complex in state, what is really needed is a JS solution for  
setting these various states. There will still need to be a fair  
amount of CSS, but at a level closer to the elements and not as high- 
level.

- Eli

On Oct 29, 2008, at 1:16 PM, Jacob Farber wrote:

> Hi Guys,
> Im still cranking away at Uploader, and I've come to a point where  
> I'm a little perplexed and I was hoping you (or anyone) could help me.
> I've noticed the root of the Uploader markup has one of a few  
> classnames ('start', 'loaded', etc) attached to it that, when  
> changed, controls the UI and other things.
> I was wondering how we got to that decision, since as I'm writing  
> some CSS I'm finding that I need to scope all my selectors to these  
> classnames if I want them to behave properly.
> Is there any particular benefit to doing it this way, as opposed to  
> using JS to manipulate state directly?
> Thanks
> Jacob
>
> -- 
> Jacob Farber
> University of Toronto - ATRC
> Tel: (416) 946-3002
> www.fluidproject.org
>

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

Eli Cochran
user interaction developer
ETS, UC Berkeley


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20081029/f69fe1ca/attachment.htm>