Hello Tobi, > Just read about the new virtual tree widget ! > > Very cool, this helps with large datasets as the dom manipulation > is done on a 'need to' basis and not all at once ... > > so I modified the sample in the demobrowser: > > http://tinyurl.com/5tgpezd > > to add 100'000 nodes to the Network node > > but no joy ... it takes my browser a minute todo that ... > > If you open the log window in the playground you can see that > preparing the array with data took less than a second > while the marshalling of the data took about 50 seconds > and appending the data to the existing tree took another 12 > seconds. I guess thats the price for having the tree react on every change in the model no matter where it occurs. The main problem here is that we have to create 100000 qooxdoo objects as model. But we need the objects because we need change events to react on. Maybe some day we can use __defineSetter__ for faking the events which would help but today, I can't see another solution. :(
> Doesn't this sort of defeate the purpose of the virtual tree/list. > > Are there any thoughs on how to make this more dynamic ? The only change i can see is to allow plain javascript objects. But again, with that, we would loos the change events and the possibility to react on model changes. Best, Martin ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
