On Mon, Jul 11, 2011 at 2:07 PM, Jens <[email protected]> wrote:
> John, > > have you seen: > http://blog.stevenlevithan.com/archives/faster-than-innerhtml ? I found it > pretty interesting that you can speed up innerHTML by combining it with a > DOM operation. Although the website uses a nowadays pretty old browser > (Firefox 2) you can still get a 2x performance boost on the latest Chrome > Browser if the work gets large enough. > > Maybe its possible to integrate it into GWT and test performance again for > cell widgets with large data sets? > > Also there has been a small discussion on the Google Web Toolkit group > where someone creates a mobile application and uses CellTable. But that > results in a large javascript file because CellTable pulls in quite a lot of > code. Would the code size increase if you integrate the ElementBuilder API > into CellTable because then it can be build via setInnerHTML and Dom > operations? Mobile app developers want things as small and performant as > possible and may be shocked when using a cell widget and see a large compile > size increase just to get that "extra 2% performance". > For mobile, it might be even better to pursue server side rendering. That would eliminate all of the rendering code from the client, and it offloads the heavy DOM building process from the phone to a server. Of course, with dual core phones on 4g networks, I'm not sure how much longer its going to matter. > > -- J. > > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
