Best structure for apps?
What's the best structure for an app with 3+ screens. An example app: Home Screen, Categories/Stars/Studios screen, Content based on Cat/Star/Studio chosen screen - These 3 screens are in their ow...
Forum Discussion
That helped a lot, I think I was finally able to wrap my head around certain things, thank you!
What I currently have is 3 pages independent of each other and i'm passing data to them via the interface fields (each page had a prevScreens and overhangNode field ) though I was having trouble passing data backward because of a lack of reference to earlier components. And I just turn visibility on and off for them when users move to a different screen.
After going through some things based on your reply, it seems the most appropriate structure is having 1 "scene", appending my 3 pages to it, updating content and turning visibility on/off as I need. The assoc array is a good idea for keeping track of the users screen movement for the BACK button. I was thinking of doing that via an interface but this will obviously be much easier having it all at a top level page.
One further question: I will also have a Login page. I'm assuming this means I should make a 2nd "scene"? One for the Login and the other is my actual app content. main.brs would then have a statement pushing the user to the correct scene based on if they were logged in or not. Does this sound correct?
What I currently have is 3 pages independent of each other and i'm passing data to them via the interface fields (each page had a prevScreens and overhangNode field ) though I was having trouble passing data backward because of a lack of reference to earlier components. And I just turn visibility on and off for them when users move to a different screen.
After going through some things based on your reply, it seems the most appropriate structure is having 1 "scene", appending my 3 pages to it, updating content and turning visibility on/off as I need. The assoc array is a good idea for keeping track of the users screen movement for the BACK button. I was thinking of doing that via an interface but this will obviously be much easier having it all at a top level page.
One further question: I will also have a Login page. I'm assuming this means I should make a 2nd "scene"? One for the Login and the other is my actual app content. main.brs would then have a statement pushing the user to the correct scene based on if they were logged in or not. Does this sound correct?
