[Seaside-dev] Seaside2.8a1-rjl.493 + Seaside2.8a1-rjl.494
Ron at USMedRec.com
Tue Oct 2 17:31:20 UTC 2007
I'm sorry I didn't get that it returned nil on cancel. That is fine for me.
I was thinking about adding other decorations, where adding didn't return
the component. In those cases if you wanted to later remove the decoration,
it was much more difficult.
I wasn't talking about using the component. Returning nil while using the
component like a dialogue is fine.
> -----Original Message-----
> From: seaside-dev-bounces at lists.squeakfoundation.org [mailto:seaside-dev-
> bounces at lists.squeakfoundation.org] On Behalf Of Ramon Leon
> Sent: Tuesday, October 02, 2007 11:30 AM
> To: Ron at USMedRec.com; 'Seaside - developer list'
> Subject: RE: [Seaside-dev] Seaside2.8a1-rjl.493 + Seaside2.8a1-rjl.494
> > Does it have to return nil? I haven't had a chance to look
> > at it but I know I had some trouble with removing decorations
> > that returned nil previously.
> > If it needs to return nil, that's fine I can probably work
> > around it, just wondering.
> > Ron
> What would you suggest a cancel action returns? WAChoiceDialog also
> nil when you select cancel, so putting a WAChoiceDialog in a window breaks
> it, and will break anything it wraps that returns something, nil seems the
> only obvious thing cancel can return.
> Honestly I'm not even sure the dialogs belong in the core framework, I
> mostly use them as samples to quickly copy or subclass and customize, but
> long as their in there, they should work consistently with each other.
> Ramon Leon
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
More information about the seaside-dev