[Seaside-dev] Issue 1 in seaside: WAInspector>>#evaluate nonportable

[codesite-noreply at google.com]

Issue 1: WAInspector>>#evaluate nonportable
http://code.google.com/p/seaside/issues/detail?id=1

Comment #17 by da... at teleport.com:
I like the idea of at least a skeleton of the implementation sitting in the  
core (or
dev) packages ... Like the inspector, there are only a handful of things  
that need to
be ported and the rest of the implementation is fine ... so unless the  
class is
completely empty, I'd be inclined to leave it there...

I also like the idea of registering platform-specific  
implementations...makes it
possible to have multiple inspectors or debuggers (production vs  
development) even in
the platform-specific case.



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