fsm:upgrading_fsm
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
fsm:upgrading_fsm [2007/05/01 16:31] – fgm | fsm:upgrading_fsm [2007/05/08 21:50] – fgm | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Upgrading apps using OSInet FSM ====== | ||
- | |||
- | ===== 1.3 to 1.4 ===== | ||
- | |||
- | * No application changes are necessary, BUT : | ||
- | * applications can now use external FSM descriptions in XML format. Building the FSM directly in code still works but it deprecated. It may go away at some later point. Constructors now typically look like just this: | ||
- | <php> | ||
- | function __construct() | ||
- | { | ||
- | $this-> | ||
- | parent:: | ||
- | } | ||
- | </ | ||
- | * The XML file holding the FSM description is found by default if it is called < | ||
- | |||
- | ===== 1.2 to 1.3 ====== | ||
- | |||
- | * No application changes are necessary. | ||
- | * New features: | ||
- | * enable/ | ||
- | * idle() shorthand method | ||
- | * additional operation modes: | ||
- | * fsm:: | ||
- | * fsm:: | ||
- | * fsm:: | ||
- | * enable/ | ||
- | |||
- | ===== 1.1 to 1.2 ====== | ||
- | |||
- | * The new post-event action feature allows shorter automata by event chaining | ||
- | * The new default " | ||
- | * Because of this change, fsm:: | ||
- | * either use apply_simple_event, | ||
- | * use the fsm_state field from the value returned by fsm:: | ||
- | |
fsm/upgrading_fsm.txt · Last modified: 2020/11/23 17:23 by 127.0.0.1