Comment by [email protected]:
@johan: The short answer is yes. Here's the reason: What's visible on the
screen can easily be ~20x50 cells in a table, and that can be surprisingly
slow to render using individual calls to td.setInnerHTML(), and even worse
if you're using entire widgets and the bookkeeping that entails. For
example, if you look at the AdWords Campaign Management UI, they've had to
do a fair amount of work to optimize their table rendering, using a similar
approach. We're working hard to codify it in a way that makes the fastest
thing the *easiest* thing, which frees up cycles to do other work.
The code in /bikeshed is all over the map right now, as we experiment with
different ideas, but we're settling on a "cell" abstraction that looks like
it's going to work out really well in practice.
For more information:
http://code.google.com/p/google-web-toolkit/wiki/DataBackedWidgetsDesign
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
