[Seaside] Seaside subsets

Lukas Renggli renggli at gmail.com
Thu Feb 15 16:34:19 UTC 2007

> >> - We use WATask sparingly.  In fact, pretty much the only use is for
> >> collecting payment info, which is of course the classic example I
> >> always give.
> >
> > Yep, except for tutorials and teaching Seaside I find this component
> > useless ;-)
> How do you manage flows then ? logging process for instance...
> It seems WATask is a hack (? heard that somewhere) but I like the idea
> to represent a flow, a process and I find natural that way... what's the
> alternative for you ?

You can do what you do within a task in any callback. Something like

html anchor
     callback: [ self call: WAFoo new; call: WABar new ];
     with: 'Foo and Bar'

If you extract the contents of the callback block into its own method
you basically have a method defining the flow. So I wouldn't remove
WATask, but it seems to be less useful as most of the flows are
started anyway from a callback (what also avoids the nasty redirect
the first time a WATask is displayed).

> Uhm, I think I'd like to know more on annoucment...
> I've ssen a bit through mondrian but don't really get it... found also
> some information (from the vw version) but not sure it's the same...

Yes, it is mostly the same: the implementation is different, but the
interface should be basically the same. Have a look at the posts of
Vassili Bykov:



Lukas Renggli

More information about the Seaside mailing list