|
Up to you. How related is the data on the
5 tabs? Sometimes what I do is have a larger model in the Applicationand make
the tabs work with subsets. <mx:Model id=’wholeModel’> <piece1 /> <piece2 /> … </mx:Model> <mx:TabNavigator> <Tab1 data=""
/> <Tab2 data=""
/> … </mx:TabNavigator> Tab1.mxml <mx:Form> <mx:Model id=”data”> <someData>{input1.text}</someData>
<someOtherData>{input2.text}</someOtherData> </mx:Model> <mx:StringValidator field=”data.someData”
/> … So it really does depend on how the data
is going to be used to decide how you want to structure it. If you want validation
and binding and you’re writing different MXML files it makes sense to
have each MXML deal with its own data. But that doesn’t mean that the
data couldn’t actually be part of a larger piece (like done above). Matt From: Doug Coning
[mailto:[EMAIL PROTECTED] Newbie Question: I have a user application that contains 5 tabs (using the
TabNavigator). I’d like to use the <mx:Model> class to store
and validate the data from each of the forms on those 5 tabs. What isthe
best method for doing this? Should I place the Model in the Application
file or should I break it down into smaller sections for each tab? I hope this question makes sense. Do I use one root
Model, or five smaller models for each tab? Thanks, Doug Coning Software Developer FORUM Solutions, LLC This e-mail and any attachment(s) are
intended for the specified recipient(s) only and are legally protected.
If you have received this communication in error, please “reply to”
sender’s e-mail address with notification of the error and then destroy
this message in all electronic and physical forms. |
