[Seaside-dev] Issue 69 in seaside: printOn: a WAUrlEncoder can get interesting when no WACurrentContext on stack

[codesite-noreply at google.com]

Issue 69: printOn: a WAUrlEncoder can get interesting when no 
WACurrentContext on stack
http://code.google.com/p/seaside/issues/detail?id=69

Comment #2 by jfitzell:
Ah, just stumbled across this bug. I'd rather use a NullCodec otherwise doing
development just seems painful. In fact, I already committed this 
change in:

---------------
Name: Seaside-Core-jf.183
Author: jf
Time: 29 July 2008, 12:25:59 pm
UUID: 7dc4db18-c648-cd4d-81c8-5c485b9a3d0f
Ancestors: Seaside-Core-jf.182

Have WAUrlEncoder use a null codec if it can't find any other in the 
request context.
------------------

As per our discussion on the list, though, this introduces a dependency 
the wrong way
with Seaside-Adapters-Core. So either we pull WANullCodec and WACodec 
into core or we
implement WAUrl>>printOn: so it doesn't need a codec and does an 
approximation the
dev tools can use and WAUrl>>toString so it uses the original codec implementation.

Or we decide it doesn't matter that you can't easily work with WAUrl 
objects in the
debugger/inspector... seems a shame though.



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