[Seaside] WATask, anyone?
nick.ager at gmail.com
Fri Sep 14 15:18:36 UTC 2012
I occasionally use WATask if I think it helps express my intent.
For example from Pier Admin
> | kernelNamedispatcherNamePair |
> kernelNamedispatcherNamePair := self
> self queryAdminUICreationFor: kernelNamedispatcherNamePair kernelName at:
> kernelNamedispatcherNamePair dispatcherName
> | kernelCreator |
> [ kernelCreator isNil ] whileTrue: [
> kernelCreator := self selectExportedKernelComponent.
> (self ifPresentConfirmRemovalOfApplicationAt: kernelCreator
> dispatcherPathName) ifFalse: [ kernelCreator := nil ] ].
> self createExportedKernel: kernelCreator.
> self queryAdminUICreationFor: kernelCreator kernelName at: kernelCreator
I'll let others judge if I've succeeded in clearly expressing my intent.
On 14 September 2012 15:31, SebastianHC <sebastian_heidbrink at yahoo.de>wrote:
> I'm currently starting a new project and it seems like Pharo and Seaside
> 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?
> When the Seaside Sushistore Example App came out, I thought well, this is
> it. Workflows can be done so easy with it.
> Is there a reason why most current great Seaside-based Frameworks and Apps
> avoid the usage of WATask?
> Is it to unreliable? Difficult to debug? Difficult to keep track of
> Am I perhaps wrong? Are there some packages out there where somebody used
> WATask excessively?
> Any thoughts very appriciated!
> View this message in context:
> Sent from the Seaside General mailing list archive at Nabble.com.
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside