25 Feb
2009
25 Feb
'09
8:54 p.m.
On Wed, 2009-02-25 at 19:10 +0100, Lukas Renggli wrote:
That's what I'm trying to to do. I have loads of components to embed.
I just want to try to build the skeleton with pier and embed my
components into that. Some times (in the case of editors) it is good
to have not only pier _or_ component but to interfere both a little. So
you embed a component but layout the structure of the component with
the tools pier has.
For me there are at least two views on my site. The one is sitemap
specific where everything has a location. That's the tree pier is
providing. The other view would be more object/rest centric where
you request an object/content to be displayed and don't care where it
is displayed. I have this already as the description of an object knows
the preferred location where it likes to be displayed. And the location
is configured in a way that it displays the object/content.
For me the same thing is valid for the roles. The tree and look are
provided by the web designer. I'm just providing the business logic.
My structure lies underneath where only I can see it :)
Yo, was meant as a joke. Just figuring out all the structure-children,
structure-environement stuff.
Norbert
Yes, I'll
give it a try. I need to know pier anyway if I want to use
it. It is just that I had a very hard time to resolve even simple
things in pier. I can accept the "structure is everything" thingy but
most of this is than "the structure in your brain" and that is hard to
follow. I scan again the papers I collected about magritte and pier over
the years. At the moment it is an infinite learning curve
Personally I wouldn't try to build a complex model as subclasses of
structure, unless they have a clear mapping to a tree. For example the
subpages of a blog are posts and comments, the subpages of an issue
tracker as issues and comments, and the subpages of a shop are
categories and articles. In other cases it is most certainly easier to
embed an independent Seaside application into the website.
(the structure
seems to be a graph :) ).
That's true, but most important the structure and their children form
a tree, much like the directory and files on your harddisc. The graph
like structure comes from the fact that structures can link and embed
into each other, but that's just at the level of the document.