Regarding helping the web designers get around the templates, i have found
in the past that providing a master HTML file with server side includes to
include the component templates that you want them to edit worked fine. It
was actually a web designer that suggested this, I think they used
Dreamweaver to edit the templates which works fine with SSI.
This way they only see it as one template when in fact they are editing all
the component templates.
On 7/4/07, David Avenante <[EMAIL PROTECTED]> wrote:
Yes I can understand but this approach is a big constraint, with big
implication for my web designer who need to play in templates and need
to have a good understanding of my templates hierarchy
For me it's an issue with lot of limitation. A simple exemple :
I want to create a component who can generate a complex layout for my
page.
I want something like :
<div t:type="myLayout">
<div t:type="contentPanel" name="north">
content a
<div>
<div t:type="contentPanel" name="south">
content b
<div>
</div>
So as you can see I can have many contentPanel (like east west center...)
And each contentPanel can content a new layout.
It's crazy for me to let play a web designer in a hierarchy of template.
I need to have a "flat" view a this type of complex component.
So I don't see the origins of this technical limitation.
Cheers,
David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
