Hi there,
Have some questions about the best practice way of designing apps.
I'm building a simple email server preferences application. And I've created two
components. One for handling the login (which hits amfphp and ldap on the backend) and
one for loading and changing/saving the user prefs (which also hits amfphp and ldap on
the backend).
There are really only two "states", login handilng, and prefs changing.
Question 1: Is it best to use States or ViewStacks to deal with changing "app states"?
on to my second question...
The login component is sorta self sufficient. It can handle good logins and bad ones. and
if it's a good login can switch the current state to the preferences state (as viewstates are
what i'm currently working with.) But when i get to the email preferences state, it wants to
know things from the login component, like email and password.
Question 2: Is it good practice to have components be able to talk and share information
with one another? And if so, how do you keep them around and reference them if you're
using viewstates?
Thanks,
mark
--
----------------------------
Igor Costa
www.igorcosta.com __._,_.___
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
![]()
SPONSORED LINKS
Software development tool Software development Software development services Home design software Software development company
Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe
__,_._,___
- Re: [flexcoders] 2 questions Igor Costa
- RE: [flexcoders] 2 questions Stacy Young
- Re: [flexcoders] 2 questions Tom Chiverton
Reply via email to
better uses of viewStack
On 11/2/06, DJ Lift <[EMAIL PROTECTED]> wrote:

