Hey, > 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? Does that mean you attach a listener from the store to the view directly? Usually, all changes have to go threw the model.
> 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). I haven't made up my mind about that but my first idea is to add a special data array which is capable of the connection and can fetch data using the store. With that, the tree controller only needs to be aware of async data requests. All the other stuff could be done by the data array in combination with the store. As I said, just a first Idea which needs to be further time to develop. Regards, Martin ------------------------------------------------------------------------------ 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
