In my current wrestling with programming my CatchaTrain application (ahem! A spiffy sounding application name) I have normally only one main state (in other words, a particular view of my application) that shows the hour that the next train is leaving.
Somehow however I have now managed to create in my main application 4 additional states (actualy 5, but the first one will disappear in due time) :
- Initial state which is shown when you start up the application for the first time: it asks you to select a station –> this needs to be removed and changed to initial empty train view!!
- Train leaving in … hours and minutes view
- Dropdown showing a datagrid of the leaving time of your train from that station
- Overlay state showing you buttons to add a station or add a train
- Overlay state for actually adding the station
- Overlay state for actually adding a train
It all works fairly logically, and I am quite happy with the results. But really, unless I had FlexBuilder, I wouldn’t be able to make heads or tails out of the different states. Many is the time that I switch to design view to check a state, add a button or remove a textfield.
If there’s one thing that flexbuilder does well, it’s that you can check via the designer view if what you are doing actually makes sense.
Now, on with the code… I’m almost finished (I’ve been saying that for the last 2 months or so…)