Prototype: Biologist workflow implemented as StateMachineActivities
I have a solid prototype of a wizard that steps through the workflow we agreed on. It’s a “perpetual motion†machine that keeps going until the user hits cancel. It maintains the model structure as the user goes along. Each model entity (cyg, patch, waypoint) is represented by a different statemachine based on windows workflow foundations. There is one state machine per model object instance (for example every CYG has its own instance of a cyg workflow).
Basically, it keeps asking for more until you cancel, tracking what is complete and what still remains to sample.
There’s a little video (mhscontroller-test-20080624.swf) which is relatively boring except for what is going on under the hood. The movie just loops.
Next steps are to wire these workflows and the new model into the main application. Then fine tune the events from measuring instruments.
CurrentYearGrowth state machine workflow activity
![]()
Permalink Comments off
