Hi Manish, thanks for your reply. Please see my comments below.

> Your custom shell can be a subclass of ViewStack itself. You can add
> the forward-back buttons into the chrome area of the component. I
> think either Accordion or TabNavigator extends ViewStack, so you can
> look at how that component is implemented and do the same.

That's definitely one possibility and I'm exploring it right now.
However, don't you think that I actually _must_ (not _can_) follow
this approach? I'm struggling to find any other plausible way to do
the shell. I would love to hear of any other approaches that cross
your mind (I'm still fairly new to Flex and maybe missing something).


> The child elements your component uses for its own purpose (like
> back-forward buttons) are known as the component's "chrome". You add
> the chrome using the allChildren (or rawChildren, whatever) API.
> 
> > Is there any possibility to extend ViewStack and enjoy the
> > benefits of design view/MXML at the same time?
> 
> Not sure about this one, but I think you should be able to enjoy
> design view for a ViewStack subclass as well.
>

If I understand this correctly, we can't leverage our designers'
skills and all the visual design stuff will need to be done in
ActionScript. Am I correct? If so, now you see why I would like to
know of any other possible approaches to this shell development thing.

Thanks,
Borek

Reply via email to