And to put the icing on the cake... The deal is the LayoutManager loves the IUIComponent interface which has another buddy called IFlexDisplayObject.
IFlexDisplayObject is instrumental in coupling measurements plus nesting levels that the layout manager needs to do it's queue sorting when laying out display objects. Navigators need Container children because Container is hard coded into them all. :) They have implemented IContainer and added some members to it. I hope they get all these concrete references out of the framework eventually. If the Flex framework is going to be really successful in the long run, everything needs to be renderers/factories and interfaces. I got three years on riding Alex's coattails in this area. ;-) Like how about IScrollContainer... this is in my framework now. Mike On Thu, Oct 16, 2008 at 2:06 PM, Tracy Spratt <[EMAIL PROTECTED]> wrote: > I think that is correct. Quoting Alex, "Navigator children must be > Containers, Container children must be IUIComponents, and UIComponent > children can be anything." > > Tracy > > > ------------------------------ > > *From:* [email protected] [mailto:[EMAIL PROTECTED] *On > Behalf Of *Amy > *Sent:* Wednesday, October 15, 2008 11:36 PM > *To:* [email protected] > *Subject:* [flexcoders] Re: Efficiency and objects in the display list > > > > --- In [email protected] <flexcoders%40yahoogroups.com>, "Tracy > Spratt" <[EMAIL PROTECTED]> wrote: > > > > Container children must be UIComponents. You will need to add the > > sprites to a UIComponent first. > > I think technically there's just an interface that has to be > implemented on whatever you add (IFlexDisplayObject? IUIComponent?). > If you extend Sprite or whatever and implement whichever one is needed, > you could add it to a container. > > -Amy > > > -- Teoti Graphix, LLC http://www.teotigraphix.com Teoti Graphix Blog http://www.blog.teotigraphix.com You can find more by solving the problem then by 'asking the question'.
