The only time I’ve used states is
transitioning from two different contexts …specifically from a login screen to
the initial state of the application after login. (I wanted to animate the
transition) As for components, my approach is to “black
box” them and leverage the event model for communicating. As soon as one
component knows about another, re-use is pretty much compromised. Your app
itself can use listeners to catch and respond to these events and orchestrate
things between components. HTH, Stace From: better uses of viewStack On 11/2/06, DJ Lift
<[EMAIL PROTECTED] Hi there,
-- 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
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 __,_._,___ |