Derrell wrote:
> Yes, there are disadvantages as well as advantages to the virtual
> table. The time must be spent rendering at some point. That means it
> must be done either before the whole page is displayed (traditional
> table) or as you scroll (virtual table). The rendering speed is
> *greatly* influenced by what browser you're using. IE is painfully
> slow at rendering; in fact, after using firefox with gmail for a
> while, I recently had the displeasure of having to use IE to access my
> email. It was a thoroughly awful experience, due solely to the
> slowness of rendering in IE. Gmail isn't a qooxdoo application, but
> the same issues apply. Firefox is way, way faster than IE and I
> understand, but have not had the opportunity to experience for myself,
> that Webkit-based browsers such as Safari are much faster yet.
I'm using firefox for most develop work,the timings noted are from firefox
2.0.0.6, but i noticed no great difference with ie 7.
> One area to experiment with would be pre-rendering the next and
> previous "page" of data in the "background" so that scrolling is
> merely a matter of making the new rows visible or moving them onscreen
> or otherwise reversing whatever mechanism was used to hide them after
> their background rendering. The problem is that this could get in the
> way of user interaction if not implemented properly, and it might add
> quite a bit of complexity to the virtual table.
Hidden div's or a native clipping window would seem good solutions.
Simple solutions are allways preferred, but the constrains seem to force me to
use something more.
> If you are using IE, please try your application using either Firefox
> or a Webkit browser and let me know your results. If you had been
> using IE, I expect you'll be very pleasantly surprised. (Then you get
> to take on the unenviable job of convincing the users of your
> application that they should switch to a reasonable browser...)
already on firefox, but the client would strongly prefer a zero install
platform.
> If you'd like to take a stab at modifying the table widget to
> pre-render next and previous pages, I'll be glad to review your work
> for inclusion. It would need to provide enough benefit in "usability"
> and perceived speed, while still having code that's easy enough to
> maintain, but that may all be achievable. Let me know!
Currently our focus in on completing the project, but we're definitely looking
at this.
Cheers,
Derrell
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
