thanxs
and also having some kind of a stateVo to store a few configs in.
well, there already is a stateVO that you can subclass.
Its interesting that what I have read here so far, is that states seem to be very much linked with the view (including in the flex framework). I tend to see it as more general than that. I have a "bootstrap" state that manages the start up; or a "save" state that manages saving out data; or an "edit" state that switches the view state...