[Seaside] Re: Dynamically placing components on a page

[Jason Johnson]

Petr wrote:
> I thought Pier might include exactly what I want, though using the 
> whole Pier codebase is overkill for my needs, so I will just have a 
> look how exactly I should implement this.
>
> Petr

I wouldn't be so fast to assume this.  You don't want to get in a 
situation where after working on it for 5 years you finally get to the 
point where you have implemented everything Pier has today.  As far as I 
understand, Pier is a CMS made to be used at customer sites (i.e. not 
just software made to show off seaside features), and therefor probably 
has the things you will end up building.

What I personally do to create my site(s) is just use Pier and create 
components that do the specific behavior I want.  Most things I end up 
doing fit really well with how Pier already works.  E.g. on the band 
site, there is a section that tells about all the band members.  The 
band is 5 people, and pretty static, but I still found it faster to just 
make a really simple Pier component that has the fields and is set up so 
that a new member can be added by saying "add->component->band member" 
and then use the Pier settings button to fill in the fields.  A kind of 
DSL if you will. :)