You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pivot.apache.org by "Greg Brown (JIRA)" <ji...@apache.org> on 2009/04/08 14:29:13 UTC
[jira] Created: (PIVOT-63) Rollup should differentiate between
user-added and skin-added components
Rollup should differentiate between user-added and skin-added components
------------------------------------------------------------------------
Key: PIVOT-63
URL: https://issues.apache.org/jira/browse/PIVOT-63
Project: Pivot
Issue Type: Improvement
Components: wtk
Affects Versions: 1.1
Reporter: Greg Brown
Assignee: Todd Volkert
Priority: Minor
Rollup should differentiate between user-added and skin-added components, like TabPane, etc. Ideally, this might be accomplished by defining "heading" and "content" components, similar to how ScrollPane defines "view", "rowHeader", and "columnHeader". Strictly speaking, we don't need to support an arbitrary number of child components in a Rollup, since this could be handled by setting the content component to a container.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (PIVOT-63) Rollup should differentiate between
user-added and skin-added components
Posted by "Todd Volkert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIVOT-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Volkert resolved PIVOT-63.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.2
> Rollup should differentiate between user-added and skin-added components
> ------------------------------------------------------------------------
>
> Key: PIVOT-63
> URL: https://issues.apache.org/jira/browse/PIVOT-63
> Project: Pivot
> Issue Type: Improvement
> Components: wtk
> Affects Versions: 1.1
> Reporter: Greg Brown
> Assignee: Todd Volkert
> Priority: Minor
> Fix For: 1.2
>
>
> Rollup should differentiate between user-added and skin-added components, like TabPane, etc. Ideally, this might be accomplished by defining "heading" and "content" components, similar to how ScrollPane defines "view", "rowHeader", and "columnHeader". Strictly speaking, we don't need to support an arbitrary number of child components in a Rollup, since this could be handled by setting the content component to a container.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.