This content has been marked as final. Show 3 replies
You can do it all, if you like. Just remember that Modules have to be downloaded on demand, so the first time there will be a delay. Use Modules only if some people will use some of the features. For example, if 90% of the user will never use the Admin portion, then having that as a Module makes sense since they shouldn't wait for it to download as part of the main SWF.
To use states, code the parts (login, panel, admin) as separate Flex classes. Then the main app, with the states, will be easier to code and understand.
Using states to make the login disappear and the panel/admin appear is nice way to handle it.
I too have been playing with modular designs.
Currently, in my main application, all states are 'popup' modules.
In your case, this may work well for the login / registration as well as for the preference settings and the like.
Personally, I have not tried modules. Although I think I may have too soon as my application is becoming quite large. I find states a bit cumbersome. What I am using now is a view stack and it works quite well. This is an excerpt from my Main mxml file . . .
The beauty of this is I can set the workflow state anywhere in my code by accessing the model and that page shows up while all other pages are hidden.