Hi everyone,
Seaside 3.2.0 is now final: https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog
Check out the Github pages for more information: - https://github.com/SeasideSt/Seaside https://github.com/SeasideSt/Seaside - https://github.com/SeasideSt/Seaside/wiki https://github.com/SeasideSt/Seaside/wiki
If you experience issues, do not hesitate to report an issue via Github.
Special thanks goes to all those who have helped, tested or contributed in some other way!
On Thu, May 5, 2016 at 4:21 PM, Johan Brichau johan@inceptive.be wrote:
Hi everyone,
Seaside 3.2.0 is now final: https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog
Check out the Github pages for more information:
If you experience issues, do not hesitate to report an issue via Github.
Special thanks goes to all those who have helped, tested or contributed in some other way!
Cool, thank you. Do you already have a OneClick Image? We should probably go through the download page [1] and update what's no longer up to date (e.g. Jenkins build jobs).
[1] http://www.seaside.st/download/pharo
Cheers Philippe
Great!!!
Congratulations and thanks for the hard work.
What's next? Revamping Seaside's website?
Regards! Esteban A. Maringolo
2016-05-05 11:21 GMT-03:00 Johan Brichau johan@inceptive.be:
Hi everyone,
Seaside 3.2.0 is now final: https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog
Check out the Github pages for more information:
If you experience issues, do not hesitate to report an issue via Github.
Special thanks goes to all those who have helped, tested or contributed in some other way!
seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
On 06 May 2016, at 06:58, Esteban A. Maringolo emaringolo@gmail.com wrote:
What's next? Revamping Seaside's website?
Indeed. Long overdue already!
Johan
Very nice Johan… thanks a lot to all the Seaside team!
Esteban
On 05 May 2016, at 16:21, Johan Brichau johan@inceptive.be wrote:
Hi everyone,
Seaside 3.2.0 is now final: https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog
Check out the Github pages for more information:
- https://github.com/SeasideSt/Seaside https://github.com/SeasideSt/Seaside
- https://github.com/SeasideSt/Seaside/wiki https://github.com/SeasideSt/Seaside/wiki
If you experience issues, do not hesitate to report an issue via Github.
Special thanks goes to all those who have helped, tested or contributed in some other way! _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
On 06 May 2016, at 10:38, Esteban Lorenzano estebanlm@gmail.com wrote:
Very nice Johan… thanks a lot to all the Seaside team!
+10
Esteban
On 05 May 2016, at 16:21, Johan Brichau johan@inceptive.be wrote:
Hi everyone,
Seaside 3.2.0 is now final: https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog
Check out the Github pages for more information:
If you experience issues, do not hesitate to report an issue via Github.
Special thanks goes to all those who have helped, tested or contributed in some other way! _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
seaside-dev mailing list seaside-dev@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Hi,
Thanks indeed!
Could you wait until after the official Pharo 5.0 release before you send the announcement on Seaside?
Cheers, Doru
On May 6, 2016, at 10:38 AM, Esteban Lorenzano estebanlm@gmail.com wrote:
Very nice Johan… thanks a lot to all the Seaside team!
Esteban
On 05 May 2016, at 16:21, Johan Brichau johan@inceptive.be wrote:
Hi everyone,
Seaside 3.2.0 is now final: https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog
Check out the Github pages for more information:
If you experience issues, do not hesitate to report an issue via Github.
Special thanks goes to all those who have helped, tested or contributed in some other way! _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- www.tudorgirba.com www.feenk.com
"We cannot reach the flow of things unless we let go."
Ciao,
Very nice Johan… thanks a lot to all the Seaside team!
+10
Dario
Esteban
On 05 May 2016, at 16:21, Johan Brichau johan@inceptive.be wrote:
Hi everyone,
Seaside 3.2.0 is now final: https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog
Check out the Github pages for more information:
If you experience issues, do not hesitate to report an issue via Github.
Special thanks goes to all those who have helped, tested or contributed in some other way! _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Thanks Johan et al
Johan Brichau-2 wrote
Hi everyone,
Seaside 3.2.0 is now final: https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog <https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog%3E;
Check out the Github pages for more information:
<https://github.com/SeasideSt/Seaside%3E;
<https://github.com/SeasideSt/Seaside/wiki%3E;
If you experience issues, do not hesitate to report an issue via Github.
Special thanks goes to all those who have helped, tested or contributed in some other way! _______________________________________________ seaside mailing list
seaside@.squeakfoundation
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- View this message in context: http://forum.world.st/Seaside-3-2-0-final-tp4893671p4893852.html Sent from the Seaside General mailing list archive at Nabble.com.
Hi Johan and the rest of the team,
Thank you very much for taking care of such an important project.
Best,
On Sat, May 7, 2016 at 10:41 AM, Paul DeBruicker pdebruic@gmail.com wrote:
Thanks Johan et al
Johan Brichau-2 wrote
Hi everyone,
Seaside 3.2.0 is now final: https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog <https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog%3E;
Check out the Github pages for more information:
<https://github.com/SeasideSt/Seaside%3E;
<https://github.com/SeasideSt/Seaside/wiki%3E;
If you experience issues, do not hesitate to report an issue via Github.
Special thanks goes to all those who have helped, tested or contributed
in
some other way! _______________________________________________ seaside mailing list
seaside@.squeakfoundation
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- View this message in context: http://forum.world.st/Seaside-3-2-0-final-tp4893671p4893852.html Sent from the Seaside General mailing list archive at Nabble.com. _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
First thanks for the work.
Second, is there a procedure to port from pharo/Git to squeak/monticello. I would like to get the latest running on 64x64 squeak.cog.spur
thx
---- On Mon, 09 May 2016 08:35:21 -0400 Mariano Martinez Peck<marianopeck@gmail.com> wrote ----
Hi Johan and the rest of the team,
Thank you very much for taking care of such an important project.
Best,
On Sat, May 7, 2016 at 10:41 AM, Paul DeBruicker <pdebruic@gmail.com> wrote: Thanks Johan et al
Johan Brichau-2 wrote > Hi everyone, > > Seaside 3.2.0 is now final: > https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog > &lt;https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog> > > Check out the Github pages for more information: > - https://github.com/SeasideSt/Seaside > &lt;https://github.com/SeasideSt/Seaside> > - https://github.com/SeasideSt/Seaside/wiki > &lt;https://github.com/SeasideSt/Seaside/wiki> > > If you experience issues, do not hesitate to report an issue via Github. > > Special thanks goes to all those who have helped, tested or contributed in > some other way! > _______________________________________________ > seaside mailing list
> seaside@.squeakfoundation
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- View this message in context: http://forum.world.st/Seaside-3-2-0-final-tp4893671p4893852.html Sent from the Seaside General mailing list archive at Nabble.com. _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
On Mon, May 9, 2016 at 7:44 PM, gettimothy gettimothy@zoho.com wrote:
First thanks for the work.
Second, is there a procedure to port from pharo/Git to squeak/monticello. I would like to get the latest running on 64x64 squeak.cog.spur
The Metacello configuration should do this for you.
Cheers Philippe
Make sure you have installed Metacello (https://github.com/dalehenrich/metacello-work). From there on, follow the installation instructions for Seaside in Pharo.
cheers Johan
On 09 May 2016, at 19:44, gettimothy gettimothy@zoho.com wrote:
First thanks for the work.
Second, is there a procedure to port from pharo/Git to squeak/monticello. I would like to get the latest running on 64x64 squeak.cog.spur
thx
---- On Mon, 09 May 2016 08:35:21 -0400 Mariano Martinez Peckmarianopeck@gmail.com wrote ---- Hi Johan and the rest of the team,
Thank you very much for taking care of such an important project.
Best,
On Sat, May 7, 2016 at 10:41 AM, Paul DeBruicker <pdebruic@gmail.com mailto:pdebruic@gmail.com> wrote: Thanks Johan et al
Johan Brichau-2 wrote
Hi everyone,
Seaside 3.2.0 is now final: https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog <https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog%3E https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog>
Check out the Github pages for more information:
<https://github.com/SeasideSt/Seaside%3E https://github.com/SeasideSt/Seaside>
<https://github.com/SeasideSt/Seaside/wiki%3E https://github.com/SeasideSt/Seaside/wiki>
If you experience issues, do not hesitate to report an issue via Github.
Special thanks goes to all those who have helped, tested or contributed in some other way! _______________________________________________ seaside mailing list
seaside@.squeakfoundation
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- View this message in context: http://forum.world.st/Seaside-3-2-0-final-tp4893671p4893852.html http://forum.world.st/Seaside-3-2-0-final-tp4893671p4893852.html Sent from the Seaside General mailing list archive at Nabble.com. _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org mailto:seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- Mariano http://marianopeck.wordpress.com http://marianopeck.wordpress.com/ _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org mailto:seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Thanks.
Metacello 'scares' me in that it seems to morph squeak into pharo at times if I am not careful.
I will give it a go.
---- On Mon, 09 May 2016 14:32:23 -0400 Johan Brichau <johan@inceptive.be> wrote ----
Make sure you have installed Metacello (https://github.com/dalehenrich/metacello-work).From there on, follow the installation instructions for Seaside in Pharo.
cheers Johan
On 09 May 2016, at 19:44, gettimothy <gettimothy@zoho.com> wrote:
First thanks for the work.
Second, is there a procedure to port from pharo/Git to squeak/monticello. I would like to get the latest running on 64x64 squeak.cog.spur
thx
---- On Mon, 09 May 2016 08:35:21 -0400 Mariano Martinez Peck<marianopeck@gmail.com> wrote ----
Hi Johan and the rest of the team,
Thank you very much for taking care of such an important project.
Best,
On Sat, May 7, 2016 at 10:41 AM, Paul DeBruicker <pdebruic@gmail.com> wrote: Thanks Johan et al
Johan Brichau-2 wrote > Hi everyone, > > Seaside 3.2.0 is now final: > https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog > &lt;https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog> > > Check out the Github pages for more information: > - https://github.com/SeasideSt/Seaside > &lt;https://github.com/SeasideSt/Seaside> > - https://github.com/SeasideSt/Seaside/wiki > &lt;https://github.com/SeasideSt/Seaside/wiki> > > If you experience issues, do not hesitate to report an issue via Github. > > Special thanks goes to all those who have helped, tested or contributed in > some other way! > _______________________________________________ > seaside mailing list
> seaside@.squeakfoundation
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- View this message in context: http://forum.world.st/Seaside-3-2-0-final-tp4893671p4893852.html Sent from the Seaside General mailing list archive at Nabble.com. _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
On 09.05.2016, at 23:44, gettimothy gettimothy@zoho.com wrote:
Thanks.
Metacello 'scares' me in that it seems to morph squeak into pharo at times if I am not careful.
Naah, it's ok :) When I come to it, I always use the Metacello procedure for Seaside on Squeak for the all-in-ones.. Best regards -Tobias
I will give it a go.
---- On Mon, 09 May 2016 14:32:23 -0400 Johan Brichau johan@inceptive.be wrote ---- Make sure you have installed Metacello (https://github.com/dalehenrich/metacello-work). From there on, follow the installation instructions for Seaside in Pharo.
cheers Johan
On 09 May 2016, at 19:44, gettimothy gettimothy@zoho.com wrote:
First thanks for the work.
Second, is there a procedure to port from pharo/Git to squeak/monticello. I would like to get the latest running on 64x64 squeak.cog.spur
thx
---- On Mon, 09 May 2016 08:35:21 -0400 Mariano Martinez Peckmarianopeck@gmail.com wrote ---- Hi Johan and the rest of the team,
Thank you very much for taking care of such an important project.
Best,
On Sat, May 7, 2016 at 10:41 AM, Paul DeBruicker pdebruic@gmail.com wrote: Thanks Johan et al
Johan Brichau-2 wrote
Hi everyone,
Seaside 3.2.0 is now final: https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog <https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog%3E;
Check out the Github pages for more information:
<https://github.com/SeasideSt/Seaside%3E;
<https://github.com/SeasideSt/Seaside/wiki%3E;
If you experience issues, do not hesitate to report an issue via Github.
Special thanks goes to all those who have helped, tested or contributed in some other way! _______________________________________________ seaside mailing list
seaside@.squeakfoundation
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Metacello installed and Seaside 3 installed on 64x64 squeak.cog.spur per the
Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; load
I will mess around with it.
The Apps->Seaside Control Panel widget display is greyed out w/o widgets an launch.
I will review and get the Workspace commands to get the server running etc in the coming few days.
Thanks for your help.
---- On Mon, 09 May 2016 17:58:30 -0400 Tobias Pape <Das.Linux@gmx.de> wrote ----
On 09.05.2016, at 23:44, gettimothy <gettimothy@zoho.com> wrote:
> Thanks. > > Metacello 'scares' me in that it seems to morph squeak into pharo at times if I am not careful. >
Naah, it's ok :) When I come to it, I always use the Metacello procedure for Seaside on Squeak for the all-in-ones.. Best regards -Tobias
> I will give it a go. > > ---- On Mon, 09 May 2016 14:32:23 -0400 Johan Brichau <johan@inceptive.be> wrote ---- > Make sure you have installed Metacello (https://github.com/dalehenrich/metacello-work). > From there on, follow the installation instructions for Seaside in Pharo. > > cheers > Johan > > On 09 May 2016, at 19:44, gettimothy <gettimothy@zoho.com> wrote: > > First thanks for the work. > > Second, is there a procedure to port from pharo/Git to squeak/monticello. I would like to get the latest running on 64x64 squeak.cog.spur > > thx > > > > > > > ---- On Mon, 09 May 2016 08:35:21 -0400 Mariano Martinez Peck<marianopeck@gmail.com> wrote ---- > Hi Johan and the rest of the team, > > Thank you very much for taking care of such an important project. > > Best, > > On Sat, May 7, 2016 at 10:41 AM, Paul DeBruicker <pdebruic@gmail.com> wrote: > Thanks Johan et al > > > > > > > Johan Brichau-2 wrote > > Hi everyone, > > > > Seaside 3.2.0 is now final: > > https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog > > &lt;https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog> > > > > Check out the Github pages for more information: > > - https://github.com/SeasideSt/Seaside > > &lt;https://github.com/SeasideSt/Seaside> > > - https://github.com/SeasideSt/Seaside/wiki > > &lt;https://github.com/SeasideSt/Seaside/wiki> > > > > If you experience issues, do not hesitate to report an issue via Github. > > > > Special thanks goes to all those who have helped, tested or contributed in > > some other way! > > _______________________________________________ > > seaside mailing list > > > seaside@.squeakfoundation > > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
On Mon, May 09, 2016 at 05:44:53PM -0400, gettimothy wrote:
Thanks.
Metacello 'scares' me in that it seems to morph squeak into pharo at times if I am not careful.
I will give it a go.
Don't be afraid of using Metacello here, it is very appropriate.
For smaller packages in Squeak, Metacello might seem like overkill, but can be very helpful in a case like this. Seaside runs on a range of images, and it may have complex dependencies to cover all those platforms. Metacello allows a suitable configuration to be declared and easily loaded into your image (Squeak or whatever). That is a good thing.
It is also very important because it helps the Seaside developers support a wide range of target platforms. They cannot do everything for everybody, so having Metacello configurations for Squeak and other target images provides a way for people working in Squeak to help the Seaside developers to help us :-)
Dave
---- On Mon, 09 May 2016 14:32:23 -0400 Johan Brichau <johan@inceptive.be> wrote ----
Make sure you have installed Metacello (https://github.com/dalehenrich/metacello-work).From there on, follow the installation instructions for Seaside in Pharo.
cheers Johan
On 09 May 2016, at 19:44, gettimothy <gettimothy@zoho.com> wrote:
First thanks for the work.
Second, is there a procedure to port from pharo/Git to squeak/monticello. I would like to get the latest running on 64x64 squeak.cog.spur
thx
---- On Mon, 09 May 2016 08:35:21 -0400 Mariano Martinez Peck<marianopeck@gmail.com> wrote ----
Hi Johan and the rest of the team,
Thank you very much for taking care of such an important project.
Best,
On Sat, May 7, 2016 at 10:41 AM, Paul DeBruicker <pdebruic@gmail.com> wrote: Thanks Johan et al
Johan Brichau-2 wrote > Hi everyone, > > Seaside 3.2.0 is now final: > https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog > &lt;https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog> > > Check out the Github pages for more information: > - https://github.com/SeasideSt/Seaside > &lt;https://github.com/SeasideSt/Seaside> > - https://github.com/SeasideSt/Seaside/wiki > &lt;https://github.com/SeasideSt/Seaside/wiki> > > If you experience issues, do not hesitate to report an issue via Github. > > Special thanks goes to all those who have helped, tested or contributed in > some other way! > _______________________________________________ > seaside mailing list
> seaside@.squeakfoundation
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- View this message in context: http://forum.world.st/Seaside-3-2-0-final-tp4893671p4893852.html Sent from the Seaside General mailing list archive at Nabble.com. _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
On Mon, May 9, 2016 at 11:44 PM, gettimothy gettimothy@zoho.com wrote:
Thanks.
Metacello 'scares' me in that it seems to morph squeak into pharo at times if I am not careful.
You should be able to use a Squeak image plus Metacello to create the list of packages Metacello will install and then install those in a second Squeak image without Metacello.
Cheers Philippe
Hello Seasiders,
I just managed to load Seaside into a Pharo 6.0 image running on MacOS Sierra unsing
Metacello new configuration:'Seaside3'; repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; version: #stable; load.
Beside starting the ServerAdaptor manually via ZnZincServerAdaptor startOn: 8081. because of the missing class NewListModel
I had to change WAResponse>>writeStatusOn: because the used stream does not support #nextPutAll: with a Character as argument.
So I changeed in #writeAStatusOn: nextPut: $ ; to nextPut: $ charCode; in two places.
Furthermore the used stream does not support #crlf so I added it to ZdcAbstractSocketStream.
Now I can open the examples etc.
That was easy :-)
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). I tracked it down to the use of Umlauts (äüö) in the rendered pages.
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.
Is there something wrong with my setup or is it a bug? Many thanks for any hints.
Happy coding,
Dietmar
Hi Dietmar,
Regarding Seaside 3.2 on Pharo 6: You were just ahead of me today. There was no stable version of Seaside 3.2 that worked on Pharo 6, until now. If you reload the stable version, you should get a working version. (There was ongoing work for Seaside 3.3 that included Pharo 6 fixes, but it was not finished yet.)
Regadering the changes you had to make and the problems with umlauts: I cannot reproduce them. I suspect there is something you do in your Seaside app that changes the Stream class that is used to render. Which Seaside version did your app work well on?
best Johan
On 9 Jun 2017, at 16:35, Dietmar Schielke dietmar.schielke@data-experts.de wrote:
Hello Seasiders,
I just managed to load Seaside into a Pharo 6.0 image running on MacOS Sierra unsing
Metacello new configuration:'Seaside3'; repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; version: #stable; load.
Beside starting the ServerAdaptor manually via ZnZincServerAdaptor startOn: 8081. because of the missing class NewListModel
I had to change WAResponse>>writeStatusOn: because the used stream does not support #nextPutAll: with a Character as argument.
So I changeed in #writeAStatusOn: nextPut: $ ; to nextPut: $ charCode; in two places.
Furthermore the used stream does not support #crlf so I added it to ZdcAbstractSocketStream.
Now I can open the examples etc.
That was easy :-)
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). I tracked it down to the use of Umlauts (äüö) in the rendered pages.
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.
Is there something wrong with my setup or is it a bug? Many thanks for any hints.
Happy coding,
Dietmar
seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Hi Johan,
many thanks for your answer.
I just downloaded a fresh Pharo-64 install to my MacBook and loaded the latest stable Seaside as described on the Seaside-GitHub page.
Now I can start the server via Seaside Control Panel. Great, thanks for fixing it so fast :-)
Then I try to access the servers starting page I get a walk back with "Error: Improper store into indexable object".
As I stated in my previous email, the reason is that the used stream does not support #nextPutAll: with a Character as argument (and crlf too).
Thats why WAResppnse>>writeAStatusOn: crashes in the first line with nextPut: $ ;
Because I downloaded all freshly without changing anything I can't imagine, what I could have done to mess this up. A have the stack trace atached to this email. Maybe you have an idea?
All thr best,
Dietmar
ByteArray(Object)>>error: ByteArray(Object)>>errorImproperStore ByteArray(Object)>>at:put: ZdcIOBuffer>>nextPut: ZdcSocketStream(ZdcAbstractSocketStream)>>nextPut: WAComboResponse(WAResponse)>>writeStatusOn: WAComboResponse>>commit WAComboResponse>>flush ZnZincStreamingServerAdaptor>>responseFrom: [ self handle: context; responseFrom: context ] in ZnZincStreamingServerAdaptor(WAServerAdaptor)>>process: BlockClosure>>ensure: ZnZincStreamingServerAdaptor(WAServerAdaptor)>>process: [ :stream | | request | request := ZnSeasideRequest nativeRequest: aZnRequest stream: stream. super process: request ] in ZnZincStreamingServerAdaptor>>process: ZnDeferredResponse>>writeOn: ZnManagingMultiThreadedServer(ZnSingleThreadedServer)>>writeResponse:on:timing: [ self writeResponse: response on: stream timing: timing ] in ZnManagingMultiThreadedServer(ZnMultiThreadedServer)>>writeResponseSafely:on:timing: BlockClosure>>on:do: ZnManagingMultiThreadedServer(ZnMultiThreadedServer)>>writeResponseSafely:on:timing: ZnManagingMultiThreadedServer(ZnMultiThreadedServer)>>executeOneRequestResponseOn: [ [ self executeOneRequestResponseOn: stream ] whileFalse ] in ZnManagingMultiThreadedServer(ZnMultiThreadedServer)>>executeRequestResponseLoopOn: [ activeProcess psValueAt: index put: anObject. aBlock value ] in ZnCurrentServer(DynamicVariable)>>value:during: BlockClosure>>ensure: ZnCurrentServer(DynamicVariable)>>value:during: ZnCurrentServer class(DynamicVariable class)>>value:during: ZnManagingMultiThreadedServer(ZnMultiThreadedServer)>>executeRequestResponseLoopOn: [ self executeRequestResponseLoopOn: stream ] in [ [ self executeRequestResponseLoopOn: stream ] ensure: [ self logConnectionClosed: stream. self closeSocketStream: stream ] ] in [ [ [ self executeRequestResponseLoopOn: stream ] ensure: [ self logConnectionClosed: stream. self closeSocketStream: stream ] ] ifCurtailed: [ socket destroy ] ] in ZnManagingMultiThreadedServer(ZnMultiThreadedServer)>>serveConnectionsOn: BlockClosure>>ensure: [ [ self executeRequestResponseLoopOn: stream ] ensure: [ self logConnectionClosed: stream. self closeSocketStream: stream ] ] in [ [ [ self executeRequestResponseLoopOn: stream ] ensure: [ self logConnectionClosed: stream. self closeSocketStream: stream ] ] ifCurtailed: [ socket destroy ] ] in ZnManagingMultiThreadedServer(ZnMultiThreadedServer)>>serveConnectionsOn: BlockClosure>>ifCurtailed: [ [ [ self executeRequestResponseLoopOn: stream ] ensure: [ self logConnectionClosed: stream. self closeSocketStream: stream ] ] ifCurtailed: [ socket destroy ] ] in ZnManagingMultiThreadedServer(ZnMultiThreadedServer)>>serveConnectionsOn: [ self value. Processor terminateActive ] in BlockClosure>>newProcess
Von: Johan Brichau johan@inceptive.be An: Seaside - general discussion seaside@lists.squeakfoundation.org Datum: 09.06.2017 19:36 Betreff: Re: [Seaside] Seaside and Pharo 6: Problem with Umlauts? Gesendet von: "seaside" seaside-bounces@lists.squeakfoundation.org
Hi Dietmar,
Regarding Seaside 3.2 on Pharo 6: You were just ahead of me today. There was no stable version of Seaside 3.2 that worked on Pharo 6, until now. If you reload the stable version, you should get a working version. (There was ongoing work for Seaside 3.3 that included Pharo 6 fixes, but it was not finished yet.)
Regadering the changes you had to make and the problems with umlauts: I cannot reproduce them. I suspect there is something you do in your Seaside app that changes the Stream class that is used to render. Which Seaside version did your app work well on?
best Johan
On 9 Jun 2017, at 16:35, Dietmar Schielke < dietmar.schielke@data-experts.de> wrote:
Hello Seasiders,
I just managed to load Seaside into a Pharo 6.0 image running on MacOS Sierra unsing
Metacello new configuration:'Seaside3'; repository: ' http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; version: #stable; load.
Beside starting the ServerAdaptor manually via ZnZincServerAdaptor startOn: 8081. because of the missing class NewListModel
I had to change WAResponse>>writeStatusOn: because the used stream does not support #nextPutAll: with a Character as argument.
So I changeed in #writeAStatusOn: nextPut: $ ; to nextPut: $ charCode; in two places.
Furthermore the used stream does not support #crlf so I added it to ZdcAbstractSocketStream.
Now I can open the examples etc.
That was easy :-)
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). I tracked it down to the use of Umlauts (äüö) in the rendered pages.
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.
Is there something wrong with my setup or is it a bug? Many thanks for any hints.
Happy coding,
Dietmar
_______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Hi Dietmar,
Now I can start the server via Seaside Control Panel. Great, thanks for fixing it so fast :-)
The working version of the package was there, it just was not in the Configuration. Just to say: I just made the hard work of others visible :)
Then I try to access the servers starting page I get a walk back with "Error: Improper store into indexable object".
As I stated in my previous email, the reason is that the used stream does not support #nextPutAll: with a Character as argument (and crlf too).
Thats why WAResppnse>>writeAStatusOn: crashes in the first line with nextPut: $ ;
Because I downloaded all freshly without changing anything I can't imagine, what I could have done to mess this up. A have the stack trace atached to this email. Maybe you have an idea?
Ok, I notice you are using the ZnZincStreamingServerAdaptor. So, that does not seem to work.
Try the ZnZincServerAdaptor, that one works.
Do you require a streaming server?
I’ll poke around to see if this is supposed to work…
Johan
Hi Johan,
thanks for your answer! Yes, I tried ZnZincServerAdaptor and with it I can access the starting page and even the WACounter demo works with Umlauts.
I think I need the streaming server adaptor because I want to port a pre 3.0 Seaside app and this application uses ajax/Comet in some places and I think this requires a streaming server. Now I start porting my old seaside application and I will see, how it works out.
Greetings,
Dietmar
Von: Johan Brichau johan@inceptive.be An: Seaside - general discussion seaside@lists.squeakfoundation.org Datum: 12.06.2017 20:46 Betreff: Re: [Seaside] Antwort: Re: Seaside and Pharo 6: Problem with Umlauts? Gesendet von: "seaside" seaside-bounces@lists.squeakfoundation.org
Hi Dietmar,
Now I can start the server via Seaside Control Panel. Great, thanks for fixing it so fast :-)
The working version of the package was there, it just was not in the Configuration. Just to say: I just made the hard work of others visible :)
Then I try to access the servers starting page I get a walk back with "Error: Improper store into indexable object".
As I stated in my previous email, the reason is that the used stream does not support #nextPutAll: with a Character as argument (and crlf too).
Thats why WAResppnse>>writeAStatusOn: crashes in the first line with nextPut: $ ;
Because I downloaded all freshly without changing anything I can't imagine, what I could have done to mess this up. A have the stack trace atached to this email. Maybe you have an idea?
Ok, I notice you are using the ZnZincStreamingServerAdaptor. So, that does not seem to work.
Try the ZnZincServerAdaptor, that one works.
Do you require a streaming server?
I?ll poke around to see if this is supposed to work?
Johan_______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Hello Seasiders,
I wonder how to asynchronously update the view from the model in the actual seaside version. In pre 3.0 times I used a CTPusher from the Comet library. Is this still the state of the art?
Greetings,
Dietmar
Hi,
Sorry for reviving this old thread. I was thinking how to solve a particular problem and I was also thinking on Comet. Does someone know the state of it?
Thanks
On Thu, Jun 22, 2017 at 10:14 AM, Dietmar Schielke < dietmar.schielke@data-experts.de> wrote:
Hello Seasiders,
I wonder how to asynchronously update the view from the model in the actual seaside version. In pre 3.0 times I used a CTPusher from the Comet library. Is this still the state of the art?
Greetings,
Dietmar _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
On Wed, Aug 16, 2017 at 4:07 PM, Mariano Martinez Peck marianopeck@gmail.com wrote:
Hi,
Sorry for reviving this old thread. I was thinking how to solve a particular problem and I was also thinking on Comet. Does someone know the state of it?
I would generally recommend against using it. It's an implementation of the "forever iframe". This has been superseded by server-sent evens (which are amazing but don't work on IE) or WebSockets. In addition it's no longer maintained so you're on your own. AFAIK there are two WebSockets implementations out there, one for WebClient and one for Zinc. If you're on one of those I would look into integrating those. Unfortunately we do not yet have out of the box for this in Seaside but you should be able to get hold of the underlying request object and then switch to the proprietary API.
Cheers Philippe
seaside@lists.squeakfoundation.org