<div dir="ltr">Hello everyone,<div>If someone would give commit rights to user jmckeon I will post the updates.</div><div>Thanks</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 21, 2014 at 7:46 PM, John McKeon <span dir="ltr"><<a href="mailto:p3anoman@gmail.com" target="_blank">p3anoman@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Seasode-Developers<div>I would like your opinions on proceeding with the creation of a Grease platform for Squeak. The question arises, why not just subclass GRPharoPlatform and override the few methods that need overriding for Squeak and be done with it. Things would be much simpler than the alternative method of copying GRPharoPlatform and making it Squeak's own. This path not only requires quite a bit of class copying (mostly the codecs amd related streams), but also requires a duplication of every Seaside-Pharo-• package to a Seaside-Squeak-• package as well (unless ther is something I am missing). Not to mention the rewiring of the ConfiguationOfSeaside3 that would be necessary.</div><div>So, in light of the close relationship of Pharo to Squeak and the overwhelming amount of code reuse that it would afford, is subclassing that bad?</div><div>I look forward to your thoughts</div><div><br></div><div>Happy Trails</div><span class="HOEnZb"><font color="#888888"><div>John McKeon</div>
<br><br>-- <br><a href="http://jmck.seasidehosting.st" target="_blank">jmck.seasidehosting.st</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><a href="http://jmck.seasidehosting.st" target="_blank">jmck.seasidehosting.st</a></div>
</div>