[Seaside] Browser problem after installing seaside

Dale Henrichs dhenrich at vmware.com
Wed Oct 12 07:56:56 UTC 2011


On September 11, when the 3.0.6 config was released (one short month ago). The config had been loaded and tested on the following platforms:
Configuration loaded and passing tests[1] on the following platforms:

  GemStone 1.0-beta.8.6

[1] except for a number of Swazoo test failures and errors

Of course a lot of water has passed under the bridge for Pharo in the last month...If you can find some of those older versions of Pharo you might have better luck....I think some of the configurations that Seaside depends upon have been broken somehow .... 

I won't have time to look at any of this stuff until early next week (if I'm lucky)....


----- Original Message -----
| From: "Panu Suominen" <panu.suominen at iki.fi>
| To: "Seaside - general discussion" <seaside at lists.squeakfoundation.org>
| Sent: Wednesday, October 12, 2011 12:36:28 AM
| Subject: Re: [Seaside] Browser problem after installing seaside
| Same thing here Seaside 3.0.6 does not load with Pharo at all. It
| seems just broke the image. Problems occur with 1.2.1, 1.3 and 1.4
| 14163. Errors do differ.
| With Pharo 1.3 and 1.2.1 loading stops with warning about missing
| class SmallintContext (Seaside-Slime-jok.80). With 1.4 codes won't
| load because lots of OB-classes seem to be missing.
| Problems are easy to reproduce. Take clean image and load.
| On which Pharo version Seaside 3.0.6 is supposed to load?
| --
| Panu
| _______________________________________________
| seaside mailing list
| seaside at lists.squeakfoundation.org
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list