Alexander Banthien wrote:
> 1. This might provide for neat further separation. Beware though: as far as
> I see right now, the screen-only-writers would loose their chance of writing
> into the head, which they have right now in the ECS-model. Maybe some sites
> dont like the idea of giving write access to such a central part of an
> application to a potential manifold of people.
You are wrong. Screen class is run and Screen template is rendered
before
Layout rendering starts. This gives the chance of modyfing the contents
of layout to screen developers by storing/modyfining objects in the
context.
The same would occur wiht page templates. The layout class/template
would
have the chance of modyfing the context before Page layout rendering
starts.
> 2. Why do you propose to have only one page-template? Why not have many mith
> the same lookup-scheme as for layouts. Do I understand you right that the
> aim of the page template is precisely the HEAD-part (since everything else
> is canonical?) I would in this case prefer calling them head-templates and
> potentially have many.
The scope of the Page template are head part, and opening/closing of
body
tags. Consedirenig what I wrote above, screen designers could customize
the output produced by Page template using a HeadTool class that would
contain all properties found in the inside head tag and the attirbutes
of the body tag. We use such class in our project in conjunction with
WebMacroOnlyLayout class.
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
