If you load that 16k items with GWT-RPC your first problem that freezes your browser is probably the deserialization process when receiving the answer from the server (converting the string received back to your object graph / list). So comment out all your tree stuff and first solve the freeze caused by the request itself. What you can try is to avoid GWT-RPC for this request and instead use plain JSON. If your browser freezes even with JSON then you have to load less data or live with the freeze. Keep in mind that an animated loading indicator (e.g. animated gif) will also freeze once the browser freezes because the browser does not have the time to animate the image.
Once you have solved the freeze caused by GWT-RPC you can optimize the tree view if you still see some freeze. A good way to optimize a view is to only add the specific data to the view that is currently visible or if you really need to add everything then use an IncrementalCommand with the Scheduler. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/J8eYjtC3xr4J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
