I’m trying to build on the tabbar sample.
In theory the tabbar sample and groups are exactly what the doctor ordered but after more than a few unsuccessful tries I thought I better take a step back.
For the most part my problems have been objects showing up on screens2 and 3 while created/used in screen1.
The questions:
-
all screen display functionality gets put into function new() on each screen?
-
Can I have other groups within group g? I.e. g1 and g2 and turn them off/on as needed?
-
Other functions can be added to screen1.lua outside new() put called from within new() as long as no screen output?
-
Is main.lua a better place to put additional functions, especially if they may be used by screen1 as well as 2 and 3? These functions would be socket calls, xml parsing, etc. I.e. no screen output. Or perhaps a separate file altogether and added via require in main.lua?
-
I need the user to login, once. Should that go into screen1 or main?
The jest/requirement of my app is pretty straightforward:
login, once.
enter part number
push button
display results (removing the ‘enter partnumber part’ from display)
change qty and push button to write changes
or push button to confirm qty ok
and we go back to ask for new part number.
A little bit oversimplified as we display more info about the part, etc. but that’s basically it. I have all the behind the scenes stuff in place and working, I.e. socket calls, xml parsing. It’s the UI that is causing me grief and that’s only because it’s hard to let go of prior programming where everything was flowing top to bottom. Not saying I don’t like the “new stuff” just that I’m having a bit of a struggle grasping it all.
Thanks in advance for any help/suggestions you may be able to provide.
[import]uid: 6547 topic_id: 6992 reply_id: 306992[/import]