No example here, but no, he does not mean using mx:Model. I advise avoiding that class entirely. It gives you the worst of both worlds, the performance problems of dynamic objects, and the lack of search, filter and navigational functionality (vs XML).
The term "model" is used generically, to mean a representation. If your data is hierarchical, then XML can be a model. If it is a list of things, then an ArrayCollection of "Thing" objects can be the model. Google "MVC", you'll find plenty of descriptions of this pattern. Tracy ________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of djbrown_rotonews Sent: Tuesday, March 11, 2008 2:32 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Accordion question that sounds like a better solution :) Do you have some sample code that would illustrate this? Is it using mx:Model? --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , "Alex Harui" <[EMAIL PROTECTED]> wrote: > > These days, we are pushing everyone to use a model-view or > model-view-controller (MVC) architecture. > > > > If you did, you would store the combobox selection in the data model and > all views would be bound to that slot in the model. > > > > ________________________________ > > From: flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> [mailto:flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> ] On > Behalf Of djbrown_rotonews > Sent: Tuesday, March 11, 2008 7:18 AM > To: flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> > Subject: [flexcoders] Accordion question > > > > I have a GUI that has a "Tabbed view" and a "tiles view", both as > children of an Accordion (the tiles view is just a repeater inside of > a vbox as opposed to an actual tile list). > > Anyhow, each component has a few combobox pulldowns etc.. I want to be > able to "synch" up those selections, so that when the user switches > from tabs to tiles that the menu selections are preserved and > displayed in the new view. > > I've messed around with placing some code to do this inside the change > event handler of the accordion itself (iterating over the children, > grabbing the menu selections etc..). Is that the easiest way to do it? >
