Basic Customization > User Interface Customization > Customizing HTML Clients Using the Windchill JSP Framework > Split Pane / Two Pane > Customization Points
Customization Points
renderTwoPanes tag attributes
The renderTwoPanes tag is a custom JSP tag that you insert in the JSP.
Parameter
Default Value
Possible Values
Req?
Description
orientation
horizontal
horizontal, vertical
No
Lays out the inner panels either side by side or stacked
leftPane
Relative or absolute path to a JSP page
Yes
URI to the file to be rendered in the left/top pane
rightPane
Relative or absolute path to a JSP page
Yes
URI to the file to be rendered in the right/bottom pane
headerPane
Relative or absolute path to a JSP
No
JSP file to be rendered in the top pane. This is only used when orientation is set to “horizontal”.
onClick
Name of a valid JavaScript function
No
Function called for every click event fired from either pane (left/right or top/bottom). The click handle will most likely make an AJAX call to get the data to display. Typically, when something is clicked in one pane you’ll want to have something happen in the other pane.
leftPaneSize
25
0-100 (Percentage)
No
Specifies the width/height (depending on the orientation value) of the panel.
rightPaneSize
75
0-100 (Percentage)
No
Specifies the width/height (depending on the orientation value) of the panel.
headerPaneHeight
0
Absolute Pixel size
No
Specifies the height of the panel. Specified as an absolute pixel size (i.e. 150)
Limitations
When the left or right pane is resized, some of the components within that pane may not get resized properly.
The underlying framework manages the layout of the components it knows about in its component hierarchy, so that (among other things) it can recalculate the layout on resize events. For example, when a resize event happens, it would recalculate the layout of its children, and those children’s children, and so on. Because the two pane component simply renders its contents to the DIV corresponding to the pane, and does not actually add its contents as a child of the pane’s panel, nesting components (especially those components that are containers to house other components) within a pane may not behave as expected.
Was this helpful?