WATask

Comment:

I am a subclass of WAComponent, specialized for defining workflow.  The difference between a task and a component is the following:

Both of them are reusable, embeddable, callable pieces of user interface. A component has state (instance variables), behavior (it may change its state, and it may also choose to display other components with #call:), and appearance (it renders HTML). A Task has only the first two - it doesn't render any HTML directly, but only through the components it calls. This is useful when what you want to encapsulate/embed/call is purely a process (show this component, then this one, then this one).

The key method for WATask is #go - as soon as a task is displayed, this method will get invoked, and will presumably #call: other components.

In terms of implementation, you can think of a WATask in the following way: it is a component which renders two things:
- a link whose callback invokes the #go method
- a header that immediately redirects to the URL of that link

Hierarchy:

ProtoObject

Object

WAPresenter

WAComponent

WATask

• CheckoutTask
• FlatStacieTask
• KidsPublisherTask
• MISPublisherTask
• SCDatabaseInspectorTask
• ShoppingTask
• WACookieTest
• WAExceptionTest
• WAOnceTest
• WAStoreTask
• WATool
• WATransactionTest

Summary:

Detail:

	^ (oldDecoration isGlobal and: [newDecoration isGlobal not])
		or: [oldDecoration isLocal and: [newDecoration isDelegation]]

	self subclassResponsibility

	self session redirectTo: (html urlForAction: [[self answer: self go] repeat])

^top