Details
Description
currently many open jira's for tabset. Will link to this one and deal with them for tablet.
1) use common core rendering
2) proper rendering of bottom orientation and get working for large view
3) correct state regardless of whether contentPanes are client or not.
4) common attributes between jsf and jsp
5) disabled support
1) use common core rendering
2) proper rendering of bottom orientation and get working for large view
3) correct state regardless of whether contentPanes are client or not.
4) common attributes between jsf and jsp
5) disabled support
rev 33519 has initial checkin of tabSet where disabled is implemented in JSF, core rendering is used as much as is possible (not a lot) and common interface to ensure attributes are same.
{tabInfo.orientation}JSP has new tabSetController component which only takes child of tabPane
<mobi:tabSetControl id="tabsetOne"
orientation="$
"
{tabInfo.autoWidth}autoWidth="$
"
{tabInfo.disabled}disabled="$
"
{tabInfo.height}height="$
"
{tabInfo.autoHeight}autoHeight="$
"
{tabInfo.style}style="$
"
{tabInfo.styleClass}styleClass="$
"
{tabInfo.selectedId}selectedId="$
">
<mobi:tabPane id="pane1" title="Sailor">
<%@ include file="../includes/pane1.jsp"%>
</mobi:tabPane>
<mobi:tabPane id="pane2" title="Breaker">
<%@ include file="../includes/pane2.jsp"%>
</mobi:tabPane>
<mobi:tabPane id="pane3" title="Skate">
<%@ include file="../includes/pane3.jsp"%>
</mobi:tabPane>
</mobi:tabSetControl>
buffered approach taken with new tags. Still some work to do to enhance performance, but tests in new JSP test app show promise. (
MOBI-659test app not yet checked in).