Hi,
I recently created a store that loads tree branches on demand. It's working
fine, my doubt is how to organize the code.
Currently the new store is responsible for loading all items and adds an
listener (to each item fetched) on the "openChange" event to know when to
fetch the children of that item.
The problem is that each item will have an event attached. Do you see a
problem with that design or that's ok?
And I'm curious to know how the binding selection will work in that case
when qooxdoo will support remote fetching[1]. Because there will have
selected items that don't exist yet (not even its model).
[1] http://bugzilla.qooxdoo.org/show_bug.cgi?id=2993
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
