[Seaside-dev] Issue 253 in seaside: WAPackage is partly under-defined

[codesite-noreply at google.com]

Comment #13 on issue 253 by jfitzell: WAPackage is partly under-defined
http://code.google.com/p/seaside/issues/detail?id=253

It would make sense (dependency-wise) for WAComponent>>rendererClass to  
return WARenderer but that's
inconvenient for subclasses that (particularly now since there's only one  
real renderer) all want to use
WACanvas. Plus, we can't really return anything other than WACanvas  
because, in a sense, it is now part of
WAComponent's interface contract with subclasses that it return something  
with the same interface as
WACanvas.

Adding a registry of renderers doesn't help here because of the implied  
contract. We could maybe add a
platform method #canvasClass (added by the Canvas package) and use that in  
WAComponent. That breaks the
code-level dependency while continuing the promise that  
WAComponent>>rendererClass will return a
renderer that implements the Canvas protocol (even if some platform  
provided a different implementation).

Someone who didn't want to load Canvas would just have to make sure that  
all subclasses of WAComponent
override #rendererClass.




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