<div dir="ltr"><div>Thanks Paul</div><div>Last night I completed posting new Grease packages as well as updates to the ConfigurationOfGrease. It appears I've made the Seaside CI job unstable?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Mar 15, 2015 at 6:25 PM, Paul DeBruicker <span dir="ltr"><<a href="mailto:pdebruic@gmail.com" target="_blank">pdebruic@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi John,<br>
<br>
I added you to the Seaside team so you should be all set.<br>
<br>
<br>
Thanks<br>
<br>
<br>
Paul<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
John McKeon wrote<br>
<span>> Hello everyone,<br>
> If someone would give commit rights to user jmckeon I will post the<br>
> updates.<br>
> Thanks<br>
><br>
</span>> On Sun, Dec 21, 2014 at 7:46 PM, John McKeon &lt;<br>
<br>
> p3anoman@<br>
<div><div class="h5"><br>
> &gt; wrote:<br>
><br>
>> Hello Seasode-Developers<br>
>> I would like your opinions on proceeding with the creation of a Grease<br>
>> platform for Squeak. The question arises, why not just subclass<br>
>> GRPharoPlatform and override the few methods that need overriding for<br>
>> Squeak and be done with it. Things would be much simpler than the<br>
>> alternative method of copying GRPharoPlatform and making it Squeak's own.<br>
>> This path not only requires quite a bit of class copying (mostly the<br>
>> codecs<br>
>> amd related streams), but also requires a duplication of every<br>
>> Seaside-Pharo-• package to a Seaside-Squeak-• package as well (unless<br>
>> ther<br>
>> is something I am missing). Not to mention the rewiring of the<br>
>> ConfiguationOfSeaside3 that would be necessary.<br>
>> So, in light of the close relationship of Pharo to Squeak and the<br>
>> overwhelming amount of code reuse that it would afford, is subclassing<br>
>> that<br>
>> bad?<br>
>> I look forward to your thoughts<br>
>><br>
>> Happy Trails<br>
>> John McKeon<br>
>><br>
>><br>
>> --<br>
>> <a href="http://jmck.seasidehosting.st" target="_blank">jmck.seasidehosting.st</a><br>
>><br>
><br>
><br>
><br>
> --<br>
> <a href="http://jmck.seasidehosting.st" target="_blank">jmck.seasidehosting.st</a><br>
><br>
</div></div>> _______________________________________________<br>
> seaside-dev mailing list<br>
<br>
> seaside-dev@.squeakfoundation<br>
<br>
> <a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
<br>
<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://forum.world.st/Grease-for-Squeak-tp4796637p4812136.html" target="_blank">http://forum.world.st/Grease-for-Squeak-tp4796637p4812136.html</a><br>
Sent from the Seaside Development mailing list archive at Nabble.com.<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
seaside-dev mailing list<br>
<a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><a href="http://jmck.seasidehosting.st" target="_blank">jmck.seasidehosting.st</a></div>
</div>