seaside September 2013

seaside@lists.squeakfoundation.org

29 participants
33 discussions

Configuration of Seaside and Zinc
by MaxBareis 10 Sep '13

10 Sep '13

Hi, when trying to load ConfigurationOfSeaside30 from a fresh Pharo2.0 image I get the error "Cannot resolve host mc.sftx.eu". When changing the wrong URL to mc.stfx.eu in the debug window the name is resolved but the error Could Not Resolve: Configuration of ZincHTTPComponents pops up. How may I get the Seaside 30 version? Thanks Max -- View this message in context: http://forum.world.st/Configuration-of-Seaside-and-Zinc-tp4707457.html Sent from the Seaside General mailing list archive at Nabble.com.

2 2

Zinc as static file server
by Paul DeBruicker 07 Sep '13

07 Sep '13

Hi - Following these instructions you can make Comanche serve static files from a local directory while also handling Seaside requests: http://samadhiweb.com/blog/2011.07.10.seaside.comanche.staticfiles.html Is there a way to do the same with Zinc and the ZnStaticFileServerDelegate ? Thanks Paul

5 22

Re: Problem upgrading seaside from an existing image (Pharo #14438 and Seaside 3.0)
by Stephan Eggermont 06 Sep '13

06 Sep '13

Dave wrote >I see, but in the package cache you can have several versions of a package, >only monticello shows the right version that image is using. Am I wrong? This was with fresh images, so the package cache shows the packages downloaded while running Gofer new url:'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; package: 'ConfigurationOfSeaside3'; load. (Smalltalk at: #ConfigurationOfSeaside3) project load: #stable at least up to the crash. Configurations only check if Metacello is loaded, not which version is loaded You might want to upgrade Metacello first. Stephan

2 1

Re: Problem upgrading seaside from an existing image (Pharo #14438 and Seaside 3.0)
by Stephan Eggermont 06 Sep '13

06 Sep '13

When comparing the ConfigurationOf... loaded In 14438 we have ConfigurationOfGofer-dkh.39.mcz which isn't in 14449 Also 14438 needed newer monticello and metacello packages. Stephan

2 1

Re: Problem upgrading seaside from an existing image (Pharo #14438 and Seaside 3.0)
by Stephan Eggermont 05 Sep '13

05 Sep '13

Repeatable in 14437

2 1

Re: Problem upgrading seaside from an existing image (Pharo #14438 and Seaside 3.0)
by Stephan Eggermont 05 Sep '13

05 Sep '13

14449 no longer shows the problem. (Complains about Zinc-HTTP though) It loads Comet-Core-lr.51.mcz Comet-Examples-lr.23.mcz Comet-Pharo-Core-lr.6.mcz Comet-Tests-Core-lr.11.mcz ConfigurationOfGrease-MattSpr.207.mcz ConfigurationOfOmniBrowser-topa.185.mcz ConfigurationOfRefactoringBrowser-topa.76.mcz ConfigurationOfSPort2-DamienCassou.11.mcz ConfigurationOfSeaside3-DiegoLont.15.mcz ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.52.mcz Grease-Core-NickAger.70.mcz Grease-Pharo-Core-JohanBrichau.52.mcz Grease-Slime-topa.15.mcz Grease-Tests-Core-pmm.80.mcz Grease-Tests-Pharo-Core-lr.13.mcz Grease-Tests-Slime-JohanBrichau.11.mcz JQuery-Core-lr.123.mcz JQuery-Tests-Core-NickAger.132.mcz JQuery-Tests-UI-pmm.82.mcz JQuery-UI-lr.80.mcz Javascript-Core-pmm.92.mcz Javascript-Pharo-Core-DaleHenrichs.9.mcz Javascript-Tests-Core-pmm.66.mcz Javascript-Tests-Pharo-Core-lr.1.mcz OB-Standard-EstebanLorenzano.552.mcz Prototype-Core-lr.25.mcz Prototype-Tests-Core-lr.13.mcz RSS-Core-lr.67.mcz RSS-Examples-lr.26.mcz RSS-Tests-Core-lr.30.mcz Scriptaculous-Components-lr.111.mcz Scriptaculous-Core-pmm.102.mcz Scriptaculous-Tests-Components-lr.39.mcz Scriptaculous-Tests-Core-pmm.61.mcz Seaside-Canvas-JohanBrichau.118.mcz Seaside-Component-jok.92.mcz Seaside-Core-JohanBrichau.769.mcz Seaside-Development-pmm.156.mcz Seaside-Email-lr.21.mcz Seaside-Environment-NickAger.77.mcz Seaside-Examples-lr.23.mcz Seaside-FileSystem-pmm.26.mcz Seaside-Flow-pmm.23.mcz Seaside-HTML5-pmm.28.mcz Seaside-InternetExplorer-pmm.7.mcz Seaside-Pharo-Canvas-lr.3.mcz Seaside-Pharo-Continuation-lr.5.mcz Seaside-Pharo-Core-JohanBrichau.17.mcz Seaside-Pharo-Development-lr.57.mcz Seaside-Pharo-Email-lr.13.mcz Seaside-Pharo-Environment-lr.6.mcz Seaside-Pharo-Flow-lr.5.mcz Seaside-Pharo-Tools-OmniBrowser.pharoOB-NickAger.7.mcz Seaside-Pharo-Tools-Web-NickAger.39.mcz Seaside-Pharo-Welcome-NickAger.2.mcz Seaside-RenderLoop-lr.73.mcz Seaside-Session-pmm.157.mcz Seaside-Slime-JohanBrichau.83.mcz Seaside-Tests-Canvas-dkh.58.mcz Seaside-Tests-Component-jok.33.mcz Seaside-Tests-Core-NickAger.257.mcz Seaside-Tests-Development-pmm.43.mcz Seaside-Tests-Email-lr.14.mcz Seaside-Tests-Environment-lr.27.mcz Seaside-Tests-Examples-lr.9.mcz Seaside-Tests-FileSystem-lr.13.mcz Seaside-Tests-Flow-dkh.34.mcz Seaside-Tests-Functional-pmm.142.mcz Seaside-Tests-HTML5-pmm.28.mcz Seaside-Tests-InternetExplorer-lr.9.mcz Seaside-Tests-Pharo-Continuation-lr.8.mcz Seaside-Tests-Pharo-Core-JohanBrichau.26.mcz Seaside-Tests-Pharo-Development-pmm.24.mcz Seaside-Tests-Pharo-Email-pmm.1.mcz Seaside-Tests-Pharo-Functional-lr.13.mcz Seaside-Tests-RenderLoop-lr.11.mcz Seaside-Tests-Session-lr.49.mcz Seaside-Tests-Slime-JohanBrichau.43.mcz Seaside-Tests-Tools-Web-lr.18.mcz Seaside-Tests-UTF8-lr.10.mcz Seaside-Tests-Welcome-lr.6.mcz Seaside-Tools-Core-lr.19.mcz Seaside-Tools-OmniBrowser-lr.25.mcz Seaside-Tools-Web-NickAger.113.mcz Seaside-Welcome-NickAger.40.mcz Seaside-Widgets-lr.26.mcz Sport-2.033.mcz Zinc-Character-Encoding-Core-SvenVanCaekenberghe.21.mcz Zinc-FileSystem-Legacy-SvenVanCaekenberghe.5.mcz Zinc-HTTP-SvenVanCaekenberghe.375.mcz Zinc-Pharo-Forward-Compatibility-SvenVanCaekenberghe.1.mcz Zinc-Resource-Meta-Core-SvenVanCaekenberghe.17.mcz Zinc-Seaside-SvenVanCaekenberghe.40.mcz Zinc-Tests-SvenVanCaekenberghe.194.mcz

1 0

Re: Problem upgrading seaside from an existing image (Pharo #14438 and Seaside 3.0)
by Stephan Eggermont 05 Sep '13

05 Sep '13

Yes, it is a repeatable problem. I can reproduce it from a clean 14438

1 0

Re: Problem upgrading seaside from an existing image (Pharo #14438 and Seaside 3.0)
by Stephan Eggermont 05 Sep '13

05 Sep '13

Repeatable from a clean Pharo 14438? Stephan

1 0

Re: Problem upgrading seaside from an existing image (Pharo #14438 and Seaside 3.0)
by Stephan Eggermont 05 Sep '13

05 Sep '13

Stable version from march doesn't sound good. I remember some vm problems at that time. http://forum.world.st/Re-Latest-pharo-issue-with-Eliot-s-latest-Cog-td46764… http://forum.world.st/Re-where-to-report-vm-crashes-while-running-Moose-tes… http://forum.world.st/where-to-report-vm-crashes-while-running-Moose-tests-… I got these from http://files.pharo.org/vm/pharo/mac/ Stephan

2 1

Re: Problem upgrading seaside from an existing image (Pharo #14438 and Seaside 3.0)
by Stephan Eggermont 05 Sep '13

05 Sep '13

Mac 10.6.8, a recent vm & image 14459 'NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Sep 3 2013, NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Sep 3 2013, git@github.com:pharo-project/pharovm.git Commit: 581a11414063fec0e53f047ca90de5e1b6d3b188 Date: 2013-08-28 15:11:08 +0200 By: GuillePolito <guillermopolito(a)gmail.com> Jenkins build #14636' seems to work fine too. Refers to an older Zinc version though. When looking at the differences between 14438 and latest monticello packages for 1.4, there are a few ugly ones (joining dictionaries, hash of methods). Could be a vm problem otherwise. Stephan

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside September 2013