This content has been marked as final. Show 9 replies
In flex you don't need to load different pages on each submit, every time you fetch data from the back end - you can modify the view by changing the state of the application.
navigateToUrl is for loading a different url into the browser. I think for your use case you need to look at states.
Flex SDK Team
I don't want to remain in the same screen if I were to login I should transition to my main screen. From the to other screens
Thanks for the help
I find ViewStack easier to use than states.
But either way, a normal flex app remains resident in the browser , and you change "screens" using navigation components.
Ok this example hit the mark. I'll continue reading it
Question: when navigating across View Stack screens, is it possible to integrate this with a pageview-tracking system?
The powers-that-be here are leery of me using Flex Apps since one complex app counts as one one page-view for us right now.
How do you handle that issue?
....to add to the last reply
How can I break up the application so other developers can work on the applications screens? Adding few States to a single MXML is ok but in a larger application were talking a huge MXML file. Ok so I'll need to make the case for Modules or Applications. So Modules how do I load one, with out generating an exception. Ya tried to load one of the samples and got an exception. Using the builder I created a new Module and copied the contents of the sample to it. The Module I created loads with out an exception.
The Modules I'll need to load will have images, Charts as well as text
Yes you should consider using modules for a larger app. There is online documentation available for using modules.
Thanks for the confirmation