Hello,
Unfortunately, my first Flex application is probably going to be
pretty gnarly. After reading up on the basics, I did some rapid
hands-on prototyping and quickly found the main "Application" mxml
will quickly become a beast. I've decided that my next step is to
really map out my architecture and figure out how I can keep
everything orderly.
Seems like the tools I really need to leverage for this are
Application, ViewStack, State and Component in no particular order. I
also think "code behind" will come in handy. Here's a tree structure
of how I think I'm going to approach my organization...
/Application
/ViewStack
/Section (MXML Component)
/ViewStack
/Page (MXML Component)
/State1
/State2
/Page
/...
/Section
/...
/Section
/...
This is using two observations. One, I've read that ViewStack is
better for emulating a "fresh start", kind of like a traditional
transition between web pages. However, a state seems to be for
modifying an existing view.
Wanting to work with modules small in size, I'm going to have
"Section" components which are really just MXML Components containing
a ViewStack and based upon some container. I think "Page" is really
just an MXML Component based upon a Box (unless someone can suggest a
lighter-weight container to use).
I'd really appreciate some opinions on whether or not this is a
reasonable approach. To me it seems logical, but I'd hate to find out
later that there are native tools for all of this.
Many Thanks!
