Currently, the markup generated for the tabbedPanel component looks like
this:
[code]
<wicket:panel>
<div class="tab-row">
<ul>
<li wicket:id="tabs">
# [[tab title]]
</li>
</ul>
</div>
[panel]
</wicket:panel>
[/code]
I think that it would be more useful to add a container to the existing
tabs, so the resulted markup would look like this:
[code]
<wicket:panel>
<div wicket:id="tabsContainer" class="tab-row">
<ul>
<li wicket:id="tabs">
# [[tab title]]
</li>
</ul>
</div>
[panel]
</wicket:panel>
[/code]
This way you can append a new css class to this container (using
AttributeAppender behavior) and can control the specific visual appearance
of the tabbed panel... It is not enough to have only "tab-row" class,
because if you have nested tabbed panels (which have different styling) it
is hard to style them as you want... And finally, you give the developer a
freedom to do what he wants with this container...
What do you think?
Thank you!
--
View this message in context:
http://www.nabble.com/-Request-for-enhancement--TabbedPanel-tf3764064.html#a10640047
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
