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...@hotmail.com> 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 > >
