On Fri, Apr 18, 2008 at 6:50 PM, Tracy Spratt [EMAIL PROTECTED] wrote:
dataprovider again, right? I had assumed that implementing a dataprovider
would make updates to the UI cleaner (not having to re-create all items),
but I could be wrong on that assumption- don't know yet.
I like to do it
On Sun, Apr 20, 2008 at 9:38 PM, gabriel montagné [EMAIL PROTECTED] wrote:
I like to do it like this:
_dataProvider = (value is Array)? new
where _dataProvider is typed IList..
... pretty useful and flexible... I'd read it (or something like it)
on one Ely Greenfield's
Just implement a public setter function on your component that takes
XML.
In the setter, launch your child instantiation code. I have done this
and it can be a bit complex, but is not hard.
Tracy
From: flexcoders@yahoogroups.com [mailto:[EMAIL
Hey Tracy,
I thought of that but it seems to limit me from what I'm trying to do. I
need the UI of this component to respond when the dataprovider changes, I
figured the best way would be to implement a dataprovider the way the mx
components do it, it seems complicated but I'm getting throught
to the model change.
But if you are on track, then keep going.
Tracy
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Derrick Anderson
Sent: Friday, April 18, 2008 8:02 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] custom
5 matches
Mail list logo
