[Seaside-dev] Issue 195 in seaside: WATree is broken

[codesite-noreply at google.com]

Issue 195: WATree is broken
http://code.google.com/p/seaside/issues/detail?id=195

Comment #5 by jfitzell:
It's not a quick way around it.

The change to WAActionCallback>>evaluateWithArgument: (it used to call  
#value)
happened in Seaside-Core-jf-164 and Seaside-Core-jf-165. We want to provide  
the value
of the GET or POST parameter to the action callback block if they want it,  
but most
of the time when you are writing an action callback you don't care.

I just think our implementation of MessageSend>>valueWithPossibleArgument:  
is buggy.
If the message send has already been parameterized, then by definition,  
there are no
possible arguments slots. What I don't know is if there are other parts of  
the code
that would be broken by this behaviour (I suspect not, because it's kind of  
illogical
to want to override the arguments specified in the MessageSend).

Name: Seaside-Core-jf.164
Author: jf
Time: 14 July 2008, 2:13:46 am
UUID: a43e950f-083b-e145-a771-90a30169a632
Ancestors: Seaside-Core-jf.163

Allow action callbacks access to the value given in the URL if they pass in  
a
one-argument block (needed to allow SUCallback to be side-effect free)

Name: Seaside-Core-jf.165
Author: jf
Time: 14 July 2008, 2:24:03 am
UUID: 31a42a97-3f83-f649-9284-09092072fb1f
Ancestors: Seaside-Core-jf.164

Oops... #valueWithPossibleArgument *is* made available on ported platforms  
so we can
use it. It's only the variant that takes multiple arguments that is  
unavailable.



-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings