Since 3.0
Panel is a generic grouping component that supports toggling, closing and an options menu.
See the ICEfaces Showcase Live Demo of this component, complete with source code.
<ace:panel header="ICEfaces Header"
closable="true"
toggleable="true"
collapsed="#{panelBean.collapsed}">
<f:facet name="options">
<ace:menu>
......
</ace:menu>
</f:facet>
<p>......</p>
<p>......</p>
</ace:panel>
TagLib Documentation
This section covers attributes involved in the typical use-cases for this component.
closable specifies whether the panel has a button to hide the panel by using the jQuery fadeOut() function.
toggleable specifies whether the panel has a button to collapse/expand the contents of the panel by using the jQuery slideToggle() function.
collapsed specifies whether the panel is collapsed.
footer specifies the footer text of the panel.
header specifies the header text of the panel.
None.
| toggle | Fired when the toggle button is activated to expand or collapse the panel (default event). |
| close | Fired when the close button is activated to remove the panel from view. |
The client side component object is exposed through the global variable name specified in the widgetVar attribute.
The "widgetVar" attribute on the ACE components has been removed in ICEfaces 4 and in its place a new "ice.ace.instance()" client JavaScript object lookup API has been introduced. The reason for this change is to enable lazy-initialization of the ACE component JavaScript objects to improve runtime performance and reduce browser memory use.
var widget = ice.ace.instance('frm:componentId);
The ice.ace.instance function requires the full client id of the component to be specified, such as "j_idt77:componentId" instead of just "componentId". To reduce the complexity of working with complete IDs with this function it may be preferable in some cases to use
prependId="false"in the enclosing form (e.g. <h:form prependId="false">).
This component doesn't have a client-side API made specifically to be used by application developers. However, the component's internal methods and variables can be accessed in this way, including the underlying jQuery object and objects from underlying Javascript libraries (if applicable), and can be used for whatever purpose a developer might have in mind.
The following ARIA roles are supported: menu (for the menu button).
The following markup represents the basic HTML structure of the component and the CSS classes it uses.
<!-- Root container -->
<div class="ui-panel ui-widget ui-widget-content ui-corner-all [user defined classes]" style="[user defined styles]">
<div class="ui-panel-titlebar ui-widget-header ui-corner-all">
<span class="ui-panel-title">Panel Header</span>
<span class="ui-panel-titlebar-icons">
<!-- Close button -->
<a class="ui-panel-titlebar-icon ui-corner-all ui-state-default">
<span class="ui-icon ui-icon-closethick"></span>
</a>
<!-- Toggle button -->
<a class="ui-panel-titlebar-icon ui-corner-all ui-state-default">
<span class="ui-icon ui-icon-minusthick"></span>
</a>
<!-- Menu button -->
<a class="ui-panel-titlebar-icon ui-corner-all ui-state-default">
<span class="ui-icon ui-icon-gear"></span>
</a>
</span>
</div>
<div class="ui-panel-content ui-widget-content">
<!-- Panel body -->
</div>
<!-- Menu -->
<span>
<div class="ui-widget ui-widget-content wijmo-wijmenu ui-corner-all ui-helper-clearfix">
<div class="scrollcontainer checkablesupport">
<ul class="wijmo-wijmenu-list ui-helper-reset">
<!-- Submenu -->
<li class="ui-widget-header ui-corner-all"><h3>Submenu label</h3></li>
<!-- Menu item -->
<li class="ui-widget wijmo-wijmenu-item ui-state-default ui-corner-all">
<a class="wijmo-wijmenu-link ui-corner-all">
<span class="wijmo-wijmenu-text">
<span class="ui-icon wijmo-wijmenu-icon-left"></span>
<span class="wijmo-wijmenu-text">Menu item label</span>
</span>
</a>
</li>
</ul>
</div>
</div>
</span>
<span class="ui-helper-hidden"></span>
</div>
None.