If that works better for dependency management and so on, please feel free.<br><br>Julian<br><br><div class="gmail_quote">On Fri, Jul 19, 2013 at 9:48 PM, Johan Brichau <span dir="ltr"><<a href="mailto:johan@inceptive.be" target="_blank">johan@inceptive.be</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
The following suggestion of Diego is probably a good idea. In essence: create a separate project for Grease.<br>
Since both Seaside3.1 and Seaside3.0 define their own 'Grease', does it not make sense to move it to its own repository?<br>
<br>
Meanwhile, I also fixed loading into Pharo1.4<br>
<div class="im HOEnZb"><br>
On 19 Jul 2013, at 16:55, Diego Lont <<a href="mailto:diego.lont@delware.nl">diego.lont@delware.nl</a>> wrote:<br>
<br>
> > The reference to Grease on Smalltalkhub is incorrect, as it contains only one package. I guess we should create a Grease project also under Seaside.<br>
<br>
</div><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>