[
https://issues.apache.org/jira/browse/FLEX-35224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15786594#comment-15786594
]
Joel Anderson commented on FLEX-35224:
--------------------------------------
The example code seems to work as expected. This design is implementing a
wrapper around DataGrid that provides the same features, plus the paging logic
and interface components.
However, to be fully compatible with DataGrid, this implementation would need
to implement wrappers for more of the features, particularly beads. The user
also does not currently have control over the position and appearance of the
buttons.
Would it be better to keep the buttons completely separate from this
implementation? For example, we could implement a PagingArrayList which would
provide the interface and events expected by DataGrid and the common beads, as
well as methods to change the page. The user would then create their own
buttons and define the layout as desired.
Does one of these solutions fit better for FlexJS? Using beads would probably
be even more desirable, but I don't have a good idea about how to implement
this at the moment.
> DataGrid doesn't support paging on large data set
> -------------------------------------------------
>
> Key: FLEX-35224
> URL: https://issues.apache.org/jira/browse/FLEX-35224
> Project: Apache Flex
> Issue Type: Improvement
> Reporter: Pan Li
> Priority: Minor
> Attachments: screenshot-1.png, src.zip
>
>
> expected:
> Gird should support paging if data collection is large
> !screenshot-1.png!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
