To my limited Flex knowledge, I thought separate state for each submodule would be the best way to go.
2. I have many self coded components which represents these submodules. And once the user spikes or save a whole submodule, Yes, I want to destroy them and recreate them again for the new workflow.
3. This question is vague (I think you also never understood what you meant to say). Yes, I can write my own reset method, but all I want to do, is to call the creationComplete() method again to re-populate the data in the screen. That is the only thing I want to know in this post. Now if I knew how to do that, I would have written a "How-to" tech-blog instead of asking it here.
But then, I am not sure, what exactly you meant when you say "lumps your entire application into one component". Are you talking about the compiled output? In the flex project I have only one application Login.mxml and so I have Login.html and Login.swf file only for this project. Will that be a problem?
I should be return back to the base state, from where I can again resume selecting any submodule. Now I am able to track the spike event and clean up all the beans containing data which I populated when the application started. But in this second round , the creationComplete() methods are not doing anything. So I am curious to know of ways to re-invoke the init() method to re-populate the beans. My init() merthods contains the logic to populate data to be displayed in the screen.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton