On Tue, Mar 17, 2009 at 3:25 PM, Mariano Martinez Peck
<marianopeck@gmail.com> wrote:
Hi people: This is my first post in this list :) I am starting a personal web site for informal tourism in Argentina. The intention is not to do money but have fun with a friend of mine that studies tourism. In the website, there are lots of thing that would be very nice and fast to do it with pier (I've been playing with it and seems to be wonderful): posts, blogs, wiki pages, and so on. However, I have others "requirements" that are very specific and they are not like CMS....So, I start looking to Pier (I already know something about seaside). And I have some questions:
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?
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 ?
If you use Magma you propbably won't need any database as Magma is an Object "database"
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?
this one is trickier i think. I have overridden WASession and added a user variable for my user requirements, then in the config screen (in the Web Browser) there is a place to override the default Session with your own subclass. In Pier there is a PUUser class but I don't think it so easy to get Pier to use a subclass, so that may not suit your purposes.
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 component to a pier component then ? In fact, the main question is, can I easily have requirements that are not Pier using Pier hahah?
Any Seaside component can be added to a page by overriding
canBeRoot to return true. Then whe you use the Add command in Pier
select Component from the drop down, when it asks you which component
in the frop down you should see your component near the bottom of the
list under the Seaside category. Select it and save and BOOM! it show
up. Really cool. This is what sold me on looking at Pier in the first place. It made all my wonky looking seaside components look like professional web pages. The built in CSS helped ALOT in that regard as well.
Also, look into using Magritte to describe your objects it makes things MUCH easier down the road.
5) What's the pier-omnibrowser ? what is for ? Documentation somewhere?
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.
7) Is there some tutorial ?
That's all for now. I am very exited with Pier and hope to use it :)
Ahh I use Pier 1.1.
Cheers,
Mariano
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki