[Seaside-dev] tasks without flow

[Julian Fitzell]

On Tue, Dec 15, 2009 at 11:06 AM, Lukas Renggli <renggli at gmail.com> wrote:
>> Does that make sense? Can we at least agree the method should exist
>> (and worry about the name separately)?
>
> Yes, I never disagreed.

Ok.

>> I suppose we could have #call:onAnswer: ? Would that be clear?
>> Unclear? One disadvantage, since #call: is already used, is I don't
>> know what to call the version that doesn't take a block.
>> #goto:/#goto:onAnswer: ??
>
> I like #call:onAnswer: because it does not introduce a new concept. I
> guess people can understand the difference to #call: in the sense that
> it does not answer a value but passes it into the block.
>
> I don't like #goto: because it does not go anywhere and it introduces
> an entirely new word. It is already difficult to explain the
> difference between #show: and #call:

Ok, that's at least consistent with #inform:onAnswer:, etc. though
those are also frustrating when you don't need the #onAnswer: part.

Anyone else have opinions on #call:onAnswer:? or a better suggestion?

Julian