On Wed, Jan 6, 2010 at 02:16, panyasan <i...@bibliograph.org> wrote: > > Derrell Lipman wrote: > > > > The whole purpose of having bSelected in the data > > model is to allow the user to pre-select certain nodes. > > > > Since I am rewriting the SimpleTreeDataModel for databinding currently, I > wonder: doesn't this also apply for bOpened? Shouldn't a separate index be > kept for the opened state just as for the selected state so that when > cloning the data for databinding, one could very fast collapse the tree > without looping through the entire (possibly huge) tree array? >
If cloning is seen as an important issue, then pulling any attributes of nodes that should not be cloned out of the node array and into separate collections would be useful. I really don't think that's necessary. In 5 years, this was the first request to do this. Allowing for a remote data model for TreeVirtual would probably be more useful. In that way, two separate trees could use the same remote store, and gain nearly the same effect as cloning. That also seems to fit in better with what you're doing. Derrell
------------------------------------------------------------------------------ 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 qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
