Sorry, I don't have time to customize an example for you. I recommend looking at the differences between ListItemRenderer and TreeItemRenderer as a start.
________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of an0one Sent: Friday, June 20, 2008 8:59 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: How to compose a super tree item renderer using TreeItemRenderer and others Fine. Can you just show me a simple example of how to "Just add the label when you subclass". Real code is most convincing and helpful to me. And you blog is cool, but it just seems not so easy to dig up the specific snippet I need in a short time. Thank you again. --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , "Alex Harui" <[EMAIL PROTECTED]> wrote: > > There are no hard rules here. I'm a code minimalist and don't like > adding layers of code and display object parents unless it is really > important. Adding one child is not worthy of another layer IMHO, so I'd > just subclass, and I don't see why such a subclass wouldn't be reusable. > See the examples on my blog (blogs.adobe.com/aharui). > > > > The more stuff you add, the slower things get and more memory they take. > MXML is convenient, but not as efficient. It's up to you. If you do > composite, the trick should be propagating the data object from the > container to the children. > > > > Also, you should never call addChild in a constructor. We have a > component lifecycle documented for performance reasons.
