[Seaside-dev] Issue 158 in seaside: Process callbacks outside the components

[codesite-noreply at google.com]

Issue 158: Process callbacks outside the components
http://code.google.com/p/seaside/issues/detail?id=158

Comment #3 by jfitzell:
More fixes... I wonder whether things that are calling  
WARenderCanvas>>callbacks
should change to use "context callbacks"?


Name: Seaside-Core-jf.278
Author: jf
Time: 7 October 2008, 10:27:34 pm
UUID: 782db400-9cf0-ed41-ac0d-0ae0e96f4e2c
Ancestors: Seaside-Core-jf.277

Finish moving callback storage into WACallbackRegistry.

Somehow in my previous commits I left a weird loop where you would ask the  
callback
registry to store a callback, and it would ask the context, and then the  
context
would store it in the registry.

Name: Seaside-Canvas-jf.9
Author: jf
Time: 7 October 2008, 10:30:26 pm
UUID: 5576e129-a26d-2c42-b5dc-c760b0b50d33
Ancestors: Seaside-Canvas-jf.8

stop storing callbacks in the Canvas; get them from the context instead

Name: Seaside-Component-jf.12
Author: jf
Time: 7 October 2008, 10:31:45 pm
UUID: 073b963c-938d-7c4c-86a1-55f551f97075
Ancestors: Seaside-Component-lr.11

updates to make sure we are always getting the callbacks from the context,  
not
creating a new registry.

Name: Seaside-Development-jf.9
Author: jf
Time: 7 October 2008, 10:32:36 pm
UUID: 90e6a4de-145c-6b42-890b-4fb441856996
Ancestors: Seaside-Development-jf.8

updates to make sure we are always getting the callbacks from the context,  
not
creating a new registry.

Name: Scriptaculous-Core-jf.42
Author: jf
Time: 7 October 2008, 10:40:11 pm
UUID: 48402e2c-8e7f-1b41-9ea8-cc68653b700d
Ancestors: Scriptaculous-Core-lr.41

updates to deal with callbacks being stored in WACallbackRegistry and the  
canvas not
holding onto the callback registry anymore.

Name: Scriptaculous-Tests-Core-jf.9
Author: jf
Time: 7 October 2008, 10:40:53 pm
UUID: 1558d0cd-8075-ce47-b5d8-6c1ae9bac271
Ancestors: Scriptaculous-Tests-Core-lr.8

updates to deal with callbacks being stored in WACallbackRegistry and the  
canvas not
holding onto the callback registry anymore.

Name: RSS-Core-jf.19
Author: jf
Time: 7 October 2008, 10:41:40 pm
UUID: d9449a5e-393b-d848-a1d8-70da1749f1fa
Ancestors: RSS-Core-jf.18

updates to deal with callbacks being stored in WACallbackRegistry and the  
canvas not
holding onto the callback registry anymore.



-- 
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