TreeView hangs in IE slow in others

0
0

I have attached a sample app that shows the behavior that is happening.  In the sample there are buyers (20 Nodes) and sellers (1500 nodes).  When expanding the byers node it works fine.  When you expand the sellers node it hangs in IE and never comes back in chrome it takes about 10 seconds and keeps causing a lag in the application.

Please help solve this as it is an important part of the application.

Thanks -Tim

Attachment
TreeView.zip
Bugs
Share
  • You must to post comments
Filter
Sort by: Recently Active
0
0

I can reproduce with IE. With Chrome for me it takes about 2-3 seconds. The problem is that it’s many nodes, each node has a child too so it’s over 3,000 widgets. We use the regular Tree widget because it’s the most flexible for rendering.

There is an alternative options for the client widget for the TreeView, the ComboBox and the ListBox to use the virtual renderers in qooxdoo. They work in a way similar to the DataGridView and create the html elements only for the visible view so instead of 15,000 dom elements (3,000 x 5 elements each) they create few hundreds. The grid is able to display unlimited rows.

I can send you a sample next week.

 

  • Tim Larson
    Thanks for looking into it. I would like to see the sample of what to do. The performance really starts to slow down around 300 nodes being added. Again thank you in advance for the sample. Tim
  • Tim Larson
    Luca, Were you ever able to come up with a sample for this? I am circling back on this and need to get it working faster. Thanks, Tim
  • Luca
    • Luca
    • Apr 13, 2018 - 5:53 pm
    Unfortunately it’s not as simple as I thought and not just a sample. It’s a different javascript class that behaves a bit differently since it uses the virtual rendering system in qooxdoo (like the one in the DGV and the ListView in item mode) so it needs to more wiring. I’d say in 2-4 weeks.
  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.