> I've tryed to install pier from your squeakmap
> repository. First I take a fresh Seaside-image from
> Seaside-website and after this a load the packages
> Margrit and Pier with monticello. After restart the image
> I tryed to start Seaside-pier in the webbrowswer. There
> an error comes up with a message not understood of
> an class from Seaside. So I think it is an version-problem
> with seaside. What package versiion (mcz) you use for
> the actual version of pier?
just load the Pier package from SqueakMap into a fresh 3.8 image. It
will automatically load all required prerequisites such as Kom,
Seaside, Magritte, etc.
I don't really see how the different MAaccesor work... as I'm always
For instance, what could be the use of MADictionnaryAccesor ?
MAVariableAccesor ? (used in MADescription class)
Are they always linked to real instance variables (created) ?
> If you aren't already, try using "WAEncodedKom startOn: 9090" instead
> of "WAKom startOn: 9090". This will do the proper conversions to and
> from UTF-8 from WideString.
I also have some problem with french characters... (é à è ...) using
- with WAKom
I have encoding problems for strings written in the squeak browser (ex:
a label definition for a description like 'Nationalité')
Inputs done from forms are ok.
- with WAKomEncoded, it's the opposite situation. Description labels are
correctly rendered whereas forms inputs are corrupted...
Do you know how to solve this problem ? (I probably missed something to
What about some docu of css using in pier. I've browsed some code of pier searching for binding css from local file-system. There was nothing that can change the width of edit-field of some contents. So I was playing around with the css itself and saw changing the css works for my wishes.
I think for newbies of pier like me the docu of css used in pier is the best thing getting the own look and feel with some usefull content.
Date: Wed, 22 Feb 2006 21:01:19
To:"SmallWiki(a)schmees.com, Magritte(a)schmees.com, smallwiki(a)iam.unibe.ch"@mx04.bwc.eu.BlackBerry.COM
Subject: Re: Fast Production Pier
> What I would like to find (and maybe it's out there, but I can't
> find it) is how to create a totally new "website". And, make it
> only readable by the general public (e.g when starting Pier, it
> just starts up and exposes everything.) Note that I'm not very
> familiar with web technology.
If you load 'Pier-Security' from Squeak map you can easily make your
web-site read only for public. With the 'Unix Permission' package you
need to remove all the permission except the one for the view from
the root directory of 'others' and assign the admin as 'owner' and
> The information to create a totally new website seems to be lacking
> in the documentation - or I just haven't found it or completely by-
> passed it. Or I'm just a confused (which is totally possible)
Yes, there is a lack of documentation :-/
> What is a typical way of creating a website from existing seaside
> or pier classes? What the heck do I subclass? Or do I subclass?
> There are a lot of Pier classes, and I'm a bit confused. Maybe the
> best thing for me to do is create a Seaside app and not subclass Pier?
What I did for my website was just to change the style sheet, to edit
the page 'environment' and to write some content. For most users
there is probably no need to write any code.
I will try and see if we can come up with something ready for Seaside-
Hosting, so that people can only press a button and then they get a
ready made and nicely hosted Pier system running. For now this is
just an idea, but if I find some time I will try to prepare
SmallWiki, Magritte, Pier and Related Tools ...
What is the fastest way to get Pier up and running for production?
(how's that for an open-ended question!)
I want just a website, not a CMS
What I have so far:
- Running on Linux, FC4
- The default Seaside/Pier running at 9090.
- installed Pier Unix Security from SqueakMap
Running at port:80 is a requirement but just a minimal website: mostly
text with some graphics (like a header) and with links is all I need
just for those that haven't noticed yet: there is now a free Seaside
hosting service available. Of course this is a good place to run your
own Pier instance ;-)
> From: Adrian Lienhard <adi(a)netstyle.ch>
> Date: 22 février 2006 09:05:27 HNEC
> To: "The Squeak Enterprise Aubergines Server - general discussion."
> <seaside(a)lists.squeakfoundation.org>, The general-purpose Squeak
> developers list <squeak-dev(a)lists.squeakfoundation.org>
> Subject: [ANN] Free Seaside-Hosting online
> Reply-To: The general-purpose Squeak developers list <squeak-
> Hi all,
> netstyle.ch and ESUG are pleased to finally announce the new
> Seaside hosting service located at
> Seaside-Hosting is a free hosting service for non-commercial
> Seaside applications. This service provides a simple to use web
> interface with FTP access to set up and run your Seaside
> applications. It allows you to put your own application online
> within minutes. The service is a Seaside application and is itself
> running on Seaside-Hosting too.
> Seaside-Hosting currently offers 128 MB of file-space for saving
> the Squeak web-application image and static files, e.g., pictures
> or style sheets which you want to use as part of your application.
> For general discussion we propose to use the Seaside mailing list.
> For specific questions or problems please contact us directly at
> Adrian Lienhard
> netstyle.ch GmbH, Terrassenweg 18, CH-3012 Bern
> T +41 31 356 42 56, F +41 31 356 42 57
> http://www.netstyle.ch mailto:firstname.lastname@example.org
I want to make a Smallwiki pages where I want to use links to other
elements (anchors) on the same page. I assumed the following would work:
-<a href="#target">Point to item on same page</a>
<a name="target">The target</a>.
But it does not, since the basepath does not point to the right
location, or something. To see my problem in real life, have a look
at the following page: http://restructuring.ulb.ac.be/achievements/
Any ideas on how to go about this ?
For a couple of years now, I've been using SmallWiki to power the
Monticello/OmniBrowser web site. Now that Pier seems to be stable,
I'd like to upgrade. Does anybody have advice for how to move the
wiki contents from SmallWiki to Pier?
I've just posted on squeakmap a stable release of smallwiki for Squeak
3.6 only, which is basically the same one used for
www.squeak.org. This release is a "one-click" install - "ready for
contribution" release both for users and developers, which means that
you don't need to bother about dependencies. The unstable one - called
Smallwiki - is for Squeak 3.7 and 3.8. This unstable one should
probably be renamed Smallwiki-unstable (sorry, don't have the
login/pass to do it - Lukas ?).
Users : just install this version and follows the instruction in the
Developers : install this version, you will see on monticello all
packages from which smallwiki depends (NamedServices, KomHttp and so
one). The repository is in global read/write access, so you don't need
to ask for permission to contribute to smallwiki. So please consider
that this is a great responsability : you should read carefully the
"how to contribute" proposal (www.squeaksource.com/smallwiki1). Please
post to the smallwiki list for any comments. The current
smallwiki-stable release is based on the Chris port version 0.9.23-6
whereas the unstable one is based on 0.9.53.
Developers - bis :
How to keep the "one-click" installation both for developers and users
? Answer: When releasing a new SW version, we should for the moment
update the modified package plus its dependent packages - maybe there
is a way to automate (TODO) that through MCConfiguration but I don't
know how to do that. For instance, a modification of SmallWiki-Kernel
implies a dependency update of SmallWiki-Parser + SmallWiki-Stable.