First (alpha!) release of Pier running with Magma Persistency.
Image available from ftp.seasidehosting.st
User: preloaded Password: squeak
Image Use Instructions
In pier configuration click on 'Magma Control Panel', which will inform
you that the repository does not exist. If you have placed this image on
seasidehosting then you will have to manually create the repository
directory. Given the list of options as to what repository to create,
click the 'create' button (and wait). The existing pier kernel should
appear in the list with a 'persist' button next to it, click 'persist'.
Then try it and see!
Detailed Log of Image Creation Steps (alternative title: "monticello
This image was prepared as follows:
Beginning with Squeak3.8-6555full
Initial start asks for updates: select "do not ask again" - this is
important should you wish to deploy. Headless servers (e.g.
seasidehosting) cannot handle user interaction and will stop at this point.
From "world menu > open.... > Monticello Browser"
Browser opens with (Monticello....)
Click the "+Repository Button", select "HTTP" as the repository type,
as the repository info (if you have a login on Squeaksource then you can
enter your initials
as the 'user' above.)
Add the following repository for Monticello.
Add the following repository for Magma.
and the following two repositories for Magritte and Pier
(to edit this information:
click the menu button in the right hand pane of the Monticello Browser)
Loading Latest Monticello.
More recent versions of Monticello provide better feedback as to which
packages are currently loaded.
Select the http://www.squeaksource.com/Monticello repository, click
"open", select the latest package (Monticello-avi.279) from the main
"Monticello" branch, and click "load".
Select the Monticello package on the left hand pane, and the
squeaksource/Monticello repository in the right hand pane. Click 'open'.
In the repository browser, click on the latest version
(Monticello-avi.279.mcz) and click 'Load'.
Select "world menu > open... SqueakMap"... and a dialog will ask if you
wish to upgrade SqueakMap. Which you do. Notice that SMBase, SMLoader
packages appeaer in the Monticello browser, since the upgrade is
performed by loading Monticello packages.
In SqueakMap, select the ever so convenient "Seaside Installer" which
should load in the whole of seaside with its dependencies in one go. To
do this select the left had pane menu button, "install". (Part way
through the install you will be prompted to enter an admin username
(seaside) and password (admin))
(if SqueakMap doesnt work it is being knobbled by a more recent
package-cache, remove it and try again)
Select the seaside repositoryClick the "open" and the repository browser
Select Seaside2.6b1 which is the current latest. In the right hand pane
are the releases. Releases may be made by anyone and they may be small
branches off from the main stream. Periodically an effort will be made
to ensure that all changes are merged. Click the history button in order
to browse the history of this package to get some idea of what is going
on. Look at the ancestors of a package to see if one version is being
sequentially built on the next, or whether any branching is occurring.
Seaside is fairly mature and changes infrequent, therefore it is likely
to be safe to grab the latest version.
To start Seaside doit:
WAKom startOn: 8080.
( Or use the "beach flags" SeasideMorph
available from: http://minnow.cc.gatech.edu/squeak/5862 )
To test if everything is running, check the following url in your normal
you should be prompted for you username and password (as given earlier).
Back to the Monticello Browser. Deselect the selected package by
clicking on it once. This should re-reveal all of the registered
(It is worth saving this. In the right hand side pane menu button there
is a menu item: "Save Repositories", which writes a simple configuration
script to the working directory.)
Select the http://www.squeaksource.com/MagmaTester repository, and click
Select MagmaServerLoader, and click "load". (it takes a while!)
loaded Ma client server-cmm.123
loaded Ma exception handling-cmm.22
loaded Ma time objects-cmm.37
Load Magma Seaside Integration Package
Select "Magma Seaside" (lhs) and the latest package and click "load",
loaded Magma Seaside-kph.18
Load Magma Seaside Sushi Store Demo fixes
Before using Magma may need to execute the following.
MagmaSession allInstances cleanUp.
Latest Pier-Magma code
Monticello Browser - "flush cached versions".
Release Preloaded Image as Sqk3.8f-smp.image
The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html
My import through SIXX is OK.
I can load it but when I try to login, the squeak image crash.
Does someone have experienced the same problem or have an idea of the
problem origin ?
only updating the image causes trouble too.
I want to write to my textArea for example ""hi all"".
And then I would like to see hi all in bold
exactly like in WikiSystem.
I used PRDocumentParser parse: '""hi all""',
but this method returns PRDocument.
But I want reneder this string in renederContentOn: method
Please help me!
Best regards Marek Fiala
I installed all the latest packages from Monticello into a Seaside-mini
2.8 image. Everything was working well, except I had no image files.
Trying to load Pier-Styles-Kph.2.mcz results in the following
dependency missing: PRPierLibrary. I thought that would be available
from Pier-Seaside but it is not, as of Pier-Seaside-lr.251.mcz.
What can I do?
Something seems to already work because when I go to
loads and displays just fine.
Is there a way to access hidden structure (if checked in the settings).
Until now, I'm doing internal links, but if I'm sure I have some unused
Also, what's your way to make ling to internal struct ? I only use the wiki
syntax. Would you find useful to have another category (structure) when we
make a link that display the full tree of struc (the one you're authorized
to view and the hidden ones) ? Maybe such a thing already exists...
if an Object holds a collection of other Objects (like a group of Persons), and
these (Persons) should not be created/edited but a list to choose from should be
presented - would a MAMultipleOptionDescription be appropriate? If so, how can
the options presented be made dynamic. - I found, that they are getting cached
in the Default DescriptionBuilder.
Or are there options to pass to a MAToManyRelationDescription, so that it does
not show editors, but choices instead?
I am building a form that consists of two components, e.g. House and
Person. For each of these, when a new one is created I register it.
I have a manager class that displays these using:
classes: (Array with: House);
accessor: (MASelectorAccessor new
default: Array new;
People is similar. The Manager class is a form, but with no buttons
as it is only needed to let the add buttons work on these relation
descriptions. The accessor shown here, houses just calls "House
instances" to get currently registered houses. I subclass
MACheckedMemento and create a custom memento that simply overrides the
#push: method to see if the object is new (no members will be set) and
if so, registers the object after called "super push:".
Everything is fine except for Houses, after I create a new hause the
main display always shows 2. If I leave the page and visit new I see
only one. I have looked around but I dont see how this is happening.
Maybe these links will help find what you want regarding tinlizzie:
Ken G. Brown
At 8:34 PM +0100 1/15/08, smallwiki-request(a)iam.unibe.ch apparently wrote:
>Date: Tue, 15 Jan 2008 20:34:35 +0100
>From: st?phane ducasse <ducasse(a)iam.unibe.ch>
>Subject: Re: Pier Sites
>To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>may be this what they called LogoWiki
>I was never clear on that
>On Jan 15, 2008, at 8:30 PM, st?phane ducasse wrote:
>> may be ask kim rose or scott because I cannot find it.
> > stef
> > On Jan 14, 2008, at 8:21 PM, Lukas Renggli wrote:
> >>> thinlizzy ?
> >> Where is that?
when I use #cssClass:, for example:
label: 'Info') beReadonly; cssClass: 'info'; yourself
I don't see class="readonly info" in my page source code, only
class="readonly". The problem seems to be in MAComponentRenderer>>classFor:,
which ignores aDescription attributes. Right?