The states as used in Cairngorm will not correlate with the
in Flex 2. The serve different purposes. Well let me
step back and say, this is how I feel about it.
Flex 2 states are good for view/control states where Cairngorm
workflow states are just that work/process flow.
Thats not to say yo
Thanks for the input. Maybe I've been misunderstanding the way to use
them from the beginning. ( very possible )
Let me give a better example, to make sure i'm not way out in left field.
This is a typical way I manage the state.
Model:
public static var workflowState:Number = 0;
p
Chris,
What I usually do is have something like:
...
And at the creation complete of the application I"ll simply put:
model.selectedState = model.SOMESTATE;
Then whe
The main thing here is if you use Views with ViewHelpers you should
have those as separate views and not use . States in my
preception are more for UI changes within a view then what the
switching containers or larger sets of UI.
Now this is not to say you can use the States for changing containe
Thanks for the input Brennan,
This makes sense because once you get into the child components,
this.currentState I believe refers to the component itself and not the
application.
So would you have the view update the model directly or would you
have a command that updates the model?
Thanks for
That makes sense, I guess I'm a little confused because the coldfusion
application wizard generates a "login" state and "mainApplication"
state and that's where I saw the first real implementation of states.
I do realize that it could be done any number of ways, I was just
looking for some input a
I am facing the same question. "What is the best way to manage
application view states with Cairngorm2?"
The pattern where you use
> > Model:
> > public static var workflowState:Number = 0;
> > public static var VIEWING_SOMETHING:Number = 0;
> > public static var VIEWING_SOMETHING_ELSE:Number =
7 matches
Mail list logo
