Hi again,
> Rafal, could you consider contributing the HeadTool into turbine
> keeping others from having to re-invent the wheel?
>
If the HeadTool we are discussing is to be implemented in TemplatePageAttributes
and thus needs to use ECS I see a little problem. In fact I took this route
myself yesterday only to find that VelocityOnlyLayout is by now the better
solution if you try to place script-elemnts into the head:
My problem: My JavaScript needs to be rendered by Velocity. In my case the
navigation is created dynamically depending on the login. but I did not get the
following code to work:
$page.setScript("javascript","text/javascript","#parse("myscript.vm")")
I kept having javascript-errors in the browser coming from unbalanced
double-quotes - naturally. My method might be useful though to put the following
element into the Head:
<SCRIPT LANGUAGE="<language>" TYPE="<type> SRC="<url>"></script>. That is an
easy change. I can post it, I myself don't need it though, because no parsing is
then possible.
Otherwise: I am
+1
on the nice templating solition for the HEAD Rafal is talking about.
regards,
Alexander
Alexander Banthien schrieb:
> > Hi Rafal and Sean, thanks for your help!
> >
>
> Rafal wrote:
>
> > Some time ago, an idea crossed my mind, that we might want to introduce
> > another layer of templating, namely Page template. It would contain
> > the common elements of all Layout templates used in conjuncion with
> > WebMacrOnlyLayout class. An application will use precisely one
> > Page template, the same way as it uses single Page class now.
> > This would bring us back to the separation between head and body parts
> > of the page we had with ECS, but with template driven customization
> > of head elements available to the developer.
> >
> 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.
>
> 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.
>
> regards, Alexander
> --
> ----------------------------------------------------------
> Alexander Banthien
> JusTec GmbH
> Haslacher Str. 126
> 79115 Freiburg
> Germany
> Tel:+49 (0) 761 401269 00
> Fax:+49 (0) 761 401269 13
> WWW: http://www.justec.de
> E-Mail: [EMAIL PROTECTED]
> ----------------------------------------------------------
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
--
----------------------------------------------------------
Alexander Banthien
JusTec GmbH
Haslacher Str. 126
79115 Freiburg
Germany
Tel:+49 (0) 761 401269 00
Fax:+49 (0) 761 401269 13
WWW: http://www.justec.de
E-Mail: [EMAIL PROTECTED]
----------------------------------------------------------
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
