[Seaside] Re: Home Link

[Zulq Alam]

I kind of agree but it seems WATask is doing more than just 
encapsulating workflow.

I wonder what purpose this redirect serves?

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

And why should local decoration wrap new delegations (the answer to this 
will likely go over my head at the moment) rather than vice versa in 
WAComponent?

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

I'd like to understand these before I stop using WATask for my short 
workflows. Also, for long workflows I still have the same problem.

Where I don't agree is I think when the application scales having 
followed a consistent pattern and separating these concerns will have 
maintenance benefits.

Z.

Yanni Chiu wrote:
>
> FWIW, I've been down the WATask path, following the Sushi
> store demo. Web apps seem to flow in two ways at the same
> time. One is just random browsing, and the other is a
> constrained path. You could consider "random" browsing
> to be a contrained path, and therefore wrap it in a task,
> but IMHO it makes the code harder.
>