I'm currently working on a Flex project and need to show the content of a
dictionary (a xml file). After the creation of an Entry object for each entry
of my dictionary, the easiest way to display one entry is to use one Repeater
for the entry's attributes (each entry has got one or more attributes), one
Repeater for the attribute's items (each attribute has got items) and one
Repeater for the item's links (each item has got links). But as you can guess
it's not very efficient. I cannot harcode because my App must be able to
display any kind of dictionary which means different numbers of attributes,
items and links. Any idea ?




<mx:Repeater id="attributeRepeater"
dataProvider="{selectedEntry.getAttributesArray()} ">
<mx:HBox>
<mx:Label text="{attributeRepeater.currentItem.getName()}" width="80" />
<mx:VBox>
<mx:Repeater id="itemRepeater"
dataProvider="{attributeRepeater.currentItem.getIt emsArray()}" >
<mx:HBox>
<mx:Text text="{itemRepeater.currentItem.getName()}" width="400"/>
<mx:Repeater id="linkRepeater"
dataProvider="{itemRepeater.currentItem.getLinksAr ray()}" >
<mx:LinkButton label="{linkRepeater.currentItem.getName()}"
click="linkButtonHandler(event)" />
</mx:Repeater>
</mx:HBox>
</mx:Repeater>
</mx:VBox>
</mx:HBox>
</mx:Repeater>

"pbittner" <webforumsuser@macromedia.com> wrote in message
news:ge77no$cso$1@forums.macromedia.com...
> I'm currently working on a Flex project and need to show the content of a
> dictionary (a xml file). After the creation of an Entry object for each
> entry
> of my dictionary, the easiest way to display one entry is to use one
> Repeater
> for the entry's attributes (each entry has got one or more attributes),
> one
> Repeater for the attribute's items (each attribute has got items) and one
> Repeater for the item's links (each item has got links). But as you can
> guess
> it's not very efficient. I cannot harcode because my App must be able to
> display any kind of dictionary which means different numbers of
> attributes,
> items and links. Any idea ?

If you can pare it down to use Canvases or even UIComponents instead of
HBoxes and VBoxes, that will help performance a lot. Also, you might want
to look at setting the recycleChildren property to true.

HTH;

Amy

How can I use Canvases instead of Vbox and Hbox when I don't know how many
children my Canvas gonna have ?

And concerning the recycleChildren property, I've tried but the result is
completely wrong. I think that I cannot use it as each object repeated in the
repeater is different (it can have different children itself and not always the
same number of children).

"pbittner" <webforumsuser@macromedia.com> wrote in message
news:ge7dfc$kq5$1@forums.macromedia.com...
> How can I use Canvases instead of Vbox and Hbox when I don't know how many
> children my Canvas gonna have ?

Use an expression in the x and y field of the component that's being
repeated to lay it out properly.

> And concerning the recycleChildren property, I've tried but the result is
> completely wrong. I think that I cannot use it as each object repeated in
> the
> repeater is different (it can have different children itself and not
> always the
> same number of children).

You need to use invalidation to make sure that each object can refresh
itself when it's reused, similar to what you have to do when you make an
itemRenderer for a List based component.

HTH;

Amy

[q]Originally posted by: pbittner
I have tried to remove completely the Hbox and Vbox I'm using but it's not
quicker. The problem comes from the 3 Repeaters.

Concerning the recycleChildren property, I've tried but the result is
completely wrong. I think that I cannot use it as each object repeated in the
repeater is different (it can have different children itself and not always the
same number of children).
[/q]

Looks a complex scenario. You might want to consider Actionscript, which
enables much more control over instantiation, deletion and recycle.