[Seaside-dev] Issue 218 in seaside: WADispatcherEditor doing a
#call: in #initialRequest:
codesite-noreply at google.com
codesite-noreply at google.com
Fri Nov 28 15:57:30 UTC 2008
Updates:
Status: Fixed
Owner: renggli
Comment #1 on issue 218 by renggli: WADispatcherEditor doing a #call: in
#initialRequest:
http://code.google.com/p/seaside/issues/detail?id=218
This is fixed in:
Name: Seaside-Development-lr.47
Author: lr
Time: 28 November 2008, 4:45:04 pm
UUID: d9653cf2-e77b-402a-841b-b3647f72e770
Ancestors: Seaside-Development-lr.46
- fixes Issue 218: WADispatcherEditor doing a #call: in #initialRequest:
Additional improvements are in:
Name: Seaside-Development-lr.48
Author: lr
Time: 28 November 2008, 4:54:24 pm
UUID: 575a119d-7fda-4398-97b7-5802df1b75a9
Ancestors: Seaside-Development-lr.47
- use #show: instead of #call: in the configuration editor, as nowhere a
blocking behavior is required
- this makes the configuration editor work in VA and uses much less memory
--
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
More information about the seaside-dev
mailing list