[ https://issues.apache.org/jira/browse/TRINIDAD-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584301#action_12584301 ]
Andrew Robinson commented on TRINIDAD-1032: ------------------------------------------- New proposal, use the panelBorderLayout instead. Add these attributes: layout (table/positioned): if positioned, use absolute positioned DIVs to render the panel. Only if layout is positioned are the following new attributes used: topHeight: the CSS height of the top facet to use if present topInnerHeight: the CSS height of the inner top facet to use if present bottomHeight: the CSS height of the bottom facet to use if present bottomInnerHeight: the CSS height of the inner bottom facet to use if present To save being verbose, other attributes: leftWidth, innerLeftWidth, startWidth, innerStartWidth, rightWidth, innerRightWidth, endWidth, innerEndWidth. Since this would be an enhancement, not a new component, it would not be a sandbox, but a core change. > New component: tr:panelStretchLayout > ------------------------------------ > > Key: TRINIDAD-1032 > URL: https://issues.apache.org/jira/browse/TRINIDAD-1032 > Project: MyFaces Trinidad > Issue Type: New Feature > Components: Components > Affects Versions: 1.0.7-core, 1.2.7-core > Reporter: Andrew Robinson > Assignee: Andrew Robinson > > Add a new component, to the trinidad-sandbox first, that is similar to the > panelBorderLayout. Unlike this component the panelStretchLayout would be > rendered using DIV instead of TABLE and would be able to stretch horizontally > and vertically. > The main reason I am proposing this is to be able to produce a component for > the new demo that can frame the browser viewport and have the demo page > content in a center-scrolling DIV. This way there can be a header, footer on > the page that fits on one page. > For those that are familiar with the Oracle panelStretchLayout, this one > would not be as robust. I do not think it would be in the scope to > automatically stretch the children and I do not think that it would be needed > to have an auto-height for the original version. > The component would have a top, bottom, left, and right facets and use the > children for the center. The facet sizes (height and width) would be > specified using attributes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.