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
Hi,
I've been working on the ConfigurationOfxxx to load the Wysiwyg editor and
think I've finally made it.
Starting with a clean Pharo1.3 image, I found I first needed to load a
recent version of Seaside:
Gofer new
squeaksource: 'Seaside30';
package: 'ConfigurationOfSeaside30';
load.
ConfigurationOfSeaside30 loadLatestVersion.
I've added the editor configuration to ConfigurationOfPierAddOns2, so the
next step is to load the configuration:
Gofer new
renggli: 'pier2addons';
package: 'ConfigurationOfPierAddOns2';
load.
If you want to test the editor in a minimal configuration, then execute:
((Smalltalk at: #ConfigurationOfPierAddOns2) project version: '2.0.9') load:
#('Pier-FileUpload-Wysiwyg').
Or if you want the editor loaded into a more complete "standard" pier
installation execute:
((Smalltalk at: #ConfigurationOfPierAddOns2) project version: '2.0.9') load:
#('Pier-Setup' 'Pier-FileUpload-Wysiwyg').
The Wysiwyg editor insert image/file upload, functionality requires a filter
and configuration to be installed. The magic to do this is
in ConfigurationOfPierAddOns2>>#initializeWysiwygEditorFileUpload:
ConfigurationOfPierAddOns2>>#initializeWysiwygEditorFileUpload
| pierApp |
pierApp := WADispatcher default handlers at: 'pier' ifAbsent: [
| distribution |
distribution := Smalltalk at: #PRDistribution ifAbsent: [ nil ].
distribution isNil
ifTrue: [
(PRPierFrame registerAsApplication: 'pier' kernel: (PRKernel named:
'defaultKernel')) ]
ifFalse: [
PRPierFrame registerAsApplication: 'pier' kernel: PRDistribution new kernel
] ].
pierApp filters detect: [ :aFilter | aFilter class name =
#NAFileUploadRequestHandler ] ifNone: [ pierApp addFilterFirst:
NAFileUploadRequestHandler new ].
pierApp configuration addParent: NAFileUploadConfigurator instance
The installation will install the required filter and configuration provided
your Pier application is installed at '/pier'
Editing a page should now display the Wysiwyg editor. The editor's links
dialog should include a Pier site map, allowing you to easily select a link
within the site. The insert image, should include a "choose file" button
which will upload a file and by default store it in folder based on the
location of the page within the pier site-map, by default within a folder -
'uploadedFiles' - in the image folder. The uploaded images folder can be
configured within /config in the "File Upload" section.
Hope this all makes sense
Nick
Hi guys. I am testing a import/export of Pier kernels and I would like to
test with a real kernel (not the one included by default in Pier). I want to
export such kernel and import it in another image.
I have 2 pier images handly but both are quite old (pharo 1.0 and non-cog).
I would like a new one based on Cog and Pier 2.0.
Of course, the Pier image should be open-source or at least you should not
care that I test it.
so...someone has a pier image to lend me?
Thanks a lot in advance.
--
Mariano
http://marianopeck.wordpress.com
Hi,
I am having a little problem. I have upgraded humane-assessment.com to the latest Pier/Seaside, but now it crashes constantly.
There is no log, it just crashes.
I suspect it has something to do with a memory leak. Any idea of what can cause this issue? Or how I could investigate it?
Cheers,
Doru
--
www.tudorgirba.com
"If you interrupt the barber while he is cutting your hair,
you will end up with a messy haircut."
