At 12:40 20/02/2001 +0100, you wrote:
>At 01:23 02/20/01, Michael Sallman wrote:
>>I made some changes to the Velocity templates to restore
>>some of the JR/TR.props references that had been hard-coded in.
>>(header logo, welcome message, login message, footer logo, stylesheet).
>>
>>I also moved the header logo from default.vm to top.vm
>>as it seems the more appropriate place for it.
>>
>>I'm just starting to investigate Velocity, so I'm not sure if I'm
>>even implementing it correctly. But the diffs do seem to work.
>>Any comments/critiques would be appreciated.
>
>I don't think reviving these settings in the TR.p is a good idea. This was
>needed with Ecs to make those things configurable, but with templates it
>doesn't make sense to me:
>The idea is that for a portal installation the templates are customized. A
>page designer can develop the look and feel just by editing the templates
>- no touching of source code, no property files. I find it much more
>natural to specify the stylesheet name in the head section of a template
>(where a page designer would expect it) instead of setting a value in a
>property file that is then included in the template through a directive.
>Things are different for dynamic parts: If you decide to use different
>stylesheets depending on the locale, then you will have to use dynamic
>elements in the template.
+1
I think that for the next alpha, the legacy ECS screens and related
properties in JR.p will be
removed since we'll already have support for 2 templating systems, and no
one in his
right mind should build markup using code...
--
Raphaël Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Services Manager / Paris
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/jetspeed@list.working-dogs.com/>
List Help?: [EMAIL PROTECTED]
