My App is basically a database app, I.e. enter part number, manually or via barcode scanner, confirm qty on shelf, change if incorrect, etc.
As part of the task we also display more information about the part, including images.
The data is exchanged using tcp/ip and the images we get dynamically from a web location.
It all works quite well but I want it working better 
I just finished adding a few special tasks, like adding stock, etc. I’m using director and start on screen1 which is actually a menu, I.e. separate button for each task (5 tasks currently), each button press goes to a respective scene/screen to do the task.
The area I want to improve is to give the user the ability to switch to another task directly via a tab bar and then us one or more scenes to complete a task.
One of the things I hope to improve on is how images are viewed. I currently use a button to open another screen where the images are viewed, each via its own button. It would be much nicer to slide the images. I currently load them dynamically when a part number is entered so they are all available on the device. One problem I have to design for is that not every part has the same number of images.
This app is limited distribution, I.e. adhoc. My other App is in the App Store (RareParts), which uses the forerunner of widgets. I want to redo that one too so I’m trying to find/define a path for myself that will last a bit and avoid double coding.
I see the tab bar in the storyboard sample but it only shows the tab bar itself. Since I’m still relatively new to all this object style of programming I need a little more of a kickstart that I can expand on
Are there any additional storyboard samples/ snippets available?
Am I being premature to contemplate a switch away from director? I just thought since I still have lots to learn about director, the time might be better spent learning storyboard.
[import]uid: 6547 topic_id: 24234 reply_id: 324234[/import]