Hi Stef,<br><br>My point was that no 3.1.x version has been released (it's just a development branch) so it seems more logical to include the newest 3.0.x version in Pharo to me. Or to do a release of 3.1 if someone thinks it worthwhile. But others may disagree...<br>
<br>Julian<br><br><div class="gmail_quote">On Thu, Mar 7, 2013 at 6:33 AM, stephane ducasse <span dir="ltr"><<a href="mailto:stephane.ducasse@free.fr" target="_blank">stephane.ducasse@free.fr</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">If you need help to write a configuration of I can help.<div>The problem is that I do not know all the fine grained dependencies.</div><div>But I think that we can do it step by step.</div>
<div><div class="h5"><div><br><div><div>On Mar 7, 2013, at 1:18 AM, Julian Fitzell <<a href="mailto:jfitzell@gmail.com" target="_blank">jfitzell@gmail.com</a>> wrote:</div><br><blockquote type="cite">Have we even done a stable release of 3.1 yet? I don't even think all the 3.0.x fixes have been ported into the 3.1 repository...<br>
<br><div class="gmail_quote">On Mon, Mar 4, 2013 at 8:20 PM, Torsten Bergmann <span dir="ltr"><<a href="mailto:astares@gmx.de" target="_blank">astares@gmx.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi @seaside-dev (CC-ing Pharo list and seaside users list):<br>
<br>
Pharo 2.0 is upon completion and it would be good to have a working Seaside<br>
running on it out of the box using a ConfigurationOfSeaside accessible<br>
through the configuration browser.<br>
<br>
(Aida is also already working this way).<br>
<br>
What I currently know from own simple tests and postings is that it is basically<br>
working on Pharo 2.0 using this load script:<br>
<br>
<a href="https://github.com/renggli/builder/blob/master/scripts/seaside31-pharo2.st" target="_blank">https://github.com/renggli/builder/blob/master/scripts/seaside31-pharo2.st</a><br>
<br>
and then<br>
<br>
"Zinc Server"<br>
Gofer new<br>
squeaksource: 'ZincHTTPComponents';<br>
"package: 'Zinc-HTTP';"<br>
package: 'Zinc-Seaside';<br>
load.<br>
<br>
"Start Zinc"<br>
" (ZnZincServerAdaptor port: 8080)<br>
codec: GRPharoUtf8Codec new;<br>
start. "<br>
<br>
There are some small issue left in #includesSubString: vs. #includesSubstring:<br>
(now in Pharo). I found it in<br>
- WAAbstractFileLibrary>>updateRoot:,<br>
- WAFormTag>>isInternetExplorer<br>
- WARenderContext>>absoluteUrlForResource:<br>
<br>
Also when one uploads files using config -> files the methods for the uploaded<br>
content get generated but not packaged with Monticello for whatever reason.<br>
<br>
Is there a plan/timeline for having a valid Seaside on top of Pharo available.<br>
Creating an updates ConfigurationOfSeaside was also discussed here on the seaside list<br>
... but still not yet realized.<br>
We all know time is always an issue - but at least I want to start a dicussion<br>
if it is possible (maybe with the help from many using a virtual sprint).<br>
<br>
Also is there any plan in moving Seaside to SmalltalkHub as well? Since<br>
there is now infrastructure for CI ready on Pharo side it could be used for<br>
Seaside also.<br>
<br>
Any comments?<br>
<br>
If possible respond on "seaside-dev" list so it is discussed on one<br>
central place (<a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a>)<br>
<br>
Thanks<br>
T.<br>
<br>
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org" target="_blank">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</blockquote></div><br>
</blockquote></div><br></div></div></div></div></blockquote></div><br>