State machines in WO
State machines in WO
- Subject: State machines in WO
- From: "Alex Boster" <email@hidden>
- Date: Wed, 17 Mar 2004 17:14:26 -0800
Newbie here gone through the Apple Web Apps tutorial and most of Ravi
Mendess book. Im try to design a task/defect tracking system and need
some insight in what would be the WebObjects Way to do some things.
In particular, the thing is basically a large state machine. Depending on
the current state, the user will have access to a different set of the tasks
attributes. Links or buttons will be displayed for the valid state
transitions.
So does anyone have a recommendation for a strategy here, in keeping with
the zen of WO? (Or a recommendation on how NOT to proceed.)
A naove idea would simply have one page per state. An incremental
improvement on that would be to factor out common features into custom
components. Another naove idea would be to have one page with a lot of
logic. Neither idea seems ideal
A much more ambitious approach would be to keep the state diagram, task
attributes, and such as metadata and build things dynamically. But I don't
anticipate that the payoff in this case would be worth the effort.
Alex
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.