[Seaside] Can I know if a WATask answered?
sebastian at flowingconcept.com
Mon Nov 3 11:08:03 UTC 2014
That idea of using a WATask to be #renderOn: instead of #call: is a contradiction.
WATasks exists to be #call: ‘ed
In any case, when they answer you know they did because you’ll see control on whatever you did to capture its answer (and the actions of the code after that)
But I encourage you to turn your back to WATask, your control flow code perhaps doesn’t get concentrated and beautiful as the one they promise you but truth is there is nothing you can’t do without them in simple ways using just components and state.
How did I reach that conclusion?
In two occasions WATasks were promising, things ended up in rework.
> On Oct 31, 2014, at 1:52 PM, Mariano Martinez Peck <marianopeck at gmail.com> wrote:
> Hi guys,
> There is an scenario that I don't know how to deal. I have a main component that displays tabs. Each tabs render a component. This component could be anything, including a task. The tab has correctly defined the #children. And the way the tab displays its current contents (a component) is via: "self activeTabComponent renderOn: html"
> The problem is if "activeTabComponent" is a Task. Since I am not doing not replacing anything (calling), I do not use #call: but #renderOn: as displayed above. The task can, at any point in time, or when the user clicks "Finish" do a "self answer: nil". I don't know what happens with this "self answer:" because I didn't do a #call: to that task.
> Anyway... I would like to hook from my main component and I would like to know if the task has answered or even if the #go method finished so that I can automatically close the tab and remove this task. Of course, I can pass the main component to the task, and then from the task itself tell the main component that he has finished...but I don't like this very much.
> Any idea?
> Thanks in advance
> http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/>
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside