Hi Developers, For some time I have been wondering about qooxdoo scrollbar user experience.
If I have a large table and a not so fast browser and I try to use the scrollbar to move the content of the table, then the whole thing feels very slow. I think there reason for this is that the scrollbar mostly seems to reflect what has already happened in the scrolling area as opposed to what I intend to happen by moving the scrollbar. It is as if a button would only show the pressed state once all the events triggered by the execute event had completed. If this behaviour could be changed, I bet qooxdoo tables and other scrolly things would feel much faster ... I have not had a look at how the whole mechanism is implemented, this is just an observation from a users point of view. cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland http://it.oetiker.ch [email protected] ++41 62 775 9902 / sb: -9900 ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
