[Seaside-dev] Issue 289 in seaside: Changes to Seaside-Tests-Core to address issues discovered in GemStone port

[codesite-noreply at google.com]

Comment #6 on issue 289 by philippe.marschall: Changes to  
Seaside-Tests-Core to address issues discovered in GemStone port
http://code.google.com/p/seaside/issues/detail?id=289

A lot of existing code uses it including JQAllTestsLibrary,  
JQUiAllTestsLibrary,
SUAllTestLibrary, SUComponentLibrary, WADevelopmentFiles,  
WAHandlerEditorFiles. This
is used for the toolbar, the halos, the icons, the functional tests and  
more. It's
not ideal but it worked for Seaside 2.8 even in GemStone, otherwise you  
couldn't run
Pier.

Should that no longer work in GemStone we clearly need to find a solution.  
But the
solution is not to edit one method by hand when there are dozens like it  
that look
just the same.

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