On 3/15/07, Lukas Renggli <renggli@iam.unibe.ch> wrote:

Hi Diego,

nice to hear from you.

>> (side note: It's very complicated to get information about Pier
>> from the
>> main Squeak site, the Pier wiki or the Seaside site. I don't known
>> how the
>> Ruby guys get the resources to make their web sites... but we -I
>> mean the
>> squeak community- need to learn a lot from them in this area)

The source where all the documentation is linked from here:

http://www.lukas-renggli.ch/smalltalk/pier

>> After running the image provided by Keith, I've tried to use Magma
>> and I got
>> the same error about "objects" file mentioned early in the list :
>> (. So
>> before digging more into the problem, I have a couple of questions:
>> - What is the recommended mechanism for persistence: plain files,
>> Magma,
>> image?
>
> I would say this depends on your requirements.

I just save the image. Works fine for me. Image segments created in a
forked copy of the image would be a nice and quick solution as well,
I just didn't had the time to implement that yet.

>> - If I want to change the persistence method, how hard is to do the
>> migration? (I think that I should execute a script that loads all
>> the wiki
>> in the image using the source persistence method, then write all
>> those
>> objects using the target persistence method... there is an easy
>> way to do
>> that?)

I just heard from a guy that never really touched Squeak before (he
is an experiences Smalltalker though) that he easily migrated the
whole object graph of a Pier Site from one image to another one using
SIXX.

>> - How can I make Pier components? (I'm new to Seaside too)
>
> There are two options:
> - any kind of Seaside component (subclass of WAComponent or WATask)
> will do

Yes. Any component that could be its own application (e.g. #canBeRoot
returns true) can be added and used within Pier. If you want to have
a bit more of convenience have a look at PRWidget and subclasses.
These are basically all the components used to get the default look
and feel.

> - make subclasses of PRStructure that are described with Margitte and
> implement the related commands

That's something else. PRStructure and its subclasses form the pages
of the Pier CMS. It can declare though what view to use (yet another
Seaside component, a subclass of PRView in fact).

>> - It's possible to use LDAP for Pier authentication?
>
> It's not implemented.
>
>> If not, how hard is to
>> use another authentication method? (I have experience developing LDAP
>> authentication libraries for gemstone... so I can help in this area)
>
> Once you have a Squeak LDAP client running, it should be fairly easy.

Should be easy to do though. You could take one of the existing
security frameworks and create the users/groups dynamically from an
LDAP query.

>> - I want to change the view component, so certain options like
>> editing or
>> configuring the environment are invisible if the user is not
>> logged in...
>> any clue on how to start?

You need to load a security plugin.

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki