I've checked a fix in and marked the issue as fixed:<div><a href="http://code.google.com/p/seaside/issues/detail?id=610">http://code.google.com/p/seaside/issues/detail?id=610</a></div><div><br><div class="gmail_quote">
On 6 November 2010 14:10, Julian Fitzell <span dir="ltr"><<a href="mailto:jfitzell@gmail.com">jfitzell@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
The general pattern I'm advocating is to extend Grease first from the<br>
package that requires the functionality (so in this case in the<br>
Welcome package). As soon as we find multiple things using it, we can<br>
move it and will have a better clue where to move it up to.<br>
<br>
In either case, I suggest adding methods with a #seaside prefix<br>
initially. If at some point we're confident with the interface and<br>
feel it is generally useful, we can add non-prefixed versions and<br>
deprecate the original methods to call the new ones.</blockquote><div><br></div><div>I've added extension methods from *seaside-welcome</div><div><br></div><div>GRPlatform>>#seasideIsAuthorNameSet</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>self subclassResponsibility</div>
<div><br></div><div>GRPlatform>>#seasideSetAuthorName: anAuthorName</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>self subclassResponsibility</div><div><br></div><div>and the corresponding implementations in GRPharoPlatform</div>
<div><br></div><div>Nick </div></div></div>