Hi,
In Magritte a MAContainer has a collection of MAElementDescription objects
called children. Often I would like to access a child using it's name.
Currently a MADescription doesn't have a name property. Most of the times it
does have a label and an accessor so I can find a child like this:
| accessor |
accessor := #eventStatus asAccessor.
MBBooking description detect: [ :each | each accessor = accessor ]
or
MBBooking description detect: [ :each | each label = 'Event status' ]
I don't like these options for identifying a child description because they
depend on properties that are used for other things. I am thinking about
adding an some kind of 'name' property to the description hierarchy. I am
curious how others have handled this issue.
Jan.
Context:
- os: debian
- vm: cog
- image: the image from the pier site, in which I updated to the
latest version of the pier packages
~/coglinux/bin/squeak x.image
starts the image with no error and port 8087 is open
~/coglinux/bin/squeak -nodisplay -nosound x.image
just blocks and the port 8087 is not open.
do you have any idea what could be the reason? I tried with all the
possible parameter combinations: (-headless, -vm-display-none)
Thanks,
M.
--
Mircea Lungu
Researcher
Software Composition Group
University of Bern
http://lungu.org/mircea
I've loaded Seaside 3.0 and Pier 2 with Metacello configurations. I tried
both the "latest" (= 3.0.3.1) and the "last" (= 3.0.6) for Seaside; I also
updated all Pier packages from Lukas's repo by hand. The problem I encounter
is with Export/Import widget: clicks on "Export" and "Import" buttons are
just ignored (at least, callbacks are not triggered in image). Am I doing
something wrong?
I remember I had (and reported) a similar issue several months ago, didn't
get any response managed to find some solutions or workaround. Now I can't.
Any help please?
--
Dennis Schetinin
Hi Erwann,
All the documentation is linked from here:
http://piercms.com/
For the automatic builds I am using the scripts here:
https://github.com/renggli/builder/tree/master/scripts
Namely seaside3.st, seaside3-kom.st, magritte2.st, pier2.st. Easier is probably to use the Metacello configuration.
The Pier application is automatically registered in the initialization code of the Pier-Seaside and/or Pier-Setup packages.
Please ask further questions in the mailing list.
Lukas
On Sep 2, 2011, at 12:34 , Erwann Wernli wrote:
> Hi Lukas,
>
> Is there any resource somewhere indicating how to create a pier web site, after having downloaded the packages?
>
> The one-click image is nice, but I would like to create pier installation from scratch, but I don't know what needs to be registered as a WAApplication in seaside, how to create the kernel, etc.
>
> Can you provide me any hint?
>
> Cheers,
> Erwann
--
Lukas Renggli
www.lukas-renggli.ch
