Hi!<br>I want to use Pier as a wiki at work, so I&#39;m evaluating if it meets my needs.<br><br>(side note: It&#39;s very complicated to get information about Pier from the main Squeak site, the Pier wiki or the Seaside site. I don&#39;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)
<br><br>After running the image provided by Keith, I&#39;ve tried to use Magma and I got the same error about &quot;objects&quot; file mentioned early in the list :(. So before digging more into the problem, I have a couple of questions:
<br>- What is the recommended mechanism for persistence: plain files, Magma, image?<br>- 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?)
<br>- How can I make Pier components? (I&#39;m new to Seaside too)<br>- It&#39;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)
<br>- I want to change the stylesheet how I can do that?<br>- 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?
<br>- It&#39;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<br><br>That are a lot of questions for a single mail!<br>
So many thanks in advance!<br>Diego.-<br><br><br>