Thanks Keith.
Loading the versions that you pointed to worked.
As a new comer to Squeak, I find SqueakMap vs Montecillo quite confusing. I thought that stable versions were in SqueakMap. Wrong?
Thierry
The current streams for Seaside are, 2.6b1 for the "stable" and 2.7a "cutting edge"
2.6b1 has WADispatcherEditorPlugin as do some recent 2.7a packages. For some reason the latest 2.7a package has not had it merged in yet.
Magam seaside-kph.20 (<- the one I ended up loading)
This one was submitted to the server in error, and only the project administrator can remove it. ( Chris? )
You need the Magma-seaside one.
Thierry Thelliez wrote:
Thanks Keith.
Loading the versions that you pointed to worked.
As a new comer to Squeak, I find SqueakMap vs Montecillo quite confusing. I thought that stable versions were in SqueakMap. Wrong?
Thierry
Right- ish (for non-moving targets the may be the case)
In this case the package maintainers publish a stable release every now and then to SqueakMap.
For those of us integrating more than one package, we tend to make fixes/tweaks to both of those packages in the process, but since we are specialist users this is not always sufficient to provoke the maintainers to go to the effort of a new release to squeakmap.
This is why I developed Installer, so that it would be relatively easy to publish a custom image generating scripts based upon with Squeakmap releases or specific/latest monticello releases.
I didnt go ahead and recreate the SMP image because someone else was doing it (they told me on IRC) unfortunately they later informed me that their machine crashed and they lost the work that they had done.
I am currently working on a system to automate the building and testing of specialist images. This automation works, but I am now adding the ability to have descendant images.
For example, If I take 3.9-final as a starting point, and build an image which adds a number of bug fixes to 3.9, we get a new image, lets call it 3.9.1. This in turn can be the new parent image for a number of children, of which a Seaside image could be one, whose child could be a Seaside-Magma image, or indeed in turn a Seaside-Magma-Pier image. In practice the important thing will be the testing of such images, so it will not really be necessary to generate every intermediate.
watch this space
Keith
___________________________________________________________ All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of use." - PC Magazine http://uk.docs.yahoo.com/nowyoucan.html
Dont forget to have a look at the simplest Seaside Magma example in.
Seaside-Store-Example-Magma in MagmaTester repository
The next simplest is the Pier-Magma stuff that I did, this includes a shared magma session. (Similar, but simpler than GJallars magma session pools) Pier has a mutex preventing concurrent edits to its model, therefore it is safe for one magma session to be shared by all users. It also includes some use of ReadStrategies.
Keith
___________________________________________________________ Try the all-new Yahoo! Mail. "The New Version is radically easier to use" The Wall Street Journal http://uk.docs.yahoo.com/nowyoucan.html
magma@lists.squeakfoundation.org