10 Jan
2010
10 Jan
'10
7:09 p.m.
As I recall, the OB and O2 collisions occured using the 2 build recommendations from
seaside.st - the cs script and the mcm file - on top of default base images. I use only
the vanilla Win32 Squeak 3.10 and the latest available Pharo and always in a fresh
directory with the addition of the squeak.exe and 2 DLL + splash + ini + .sources
I find that many Seaside class load problems are averted if you load packages into images
which have already had a Seaside running - but I have to be able to build and deploy.
I will try the method you suggest for Pharo.
--- On Sat, 1/9/10, Lukas Renggli <renggli(a)gmail.com> wrote:
From: Lukas Renggli <renggli(a)gmail.com>
Subject: Re: 3.0 merge status (observations and a code variant)
To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
Date: Saturday, January 9, 2010, 7:26 PM
There are also many places where
OmniBrowser is broken or where classes in O2 have instances
being sent messages by OB - I have not even bothered
debuggin those as they do not generally impede finding what
is needed to get a base image (Squeak 3.10) or Pharo RC-1
(pharo1.0-10502-rc1web09.12.2) to run Seaside 3.0 on Win XP
SP3
O2 has overrides in OB code. You cannot load both into one
image.
Here is my last list of classes where I comment
out
the class-side initialize until I have all nec loaded, then
uncomment all of those and let fire
This is more a Seaside related comment, but I use the
following
script. It works out of the box for me:
[ Gofer new
squeaksource: 'Seaside30';
package: 'LoadOrderTests';
load ]
valueSupplyingAnswers: {
{'Load Seaside'. true}.
{'SqueakSource User Name'. ''}.
{'SqueakSource Password'. ''}.
{'Run tests'. false}.
}
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki