If you look at ClassFactory, it has a properties map that will copy any
properties in the map to each instance. This is different from
assigning it to the data objects in the dataprovider, which you don't
want to do because you're trying for a clean model/view design. With
repeaters, you are essentially generating view instances.
If your renderer had a property called "thumbnailViewer" that pointed to
something you wanted to customize, then you can assign to the
ClassFactory properties= {"thumbNailViewer", myThumbNailViewer} and it
will essentially give every instance of the renderer that reference.
________________________________
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Amy
Sent: Thursday, January 17, 2008 7:24 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Passing additional information into renderer
--- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com>
, "Alex Harui" <[EMAIL PROTECTED]> wrote:
>
> You can customize the properties bag on the class factory to supply
more
> info to each instance.
If I understand you correctly, you're saying that I should repeat the
folder information in each object in the data source. To me, that's
sort of a hack...it should be possible for the parent container to pass
this information in easily, like you can with an itemRenderer in a
Repeater.
Why is it that it is so much easier to pass information to
itemRenderers that are used in a Repeater? You can essentially tell
them anything you want. It seems like it is prohibitively hard to
cleanly pass data in the List type containers.
Thanks;
Amy
