ציטוט Ron Piterman:
ציטוט Vinicius Carvalho:
This is just like the page title question.
You use one border, but you need for each page another title, so you use
pass parameter to the border, indicating the title.
Now, if some pages use just the same layout, but vary slightly, you can
include these parts as optional, dynamic parts of your border.
<tr>
<td> some menu </td>
<span jwcid="@Conditional" condition="ognl:displaySubmenu">
<td> submenu </td>
</span>
<td>@RenderBody</td>
</tr>
Now I go a bit further with implementation, but that acctualy was
already everything.
public boolean getDisplayBorder() {
return getPage() instaceof ISubmenuPage;
}
public List<SubmenuItems> getSubmenuItems() {
return ((ISubmenuPage)getPage()).getSubmenuItems();
}
Just an idee...
Answering myself...
I dislike that. I think it would be better to pass an optional list
parameter to the border, containing the submenu items, than implementing
it with an interface on the page class.
Cheers,
Ron
Thanks to Ron and Jamie I got things started here with composite
screens. Well But I found it most ackward to have a component called
Border with my page layout. What if I have diferent layouts, should I
create a new component for each one? What about nesting? Imagine a
page that has a menu on top and content underneath. Ok here's my
component:
<tr>
<td> some menu</<td>
<td>@RenderBody</td>
<tr>
Ok, now what happens is let's say one of the itens of the menu has
another composite page with a menu on the left? How to compose them?
thanks all
Vinicius
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
