On Sun, May 18, 2008 at 1:01 PM, Manish Jethani <[EMAIL PROTECTED]> wrote: > Wrapping the view stack children into an array of plain objects is the > only way to do that, from what I know. > > Perhaps this would be cool: > > <ButtonBar id="buttons"/> > <ViewStack id="vs"> > <custom:Chart id="chart" icons="...."/> > <custom:Grid id="grid" icons="..."/> > <custom:Form id="form" includeInNavigation="false" /> > </ViewStack> > > i.e. a property that can mark a view to not be included in any > navigator controls.
Yes, something like that would be cool, although it would benefit from somehow more customization possibilities: what if I have several navigator controls associated with a single viewstack but want them to display different "child"? > But I think another way to achieve that is to simply not add the view > to the view stack. You can use states to declaratively add the form > view only later when the application switches to that state. Yeah, I hesitated about using states but, since ButtonBar and ViewStack are expected to play nice together (well, except if you want customization apparently), I investigated the viewstack approach. I'll investigate it later. Anyways, thank you for your time! Regards -- Fiouz
