But how would I setup the binding in the tabnavigator so that the first tab the list of rooms never goes away? I can't just set it to a arraycollection of the rooms in the model since that will wipe out my room list that I always want to be there. The only solution I can think of is to implement a viewcontroller that listens for a an event that is fired from the command that the model has been updated with the new room which then tells the view to run through the room list and add any rooms that don't already exist. This seems like a lot of extra work. Anyone have a cleaner method?
Thanks --- In [email protected], "Ralf Bokelberg" <ralf.bokelb...@...> wrote: > > It would be in the spirit of Cairngorm to fire off a EnterRoom event, > which triggers a EnterRoom command. The command calls a enterRoom > method in some model. The TabNavigator binds to this model and > updates itself, whenever the model changes > > With kind regards, > Ralf. > > On Sun, Jan 4, 2009 at 7:49 AM, someguy7_7 <mus...@...> wrote: > > I am trying to determine the best way to use cairngorm for the > > following use case. I want to display a tabnavigator that only has 1 > > child which is a component that has a list of rooms in a datagrid. > > When one of the rooms is clicked a instance of the room component is > > added to the tabnavigator as a child. The room component just has a > > label that says "You are in room xxxxxx". Can I just fire off a > > regular event from the room list component that the main view is > > listening for so it can add the new child to the tabnav or do I need > > to fire off a cairngorm event that goes through a command which > > somehow gets back to the view and tells it to add a new child to the > > tabnav? > > > > Any ideas on the best way to set this up so it does not violate the > > spirit/laws of cairngorm? > > > > Thanks > > > > >
