Probably not since it's still the same problem in essence - that you are manipulating the DOM a lot.
Here are some things to try: Build the widget first using javascript & then add it as one thing (although if you still pass it off to TreePanel, it's probably not going to help since TreePanel will still build the model again). Use lazy panels (I think it's in 1.6 but it's also in the incubator AFAIK) + stack panel. That may work. Another trick might be to use a timer & incrementally add 1 results every 50 milliseconds or so. That should keep the UI responsive, although I'm not sure how IE will perform with a large tree once its there anyways. In fact, on the GWT incubator sight, it does seem like they implemented the lazy panel + stack panel idea anyways http://code.google.com/p/google-web-toolkit-incubator/wiki/FastTree - that sounds exactly what you're looking for. On Wed, Mar 11, 2009 at 1:49 AM, GWTFan <[email protected]> wrote: > > I read the thread > http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/22aecc7de7b8a92 > on tree performance. > > We are having a similar issue with the tree, where most of the cases > it would have 1-10 items. However rarely it would have 500-1000 items, > which slows down IE badly. > > Ours is just one level hierarchy and I don't really need tree. Do you > think using a stack panel would be faster than tree? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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 -~----------~----~----~----~------~----~------~--~---
