You can make your 'views' components and use a viewstack or other container to show that 'screen' or your can make each screen its own app and use the module system to pull each app into the main app as needed.
On 5/30/07, Dave @ VitalPodcasts.com <[EMAIL PROTECTED]> wrote:
I feel like its back to the Old QBasic ways... Make one super long file that does everything, thats kind of nuts. You mean there isn't a "Load NextScreen" type of thing? Where a whole new set of objects live? and I don't have to worry about hiding everything? So far it feels to me, so far, I need to create lots canvases for the different "screens" the application uses, and then create a funciton that hides all but the one in focus... Can anyone describe how they setup their code? As far as logic, Im not too worried abotu that as most the logic will be in CF webservices, im more worried about having an insane amount of visual code in the MXML.
-- I am not a diabetic, I have diabetes my blog - http://grumpee.instantspot.com/blog
