Thnx for replying all. It really helped me a step further.
>I searched Google for "_measuredPreferredWidth" and unfortunately found only a single page of results. :( >http://www.google.com/search?q=_measuredPreferredWidth >http://search.yahoo.com/search?p=_measuredPreferredWidth > >Anyway, here's a nice article about how to create components: >http://www.macromedia.com/support/documentation/en/flex/1_5/createcompo nents/ According to the article: these properties, but you can override them in the measure() method: _measuredMinWidth _measuredMaxWidth _measuredMinHeight _measuredMaxHeight _measuredPreferredWidth _measuredPreferredHeight The properties define limits for when the object is resized. These measured properties are used for layout in containers if your component doesn't explicitly set a preferredWidth or preferredHeight attribute. I think this information is missing the part where they explain what function these properties have exactly. >Then when the container is getting initialized, it looks at the >object descriptors and created its children using createChild() > >You can see how the descriptors are set up by setting the following >option in flex-config.xml > > <!-- write xxx-generated.as file to disk --> > <!-- These files are generated by the compiler during mxml translation. --> > <keep-generated-as>true</keep-generated-as> > >Then you can open the MyMXMLFile-generated.as file to see the translated >AS code. Look for "Descriptor" in that file to get an idea. Yeah I have seen these pieces of code. I was however wondering how I this information was processed internally so I could create my own version for that. In some cases its preferable to create these childs not directly into the component but into a holder. For the developer using your component it should look like the children of the component itself. >There may be many, but if they are not in the ASDoc then one has >to assume they were not meant for public use. Well these undocumented function are used in components themselves. So they are public and part of the framework, else the should not be used in components. I agree with u that they are not public for developers wich use the components, but if u are creating components within the V2 framework, these methods are perfectly good to use. In order to make good V2 components we need to know about these methods. >> These classes are not included in the FlexForFlash.zip file while they >> can be valuable to the development of good UI components. Does any1 >> know why? > >No idea. :-/ Thnx to the tip of one of u, I have managed to get the source of these classes, wich I can use to gain more knowledge of the V2 framework and be able to create more solid components. >When you resize a child in the box, its parent's "layout" needs >to be redone, so Flex remembers this and calls the parent's layoutChildren() >on the next frame. In the layoutChildren() of the Box container, it >calculates the sizes of its children and lays them out accordindly. > >This happens for any Container, not just Box. U say "Flex remembers this", but how is it done? Via an event? I mean how does the parent container know one of its children is resized? Is it automaticly registering itself as listerer for the size event? >> 6. >> >> In the documentation of the V2 architecture I miss the overview. I see >> a lot of examples of parts of the framework, but I don't see a list of >> goals connected to the theory of its implementation. It seems in the >> general documentation everything is ordered by feature and in >> component creation documentation all simple features are included and >> minimaly explained (think init, createChildren, measure, etc.). >> >> Im missing a structured view of how the framework is tied together. >> From concepts all the way down to parts of implementation code in components. > >Have you read this book? >http://www.amazon.com/exec/obidos/tg/detail/-/0321255666/qid=1116262210 /sr=8-2/ref=pd_csp_2/002-2276896-9552008 >I haven't, but I hear it's great. Some of the chapters are now becoming available online too. >http://www.macromedia.com/devnet/flex/articles/component_reuse.html I have that book on my table yes, but this book doesn't go in on the creating of Actionscript components, or how the V2 framework internally works. Thnx again for your reply. Greetz Erik Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
