<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Dietmar,<div class=""><br class=""></div><div class="">Regarding Seaside 3.2 on Pharo 6: You were just ahead of me today. </div><div class="">There was no stable version of Seaside 3.2 that worked on Pharo 6, until now.</div><div class="">If you reload the stable version, you should get a working version.</div><div class="">(There was ongoing work for Seaside 3.3 that included Pharo 6 fixes, but it was not finished yet.)</div><div class=""><br class=""></div><div class="">Regadering the changes you had to make and the problems with umlauts: I cannot reproduce them.</div><div class="">I suspect there is something you do in your Seaside app that changes the Stream class that is used to render.</div><div class="">Which Seaside version did your app work well on?</div><div class=""><br class=""></div><div class="">best</div><div class="">Johan</div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On 9 Jun 2017, at 16:35, Dietmar Schielke <<a href="mailto:dietmar.schielke@data-experts.de" class="">dietmar.schielke@data-experts.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><font size="2" face="sans-serif" class="">Hello Seasiders,</font>
<br class="">
<br class=""><font size="2" face="sans-serif" class="">I just managed to load Seaside into
a Pharo 6.0 image running on MacOS Sierra unsing</font>
<br class="">
<br class=""><font size="2" face="sans-serif" class="">Metacello new</font>
<br class=""><font size="2" face="sans-serif" class=""> configuration:'Seaside3';</font>
<br class=""><font size="2" face="sans-serif" class=""> repository: '<a href="http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main" class="">http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main</a>';</font>
<br class=""><font size="2" face="sans-serif" class=""> version: #stable;</font>
<br class=""><font size="2" face="sans-serif" class=""> load.</font>
<br class="">
<br class=""><font size="2" face="sans-serif" class="">Beside starting the ServerAdaptor manually
via </font>
<br class=""><font size="2" face="sans-serif" class=""> ZnZincServerAdaptor
startOn: 8081.</font>
<br class=""><font size="2" face="sans-serif" class="">because of the missing class NewListModel</font>
<br class="">
<br class=""><font size="2" face="sans-serif" class="">I had to change </font>
<br class=""><font size="2" face="sans-serif" class=""> WAResponse>>writeStatusOn:</font>
<br class=""><font size="2" face="sans-serif" class="">because the used stream does not support</font>
<br class=""><font size="2" face="sans-serif" class=""> #nextPutAll:
with a Character as argument.</font>
<br class="">
<br class=""><font size="2" face="sans-serif" class="">So I changeed in #writeAStatusOn:</font>
<br class=""><font size="2" face="sans-serif" class=""> nextPut:
$ ;</font>
<br class=""><font size="2" face="sans-serif" class="">to </font>
<br class=""><font size="2" face="sans-serif" class=""> nextPut:
$ charCode;</font>
<br class=""><font size="2" face="sans-serif" class="">in two places.</font>
<br class="">
<br class=""><font size="2" face="sans-serif" class="">Furthermore the used stream does not
support </font>
<br class=""><font size="2" face="sans-serif" class=""> #crlf</font>
<br class=""><font size="2" face="sans-serif" class="">so I added it to ZdcAbstractSocketStream.</font>
<br class="">
<br class=""><font size="2" face="sans-serif" class="">Now I can open the examples etc.</font>
<br class="">
<br class=""><font size="2" face="sans-serif" class="">That was easy :-)</font>
<br class="">
<br class=""><font size="2" face="sans-serif" class="">Now I tried to deploy an old Seaside
App written by me and got "cannot parse response" error in my
webbrowser (no debugger in the VM).</font>
<br class=""><font size="2" face="sans-serif" class="">I tracked it down to the use of Umlauts
(äüö) in the rendered pages.</font>
<br class="">
<br class=""><font size="2" face="sans-serif" class="">As a simple demo of this problem I changed
the WACounter example. If I add a german Umlaut to the "++" or
"--" label I get a "cannot parse response" in my browser
upon rendering the WACounter expample.</font>
<br class="">
<br class=""><font size="2" face="sans-serif" class="">Is there something wrong with my setup
or is it a bug? </font>
<br class=""><font size="2" face="sans-serif" class="">Many thanks for any hints.</font>
<br class="">
<br class=""><font size="2" face="sans-serif" class="">Happy coding,</font>
<br class="">
<br class=""><font size="2" face="sans-serif" class="">Dietmar</font>
<br class="">
<br class="">
<br class="">_______________________________________________<br class="">seaside mailing list<br class=""><a href="mailto:seaside@lists.squeakfoundation.org" class="">seaside@lists.squeakfoundation.org</a><br class="">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside<br class=""></div></blockquote></div><br class=""></div></body></html>