flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Ent (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-35224) DataGrid doesn't support paging on large data set
Date Tue, 10 Jan 2017 14:13:58 GMT

    [ https://issues.apache.org/jira/browse/FLEX-35224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815061#comment-15815061

Peter Ent commented on FLEX-35224:

We should be able to specify beads either in CSS or in-line via <js:beads> property.
I've been finding that some of the beads written do not take into account the differences
in timing between CSS and in-line. In fact, you should be able to remove a bead and add a
new bead programmatically - but that's something we can aspire to be able to since it may
mean all beads need deal with a new bead in their presence. Not being able to replace the
model in-line is a bug.

Having a new component is certainly a good way to go. It is a pay-as-you-go solution. You
could also add a className to your assembly of beads (e.g., className="PagingDataGrid") and
use a .PagingDataGrid selector in CSS to provide the beads. 

But you should be able to override CSS-supplied beads in-line using <js:beads>; please
file another bug for that with the DataGrid and I can look into that. The DataGridPresentationModel
bead was created near the beginning of FlexJS so it probably needs an update.

> 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: FilesOfPagingDataGridUsingBeads.zip, PagingDataGridAsBeads.patch,
TestPagingDataUsingBeads.zip, 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

View raw message