Hi Kenny, I agree with Ralf. For larger projects, that use a modular structure, there will be nesting of containers (components). If you're worried about performance, opt to use the lightest-weight container that is necessary for the case (i.e. Canvas over Panel). Where possible, you can also set the width and height of containers and controls explicitly; to reduce the calculations for measure and layout.
-TH __________________________________ Tim Hoff Cynergy Systems, Inc. http://www.cynergysystems.com <http://www.cynergysystems.com> --- In [email protected], "Ralf Bokelberg" <[EMAIL PROTECTED]> wrote: > > What would be the alternative? I mean, if you need nested containers, you > need them. Our projects are nested 15 levels deep and more and i never found > that performance is bad. Premature optimization is the root of all evil :) > Cheers, > Ralf. > > > On 12/23/06, lostinrecursion [EMAIL PROTECTED] wrote: > > > > Hi all, > > > > Just a quick question about the Cairngorm Store. It is my > > understanding that the application was constructed to showcase some > > of the best practices in developing a Cairngorm project. > > > > With that in mind, I took note of some container nesting in the > > Store. I am a little confused because in some performance articles it > > specifically advises against the use of nested containers. > > > > I ask because I have some instances where a ViewStack in a panel > > would be ideal: For example, I have an application where access level > > controls the view inside a Control Panel. I'd like to bind a > > ViewStack selected index to the access level in my ModelLocator. > > > > I also would like to utilize a little nesting with Panels inside a > > VBox, etc. > > > > What's the jury say on this? Is there a happy medium on the subject? > > > > Thanks for any advice > > -Kenny/LIR > > > > > > > > > > -- > Ralf Bokelberg [EMAIL PROTECTED] > Flex & Flash Consultant based in Cologne/Germany >
