[Seaside] WATask, anyone?
watchlala at hotmail.com
Sun Sep 16 15:42:16 UTC 2012
I feel like this is said a lot on this mailing list, but I'm a huge proponent of it. Announcements ftw.
WATask isn't really a state machine. It's more like a wizard or a subroutine (at least in my brain hehe).
> Subject: Re: [Seaside] WATask, anyone?
> From: mac.hive at me.com
> Date: Sun, 16 Sep 2012 10:23:33 -0400
> To: seaside at lists.squeakfoundation.org
> On Sep 16, 2012, at 9:53 AM, Philippe Marschall wrote:
> > On Fri, Sep 14, 2012 at 4:31 PM, SebastianHC
> > <sebastian_heidbrink at yahoo.de> wrote:
> >> Hi!
> >> I'm currently starting a new project and it seems like Pharo and Seaside are
> >> part of it.
> >> I follow the community and did some prototyping since the early beginnings
> >> of Seaside.
> >> But there's one thing I'm really wondering about!
> >> Why is WATask so rearly used and mentioned?
> > Maybe because you can get the same functionality with a method or
> > block and #call: without having to create a class.
> I used a WATask to handle the login logic for www.practicemusic.com, but after login all of the other views are shown with a call:, like this;
> | user component |
> self call: self userLoginView.
> (self userLoginView user) notNil
> ifTrue: [
> component := self firstComponentToDisplayForUser: self userLoginView user.
> [ component notNil ]
> whileTrue: [
> self call: component.
> component := component nextComponentToBeDisplayed ] ]
> I'll have to think about whether I could use WATask for some sophisticated workflow/notification processing in my system.
> Larry Kellogg
> > Cheers
> > Philippe
> > _______________________________________________
> > seaside mailing list
> > seaside at lists.squeakfoundation.org
> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside