This week's book giveaway is in the
We're giving away four copies of
Head First Android
and have Dawn & David Griffiths on-line!
A friendly place for programming greenhorns!
Big Moose Saloon
Register / Login
Win a copy of
Head First Android
this week in the
Each State consisting of a new Conatiner
Ravi Kiran Va
Joined: Apr 18, 2009
May 28, 2010 06:00:09
I have seen a example regarding View states , where the coding is in this way :
An Application container consisting of two states , where in each state there is a Form Added , something this way shown below :
<mx:Application> <mx:states> <mx:state name="Login"> <mx:addChild> <mx:form name ="LoginForm"> // Some componets with respect to Form Container here </mx:form> </mx:state> <mx:state name="Register"> <mx:addChild> <mx:form name ="Register"> // Some componets with respect to Form Container here </mx:form> </mx:state> </mx:states> </mx:Application>
This works fine and looks nice .
I am having a question here "Is this type of coding is nice ??"
will this make sense as i read that states help in maintaing different views with same conatiner , but in this example the user is creating a new conatiner for every state ??
Please share your ideas .
Thanks for reading .
Save India From Corruption - Anna Hazare.
Joined: Apr 14, 2004
May 30, 2010 09:54:56
I'm not sure I see what is wrong with that approach. What concerns you?
I agree. Here's the link:
subject: Each State consisting of a new Conatiner
How do you handle the auto-population of collection of data from dynamic pages?
having components based on Data Grid's column value.
Dynamic translation of XML into CSV using XSD
Flex 3 :Help needed in implementing View States
Tips on form vo binding in flex3 and flex4 approach with two-way binding
All times are in JavaRanch time: GMT-6 in summer, GMT-7 in winter
| Powered by
Copyright © 1998-2015