On Tue, Mar 17, 2009 at 6:14 PM, Lukas Renggli
<renggli@gmail.com> wrote:
> 1) Pier persistence. I think I can use image and magma persistence. Is this
> right? Is somewhere explain it how to do it with magma?
I am using the image persistency and I also started to do some work on
image segment persistency, but this hasn't been well tested yet. Since
the last release it is also possible to export the Pier model using
reference streams, however I do not suggest to use that as a
persistency mechanism because it is rather slow.
Excellent. I will use image persistence then. I also so your post of export and import from images!
> 2) My application has its own "business" objects like destinies, user,
> companies, trips, and so on. So, I need persistence for this model. Here,
> can I use whatever I want? I want to test squeakDBX for example, can I use
> it ? regarding of the effort of this? Or I must use the persistence strategy
> I use for Pier ?
That can be combined, you just need to make sure that the two
persistency strategies
Perfect.
> 3) Suppose there are users that can register in my site, and there is a crud
> of User. But, that's MY User. I mean, User class will have attributes of MY
> application. However, I still need a user for Pier, so that to let the user
> post, create blogs, etc....How can I do this?
Have a look at PUUser and make your user polymorphic. There should be
no problem injecting that into Pier.
Ok. I will look at PUUser and see. Perhaps I can do a inheritance. I will see...
> 4) As I said I have requirements that are not related with CMS. How can I do
> them? Create my own seaside component? extends PRComponent? How can I add my
Create your own components. It is not necessary to subclass PRComponent.
Ok, perfect.
> component to a pier component then ? In fact, the main question is, can I
> easily have requirements that are not Pier using Pier hahah?
Add to a page an embedded link like +mycomponent+, click on that link,
select "add component", select the name of your Seaside component
class and your component is within Pier.
Nice. Very simple :)
> 5) What's the pier-omnibrowser ? what is for ? Documentation somewhere?
Pier is independent of Seaside, most people (including me) mostly use
it together with Seaside. However that's not a requirement and other
views can be used instead. Pier-OmniBrowser is view for Morphic using
the OmniBrowser framework to edit and view a Pier model. It is
mentioned for example in my Master Thesis
(http://www.iam.unibe.ch/~scg/Archive/Diploma/Reng06a.pdf, Section
3.4.1) or in this short proposal
(http://www.iam.unibe.ch/~scg/Archive/Reports/Reng07c.pdf).
Ahh okok. I will also read pdf. Thanks
> 6) How can I change Pier styles (css). For example, I would like to change
> the height of the div of the header. Or the bottoms of the menu. Or put a
> background in all the site.
The "Edit Design" command lets you edit the CSS style-sheet. Also you
can use the mechanisms of Seaside, e.g. WAFileLibrary or #style
methods.
That's the main problem. I do not see "Edit design" command :( I am admin and have all the permissions, but I don't see it.
> 7) Is there some tutorial ?
www.piercms.com contains a growing collection of documentation,
tutorials, videos, blogs, examples, etc.
Cool.
> That's all for now. I am very exited with Pier and hope to use it :)
Please keep your questions rolling!
Ok, Believe me I will do it haha.
Thanks for all the help :)
Greetings,
Mariano
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch