I believe in using MVC in whatever way feels right for the application. A lot of times it's just easier to grab an instance of the model from wherever you need it.
That being said, whenever possible I try to follow the pattern of top level display objects referencing the model and then handing data out to its children. In your case I might put a variable referencing the model list in the objects contained in the dataProvider for the list and therefore have access to them in the data property of the itemRenderer as Tim mentioned above. On Fri, Jun 6, 2008 at 5:04 AM, Tim Hoff <[EMAIL PROTECTED]> wrote: > > Hey Jerry, > > No, referencing the model from anywhere in your application is the power > of MVC. Most times you can get what you need from data or listData in > an itemRenderer. But, there's nothing keeping you from using the model > any way that you need. > > -TH > > --- In [email protected] <flexcoders%40yahoogroups.com>, > "slash_n_rose" <[EMAIL PROTECTED]> > wrote: > > > > > Hi > > I'm using a Combobox control in my itemrenderer and its dataprovider > > is a Cairngorm ModelLocator variable. So my itemrenderer has a > > reference to ModelLocator. Is it a bad method by referencing model in > > Item Renderer,? If yes is there any other methods? Thanks in advance. > > > > Regards > > Jerry > > > > >
