panyasan wrote:
>
> I just changed the demo to use 100.000 "spam messages". To generate them,
> you need a nested loop with timeouts:
>
> var x =0;
> for (var j = 1; j < 100; j++ )
> {
> qx.event.Timer.once(function(){
> for (var i = 1; i < 1000; i++)
> {
> dataModel.addLeaf(te, "Spam Message #" + (x++) );
> }
> },this,0);
> }
>
> otherwise there will be a script timeout. But once they are generated, the
> tree works very well, without any noticeable delay, except when you prune
> the node containing the 100.000 nodes (script timeout in Safari, Firefox,
> and Chrome) - which might happen just as well with the native array
> implementation.
>
> So even when I don't have exact tests, I think this casts doubt on the
> thesis that qx.data.Array doesn't work well with huge loads of data.
>
I'm impressed it works that well. Just thinking about the specific prune()
case... Wouldn't be interesting to deal with the parent reference in order
to avoid firing all the events on the children ?
Best,
Benoît.
--
View this message in context:
http://old.nabble.com/qooxdoo-contrib%3A-cometd%2C-Dialog-and-VirtualData-tp27005956p27026059.html
Sent from the qooxdoo-devel mailing list archive at Nabble.com.
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
