On Tuesday, April 16, 2002, at 10:42 AM, David Wynter wrote:
> You are missing the point. I have one layout template,
> .../app/layouts/Admin/Default.vm, for 12 screen classes. This enforces
> consistency of look and feel for a given role (Admin) using the system.
> Having $page.setTitle(..) was very powerful in this context. I see
> having to
> create 12 identical layouts with different names and one difference,
> that is
> title, as being poor architecture.
Now I get it. I think this use case was part of the
ECS debate you mentioned. As you've discovered, you
can only do that with ECS in the picture. I know
you have returned to ECS, but for the sake of the
discussion I want to brainstorm some alternatives.
The first one that leaps to mind is to create a pull
tool for the common elements in your layout, instead
of using the layout. So your screen templates could
use something like this:
$header.renderWithTitle("unique title for this page")
Of course, this doesn't cleanly separate the layout
from the screen:
<table>
<tr><td colspan="2">$header.renderFoo()</td><tr>
<tr><td>$leftBar.renderFoo()<td>
<td>
<!-- your screen goes here -->
</td>
</tr>
</table>
In Turbine 3, I understand the the pipeline is thought
to enable something of this nature, but I haven't even
looked at it, so I can't say how that will work.
-Eric
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
