15 Mar
2007
15 Mar
'07
4:11 p.m.
Hi!
I want to use Pier as a wiki at work, so I'm evaluating if it meets my
needs.
(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)
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?
- 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?)
- How can I make Pier components? (I'm new to Seaside too)
- It's possible to use LDAP for Pier authentication? 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)
- I want to change the stylesheet how I can do that?
- 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?
- It's possible so show or hide a component according to the user role? I
want to show the tree component only if the user is the administrator of the
wiki
That are a lot of questions for a single mail!
So many thanks in advance!
Diego.-
15 Mar
15 Mar
6:24 p.m.
2007/3/15, Diego Fernandez <diegof79(a)gmail.com>om>:
Hi!
I want to use Pier as a wiki at work, so I'm evaluating if it meets my
needs.
(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)
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.
- 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?)
- 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
- make subclasses of PRStructure that are described with Margitte and
implement the related commands
have a look at:
http://mc.lukas-renggli.ch/pieraddons.html
or the blog plugin to get some ideas
- 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.
- I want to change the stylesheet how I can do that?
remove PRPierLibrary from the pier application (via the Seaside config
application) and add your own
- 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?
To always display the environment remove the PRHider decoration (the
simplest way is with the object explorer).
Then you can set the view permission on the environment.
- It's possible so show or hide a component
according to the user role? I
want to show the tree component only if the user is the administrator of the
wiki
Change the view permission of the component.
Cheers
Philippe
That are a lot of questions for a single mail!
So many thanks in advance!
Diego.-
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
9:42 p.m.
Hi Diego,
nice to hear from you.
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.
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.
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.
> (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. > - 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 - 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. > - 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
17 Mar
17 Mar
7:33 p.m.
Many thanks to everyone for the answers :)
I need to setup a wiki fast.. so I'm going to start with the old ComSwiki
until I learn more about Seaside and Pier... so you will hear more questions
from me about Pier :)
(BTW Lukas your work on Pier is amassing, thanks!)
On 3/15/07, Lukas Renggli <renggli(a)iam.unibe.ch> wrote:
Hi Diego,
nice to hear from you.
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.
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.
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.
> (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. > - 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 - 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. > - 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
6512
days inactive
6514
days old
3 comments
3 participants
participants (3)
-
Diego Fernandez -
Lukas Renggli -
Philippe Marschall