You can do this the same way as you would have done using a ViewStack
approach. As Scott said, you can store the state representations and a
workflow property in your model. The only differences are in your view.
Instead of binding a method to the ViewStack's selectedChild instance,
you could bind
Actually, application state can be stored in the Model. If you look at the login example, you'll see them storing a workflowState variable. However, if you're talking about your views, then that is probably the proper time to use the objects.
ScottOn 4/1/06, sof4real03 <[EMAIL PROTECTED]> wrote
2 matches
Mail list logo
