Hi Sam Sounds like you're asking for a workflow system, running and governed by a TW. Right? That's like a GTD system with definition capabilties and archival capabilties and...
Wow. That would be astonishing if it could be put together correctly. I can see that the simplest WF could be achieved by any of the slideshow plugins available providing a simple "get next task" kind of function. But, strictly, if you're expecting 1) (ability to define sequences (workflows)) and 7) (collecting data along the way) then this implies that validation and therefore vital task criteria are required to know exactly what the next task should be in a given scenario. This implies a state machine. System needs to know what state a given WF is in to be able to decide what to do next. Which further implies the ability to specify and capture all states for a workflow template when it's being built. Maybe I'm reading too much into what you said? Russ 2009/3/18 SamCox <[email protected]> > > Hi Everyone, > > I want to document an assembly procedure having about 20 major steps > with each step consisting of a primary operation preceded by a pre- > assembly inspection sub-step and a post-assembly verification sub- > step. Many steps will be illustrated with photos. > > I'd like my procedure to have some or all of these features: > > 1) Defined sequence -- the steps must be done in a specific order. See > also 6), below. > 2) Display one step at a time -- i.e., close other steps. > 3) Must click check box to advance to next step. > 4) Access to pop-up reference tiddlers via, say, sidebar tag cloud or > links embedded in individual steps. > 5) Novice / Expert modes in which more or less information is > displayed. I expect my experienced operators to actually need only a > checklist but the more inexperienced such as trainees and engineers > (!) will need hand-holding. It should be easy to switch between modes. > 6) Master tiddlers that can employ (deploy?) other tiddlers in a > specified sequence. This is important because the procedure steps > appliy to a few assemblies with somewhat different content. > 7) Minor data collection such as serial numbers, revision codes, go-no- > go test results -- stuff like that. > > Is it possible that someone has collected the right set of plugins for > a job like this? > > Thanks, > -- Sam > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
