[Seaside] novice question: WATask vs WAComponent

[Brian Brown]

One more thing I forgot to mention about WATask...

if you #call: a WATask, it won't loop, but will return the result of 
the #go

The looping behavior works in the case I demonstrated since the WATask 
is the root component; thus when it returns the session just runs it 
again.

This looping behaviour will also happen if a WATask is rendered as a 
component on a page.

Have fun,

Brian

On May 12, 2004, at 2:36 PM, Brian Brown wrote:

> Ha! Just bad typing... I meant implicit loop...
>
> Brian
>
> On May 12, 2004, at 10:29 AM, Jason Dufair wrote:
>
>> Brian Brown <rbb at techgame.net> writes:
>>
>>> For this, I would use a WATask; you can think of it as an implicit
>>> look.
>>
>> Brian - just wondering: what do you mean by "an implicit look"?  I
>> understand the code you posted, but I'm not clear on this terminology.
>> Thanks!
>> -- 
>> Jason Dufair
>> Office of the VP for Information Technology
>> Purdue University
>> jase at purdue.edu
>> 765-496-1185 - fax: 765-496-7409
>>
>> _______________________________________________
>> Seaside mailing list
>> Seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/listinfo/seaside
>
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/seaside