[
https://issues.apache.org/jira/browse/PIVOT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777455#action_12777455
]
Noel Grandin commented on PIVOT-276:
------------------------------------
I think part of my confusion is the naming - what you're describing here I
would want to call a BoxView, since that is the container with the closest
semantics.
A GridView is a grid - it has rows and columns, doesn't have an orientation,
you have to specify every single cell explicitly.
If what you want is parity with the containers, then maybe we should create:
(1) GridView - acts like the new GridPane.
(2) BoxView - acts like BoxPane, the closest thing to what you're describing
here.
> Add a GridView component
> ------------------------
>
> Key: PIVOT-276
> URL: https://issues.apache.org/jira/browse/PIVOT-276
> Project: Pivot
> Issue Type: New Feature
> Components: wtk
> Reporter: Greg Brown
> Fix For: 1.5
>
>
> GridView would be a data-driven component like ListView or TableView, but
> would arrange items in a 2-dimensional grid instead of in rows (similar to
> "icon view" in Windows Explorer or Mac OS X Finder). It would provide an
> orientation property that would dictate which way items would be laid out: a
> horizontal grid view would arrange items left to right, and a vertical grid
> view would arrange them top to bottom.
> GridView would assume a fixed renderer size, and would report preferred size
> based on orientation: e.g. the preferred size of a horizontal grid view would
> be (n * renderer width) x (renderer height). Constraining the preferred width
> of a horizontal grid view would cause the items to wrap at the end of each
> row; constraining the preferred height of a grid view would cause items to
> wrap at the end of each column.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
