Hi Garth, Thanks very much for the lead. I am currently following the "anonymous" object advice but would like to investigate more ObjectProxy approach later once I have more time.
Just another quick question. It seems both approaches entail serializing objects in Flash Player at client side. Which one would be better performance wise if I will be dealing with a large collection of data (say 600-1000 per "page")? Best regards, geng --- In [email protected], Garth Somerville <therealga...@...> wrote: > > If the point of your question is that you are starting with anonymous objects, then wrapping each item with a mx.utils.ObjectProxy will do what you want by making each property of the proxied object bindable. > > The other alternative is not to use an anonymous object, but to create a concrete class for the tasks: > > class Task { > [Bindable] public var label:String; > } > > Ultimately this way is better for several reasons. (Note that as shown the mxml compiler will have to rewrite the class to implement IEventDispatcher) >
