You must Login before you can answer or comment on any questions.
I'm building my first app with Appcelerator and have watched the training views and downloaded the appropriate code snippets. I understand the general framework and think I have most of the tools needed to do my job.
However, before I begin, I have a big general question about app architecture. It really comes down to a question between Windows & Views.
The app I have in mind will consist of 4 general screens. But, I can NOT use a tabbed architecture for developing this app. This is because it will be a guided navigation. By that, in order to get to screen 2, the user will need to perform an action on screen 2. And, in order to get to screen 3, the user will need to perform an action on screen 2. For both screen 2 & 3, the page "template" will be the same, but the data will be different based on the value selected on the previous screen. Make sense?
Now - my question is how i should architect this?
Originally, I assumed each new screen would be a Window. But I later learned that you can only have two Windows open at a time. (at least the way I was doing it). So I am now trying views instead. does this make sense.
Also - as part of the application process, the user will be closing screen 3 quite frequently, going back to screen 2 and re-opening screen 3 with a new set of data (by selecting a different value in screen 2). Therefore, I assume that I need to do some sort of memory management (aka: garbage cleanup). Every time screen 3is closed, I want to totally erase it from memory. This way, a new version of screen 3 can be opened again without any legacy data. And, if I do this a dozen times in a row, i don't want my app to crash from using too much memory.
Any help on these two issues would be greatly appreciated.
1 Answer
You can use a navigation group to create the general flow from window to window. You can hide the navigationBar so that the user can only advance and go back based on the UI controls you give them.
As far as I know, the navigation controller will handle your memory issues for you (closing/opening windows). You shouldn't need to worry about that.
Your Answer
Think you can help? Login to answer this question!
