<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>I feel like this is said a lot on this mailing list, but I'm a huge proponent of it. Announcements ftw.<br><br>WATask isn't really a state machine. It's more like a wizard or a subroutine (at least in my brain hehe).<br><br>RS<br><br>> Subject: Re: [Seaside] WATask, anyone?<br>> From: mac.hive@me.com<br>> Date: Sun, 16 Sep 2012 10:23:33 -0400<br>> To: seaside@lists.squeakfoundation.org<br>> <br>> <br>> On Sep 16, 2012, at 9:53 AM, Philippe Marschall wrote:<br>> <br>> > On Fri, Sep 14, 2012 at 4:31 PM, SebastianHC<br>> > <sebastian_heidbrink@yahoo.de> wrote:<br>> >> Hi!<br>> >> <br>> >> I'm currently starting a new project and it seems like Pharo and Seaside are<br>> >> part of it.<br>> >> <br>> >> I follow the community and did some prototyping since the early beginnings<br>> >> of Seaside.<br>> >> <br>> >> But there's one thing I'm really wondering about!<br>> >> Why is WATask so rearly used and mentioned?<br>> > <br>> > Maybe because you can get the same functionality with a method or<br>> > block and #call: without having to create a class.<br>> > <br>> <br>> 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; <br>> <br>> go<br>> 	| user component |<br>> 	self call: self userLoginView.<br>> 	(self userLoginView user) notNil <br>> 		ifTrue: [ <br>> 			component := self firstComponentToDisplayForUser: self userLoginView user.<br>> 			[ component notNil ]<br>> 				whileTrue: [ <br>> 					self call: component.<br>> 					component := component nextComponentToBeDisplayed ] ]<br>> <br>> I'll have to think about whether I could use WATask for some sophisticated workflow/notification processing in my system.<br>> <br>> Regards, <br>> <br>> Larry Kellogg<br>> <br>> <br>> <br>> > Cheers<br>> > Philippe<br>> > _______________________________________________<br>> > seaside mailing list<br>> > seaside@lists.squeakfoundation.org<br>> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside<br>> <br>> _______________________________________________<br>> seaside mailing list<br>> seaside@lists.squeakfoundation.org<br>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside<br> </div></body>
</html>