Thats actually a really good idea Tracy, thanks. Not
sure why it
didn't occur to me :)
That approach still leaves me with my biggest question though, which
is how to handle updates to the data. My app is basically a document
generation workflow, so the user will be moving (possibly large) sets
of documents through different steps that happen on the server, and
we'll be polling for status updates and whatnot. So when a result
returns from the server, would I just push out the new data to the
collections? Or perhaps I could bind the collections to the master set
somehow?
Thanks,
Ben
--- In [EMAIL PROTECTED]ups.com,
"Tracy Spratt"
<[EMAIL PROTECTED]> wrote:
>
> Could you use e4x xml as the master data, then use the node selection
> sepressions to return the xml or XMLList you want, and put that data
> subset into an XMLListCollection to take advantage of the cllection API?
>
>
>
> Tracy
>
>
>
> ________________________________
>
> From: [EMAIL PROTECTED]ups.com
[mailto:[EMAIL PROTECTED]ups.com]
On
> Behalf Of ben.clinkinbeard
> Sent: Monday, October 23, 2006 11:30 AM
> To: [EMAIL PROTECTED]ups.com
> Subject: [flexcoders] One data set, multiple DataGrids/views- best
> approach?
>
>
>
> In an upcoming project I will need to provide multiple views of the
> same data, most likely in the form of an XMLListCollection, in
> multiple DataGrids. The scenario is that I will have a large master
> set of data, but depending on which screen you are on you will only
> see the appropriate parts of the data (proposed documents, generated
> documents, approved documents, etc). I will also be using some
> compound filterFunctions, so that on the screen displaying only the
> approved documents, the user can additionally filter by document type,
> etc.
>
> My question, finally, is what is the best way to approach this? I have
> toyed with the idea of making a copy of the data for each screen, but
> that seems error prone and hackish as the data will be updating while
> the application is being used. Should I change the filterFunction
> being used when the user switches screens so I essentially have one
> DataGrid shared between screens and the 'multiple views' is faked?
> Should I break the data into pieces? Any advice or guidance is greatly
> appreciated.
>
> Thanks,
> Ben
>
