On 29 June 2011 17:34, Lukas Renggli <renggli(a)gmail.com> wrote:
But before
this I downloaded the image from
http://www.seaside.st/distributions/Seaside-3.0.5-OneClick.zip
and this did *not* have the Magritte packages installed.
As the download page lists various images. The one-click image does
not contain Magritte anymore, because it was decided that the Seaside
image should only contain Seaside. However, there is another download
link just below, that lists Magritte as one of the ingredients of the
image.
Thanks. Saw that. I downloaded and saw that all was as per my understanding.
Despite that I'd prefer to load into my environment because it forces me to
understand the dependencies.
I was under the impression that Magriite was
quite fundamental to the
Seaside architecture but it appears from the dependancy list of the
Seaside
package that Magritte is not a prerequisite
(probably an error in my
understanding)
No, Seaside does not depend on Magritte, neither does Magritte depend
on Seaside. The package Magritte-Seaside just integrates Magritte with
Seaside, and is likely the most common use of Magritte.
OK I understand now. And also a likely reason for the load failure. When
loading the Magritte package the script didn't get Magritte-Seaside.
Running Nick's script (below) got it and now it's functional on the Pharo
1.2.1 image. (Strangely not on the 1.1.1 image.)
"Nicks fragment"
Gofer new
renggli: 'magritte2';
package: 'ConfigurationOfMagritte2';
load.
(ConfigurationOfMagritte2 project latestVersion) load:
#('Magritte-Seaside' 'Magritte-Tests-Model').
What is a
little more puzzling (worrying because I was planning to use
Magritte in a current project) is that when I do load the latest Seaside
and
Magritte packages in a current Pharo release
(1.1.1 and 1.2.1) they seem
to
be quite broken. Is this the Smalltalk version of
DLL hell or am I
suffering
from terminal PEBKAC failure?
I don't know why the scripts you used don't work, Dale might know more?
Running Nick's script sorted the problem on 1.2.1 but not on 1.1.1. That's
good enough for me as I've added to my (meager) understanding and reinorces
your explanation. If anyone considers this worth looking into I can provide
more details. I might say that I ,possibly reasonably, expected
Magritte-Seaside to be loaded with Magritte. Although you probably have good
reasons for seperating the installation.
You can use the latest build from my server, this is all the latest
code loaded into Pharo 1.2:
http://jenkins.lukas-renggli.ch/job/Magritte%202/ (Seaside + Magritte)
http://jenkins.lukas-renggli.ch/job/Pier%202/ (Seaside + Magritte +
Pier)
Many thanks to you and to Nick for taking time to respond. I'll study the
code
and experiment with the tests before trying anything else.
Miguel
Lukas
--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki