I've had the same problem in an application for a customer that uses IE. Finally I've decided to create a paged table to show only a few rows in screen. In this way it's faster to render the table. It's a workaround, not really a solution, but it was acceptable for the customer.
On Mar 5, 3:47 pm, eadams <[email protected]> wrote: > After searching for additional posts on slow FlexTable performance, I > followed someone's suggestion to use Grid instead. A FlexTable wasn't > needed as the structure of the displayed lists is not dynamic. The > Grid displays a parts list of over 1000 parts in under 3 seconds. The > smaller lists (200-300) parts are under 2 seconds. The solution now in > place includes: > > Use Grid instead of FlexTable > Build the Grid before adding to the scroll panel or other panel > This was only an issue in IE > > Thanks, Ernie > > On Mar 5, 3:33 am, Lex <[email protected]> wrote: > > > Hello all, > > > And we are generating the Table HTML on server side, and put it as > > innerHTML and have performance 1000 rows - 3-4 second in IE. > > The biggest problem is using components which should handle events and > > placed in such table, but it seems JSNI is a solution in this case. In > > our case Links already working. > > So it seems this is the optimal solution if you need high performance. > > > On Mar 4, 7:36 pm, eadams <[email protected]> wrote: > > > > Thanks for the suggestions. > > > > Changing the code to add the FlexTable to the scroll panel after > > > loading the data resulted in a good improvement. The 268 row parts > > > list will now load in IE in just over 5 seconds. I tried the setVisible > > > () suggestion as well, but that did not yield much change. The changes > > > yielded an elapsed time of 0.3 seconds in Firefox. > > > > On Mar 4, 11:55 am, Lothar Kimmeringer <[email protected]> wrote: > > > > > eadams schrieb: > > > > > > The > > > > > timings showed the first third was in about 1.5 seconds, the next > > > > > third was in about 4 seconds and the last third in over 6 seconds. > > > > > This elapsed time is after thedatahas been received from the server > > > > > (which is also very fast). > > > > > > All of the above is on a Windows Vista client using IE 7. Testing the > > > > > same code on FireFox 3.0.6, the 268 rows display in under 1 second. Is > > > > > this a known problem with IE and are there any work arounds? > > > > > Unfortunately FireFox is not a solution for this issue as the > > > > > company's only approved browser is IE. > > > > > It's a rendering issue and not the only one. Try creating a > > > > Tree with 100.000 elements and have a look how much fun you > > > > have with InternetExplorer and Firefox (Safari is very fast > > > > here which makes me jealous). > > > > > One thing I haven't tried but you might try out is adding > > > > the flex-table to the panel after adding all rows. This > > > > might speed up things because InternetExplorer seems to > > > > redraw the whole table when adding rows (this is not GWT- > > > > specific, I had the same effects with other web-frameworks > > > > in the Good Old Days(R) as well). Or - if that has no effect - > > > > you might play around with setVisible. > > > > > Regards, Lothar --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
