How to sequence canvasses, SVGForms, SVGSplashScreens

Question

I have made a program, that "walks" , through a few input phases. Purely sequentially:
1: the splash, that times out after 2 seconds and at DISMISS_COMMAND steps to a
2: Canvas, that processes exactly 3 keyPressed events and then automatically jumps to
3: an SVGForm that asks for two values via a set of SVGRadioButtons and an SVGSpinner. Pressing Command.EXIT makes the program exit, Command.OK makes the program then jump to
4: a canvas that keeps running "forever", until a certain key is pressed. (event KeyPressed) Then the Canvas stops and the program exits.
So the program is controlled by regular commands and by keyPressed events.
My question is, what the best, or "best practice" way is to connect these phases.
1: in the commandAction of the main MIDlet ? This processes the DISMISS_COMMAND , EXIT command and OK command mentioned., but not the keyPressed events of phase 4 or the automatic jump from phase 2.
in other words: is it "good practice" to use commandAction to handle all program control ? The DISMISS_COMMAND would then cause Canvas (2) to start, which would, on ending, create and start the SVGForm which would again have the same commandListener as the splash. Sort of recursion ?
2: or in the startApp with some if-constructions and state variables or whatever?

Answer 1

Erik_that_s_me wrote:
I have made a program, that "walks" , through a few input phases...given that you describe the problem in terms of phases (states), [state pattern|http://en.wikipedia.org/wiki/State_pattern|explanation] naturally comes to mind.
My question is, what the best, or "best practice" way is to connect these phases.
1: in the commandAction of the main MIDlet ?Above, you mean something like having single CommandListener "shared" between different screens?
My experience with stuff like that was rather negative: "personal" listeners (one per screen) were easier to code and maintain. If you find a way that does not use shared listener, I'd recommend to go for it.
2: or in the startApp with some if-constructions and state variables or whatever?hm for stuff like that I would try to design a dedicated object to manage state, variables and transitions