Maybe I don't understand your problem correctly but there is a demo [1] on the Qooxdoo demobrowser that seems to do what you want.
-deech [1] http://demo.qooxdoo.org/current/demobrowser/#data~Finder.html On Fri, Nov 12, 2010 at 5:16 PM, Greg Beaver <[email protected]> wrote: > Hi, > > I've been trying to solve a problem I have using qooxdoo for over 3 > months now with no luck. Any assistance modeling this properly using > qooxdoo would be helpful. > > Basically, I have a 3-tiered tree of data organized as follows: > > Composer > \-> Piece1 > \-> Movement > \-> Movement > \-> Movement > \-> Piece2 > \-> Movement > \-> Movement > \-> Movement > > and so on. However, to avoid taking up all of the available memory and > performance, the structure starts out as: > > Composer > \-> Piece1 > \-> Loading... > > and then I lazy-load the movements as needed. > > In a separate location, I store a program consisting of 3-4 pieces and > their movements that uses a Composer's/Piece's/Movement's ID to link > back to the tree above. I've designed a control that displays the > composer, piece and movements and allows editing them, which can then be > used in a qx.ui.form.List to display the program. Each of the three > things is displayed using some kind of list (selectbox or List) > > My problem is that no matter how I organize it, I can't get 3 > controllers to properly bind together. Thus, when the user changes the > composer, the piece controller and the movements controller should > update their models based on the composer's children. Sometimes, and > with no apparent pattern, no events are fired at all (as determined by > adding a listener on the composer's list controller). On a refresh, the > same conditions occur, but I can't find anything that is making the > event not trigger, because when I step through with firebug, an event is > always triggered. > > When I stopped using binding and instead tried to monitor change events, > the same problem occurred: no events fired sometimes. > > How should I be solving this? I need it to work ASAP, it's the last > thing holding up a major release. > > Thanks, > Greg > > ------------------------------------------------------------------------------ > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
