[Zope3-dev] Re:

[Tonico Strasser]

Jim Fulton wrote:
> Tonico Strasser wrote:
> 
>> Jim Fulton wrote:
>>
>>> For me, the scope is broader than that.  Uptimately, the goal is to
>>> produce pages that end users see.  I see composition at various levels.
>>> For example, I'm *finally* understanding how poorly our page-macro
>>> system works.  When a developer defines a page as a view of some
>>> object, they shouldn't have to say how the page is wrapped with the
>>> site look and feel. That should be the concern of someone else.
>>> There should be a mechanism for "composing" these pages with the site
>>> look at feel.
>>
>>
>>
>> Thinking in page templates I would try to solve it this way:
> 
> 
> I assume by "it" you mean the problem of making individual pages
> responsible for providing the layout.

Yes, the individual pages don't need to know about the look and feel.

[...]
>>
>> This way, I can switch to a different layout by using a different 
>> layout macro (and stylesheet).
>>
>> This is a silly example, but I hope you get the idea.
> 
> 
> Nope, not at all.  Regardless of how you implement the layout,
> the individual pages have to invoke the main template some how.  I think
> there are a number of problems with that.  I don't think the solution lies
> in more macros.

Individual pages don't have to invoke the main template directly, the 
can call a script that returns a macro with slot definitions. An 
indivudal page is only interested in filling slots.

What are the problems with that?

What are the alternatives?

   * An additional abstraction layer for better separation of
     presentation-structure and presentation-layout?
   * A new pure UI language?
   * XSLT?

Tonico