Re: [flexcoders] Cairngorm: should pure view state changes go through the ModelLocator?

2008-10-24 Thread Farid SALAH
Le 24 oct. 08 à 03:48, Dimitrios Gianninas a écrit : #2 because your app is simple..#1 if you want to be a purist. start simply and add complexity as you go along, thats my rule. That's a good rule ! If your 2 components in your view are in the same component, let's say whatever Panel or

Re: [flexcoders] Cairngorm: should pure view state changes go through the ModelLocator?

2008-10-24 Thread Fro Rosqueta
I also vote for #2. Seems strange for me to have a boolean in the ModelLocator that is specific to this UI context. I always thought the ModelLocator should only have data that is potentially global to the app (like your list of users), and find it strange that many online Cairngorm examples put

RE: [flexcoders] Cairngorm: should pure view state changes go through the ModelLocator?

2008-10-23 Thread Dimitrios Gianninas
#2 because your app is simple..#1 if you want to be a purist. start simply and add complexity as you go along, thats my rule. Dimitrios Gianninas RIA Developer Team Lead Optimal Payments Inc. From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On