Hi Igor, Sizes are fine - I'm already using percentage widths. The problem is sometimes I want the component to use a tabNavigator and sometimes I want it to use a linkBar, etc. The basic criteria is the 'outermost' component on the page should use a TabNavigator, and components inside that should use a linkbar. Having mulitple tabNavigator components 'inside' each other is just looking nasty - and is rather confusing. So if I'm using the component 'stand-alone' - it should have a tabNav, but if I stack it inside another component, it should use a more discreet nav.
The problem boils down to: How can I make the components container 'selectable' at run-time? So I can something like: <ns:MyComponent nav_interface="tab" /> or <ns:MyComponent nav_interface="buttons" /> I've thought about using addChild to build the components dynamically - but that seems like over killl.... On 12/1/06, Igor Costa <[EMAIL PROTECTED]> wrote:
Steve Nope you don't have to create 2 or 3 types of version, you just be more reusable as possible just setting the width and height size for percentage. Due to you can uses in other containers that you specifies the sizes and positions. Best. On 11/30/06, Steve Hindle <[EMAIL PROTECTED]> wrote: > > Hi All, > > Anyone got any good design patterns for building components that can > be stacked inside other components and still look good visually? I'm > ending up in nested tabNavigator hell... > > When you build components that can be used both stand-alone (top > level) or included _inside_ another component - how do you organize > the component, and what nav containers do you use ? > > Do I really have to create 2 or 3 versions of the component (with > tabs,with linkbar, with...) > or is there a way of switching the container at runtime? ( I thought > about building dynamically with addChild, getting the navcontainer to > use from a property...) > > Thanks! > -- ---------------------------- Igor Costa www.igorcosta.com
