|
Here's what I'm getting from all the manual reading I've
been doing over the past week. Others may correct me or clarify as
needed.
- Think of the base state as the "home page"... it's the
initial state of the app or component when the user browses to it. I can't think
of a good reason why it would ever be empty unless you wanted to implement some
kind of transition or effect immediately upon loading it.
- In the larger sense of UI design, HTML "pages" are
addressed in the Flex metaphor with ViewStacks attached to a navigator. Use this
for macro changes in the interface.
- View states are used to display incremental changes in
state. Sounds like you are using that correctly insofar as you describe it...
however, depending on how your user interface is designed and what you're trying
to accomplish, the "Detail" state you describe could also be just an incremental
change to the "Master" state with the Master state remaining visible. Also, the
"Master" state could be your base state since it's empty and that's the first
thing the user sees.
Also, and more generally, don't forget that Flex
development is based on components. So it may be appropriate to shelter
your calendar "module" in a component if you haven't already done
so...
Kevin
__._,_.___ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com YAHOO! GROUPS LINKS
__,_._,___ |
- [flexcoders] Am I using States correctly? gotgoose09
- RE: [flexcoders] Am I using States correctly? Kevin Mulvihill
- [flexcoders] Re: Am I using States correctly? gotgoose09
- RE: [flexcoders] Re: Am I using States correc... Kevin Mulvihill
- Re: [flexcoders] Re: Am I using States co... Tom Chiverton

