Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 15AEE200C03 for ; Fri, 6 Jan 2017 17:00:00 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 11960160B1F; Fri, 6 Jan 2017 16:00:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 57E6E160B37 for ; Fri, 6 Jan 2017 16:59:59 +0100 (CET) Received: (qmail 11895 invoked by uid 500); 6 Jan 2017 15:59:58 -0000 Mailing-List: contact issues-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flex.apache.org Delivered-To: mailing list issues@flex.apache.org Received: (qmail 11871 invoked by uid 99); 6 Jan 2017 15:59:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jan 2017 15:59:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 6EDF92C1F54 for ; Fri, 6 Jan 2017 15:59:58 +0000 (UTC) Date: Fri, 6 Jan 2017 15:59:58 +0000 (UTC) From: "Peter Ent (JIRA)" To: issues@flex.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FLEX-35224) DataGrid doesn't support paging on large data set MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 06 Jan 2017 16:00:00 -0000 [ https://issues.apache.org/jira/browse/FLEX-35224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15804857#comment-15804857 ] Peter Ent commented on FLEX-35224: ---------------------------------- The paging aspect just means you want to present multiple items at a time, not a single item, but the process is the same. In FlexJS, there's no "demand" except when the data provider signals it has changed. Your paging button would cause the data provider to refresh itself in some way and then dispatch an event. The component presenting the item renderers (i.e., "virtual" DataGroup) would need to figure out what to do to present this new information. Probably something like make a pass through the itemRenderers it already has (since you aren't scrolling, it is effectively a refresh of the itemRenderers) and giving them the new data. The itemRenderers would then have to respond by redrawing themselves using the new data. I think you need a new DataGridView that creates the controls you need and you can either make a new DataGridLayout or just make your DataGridView do the work. The "DataGrid" in FlexJS is the sum of its beads, nothing more. If you have your own view, model, data group, item renderer factory, etc. then any changes to the DataGrid beads in FlexJS will have no effect on your work. What you probably do not need to do is change the logic of the Container and its beads since you can just use those to hold your own grid pieces. Yes, it is a completely new view, but that's how pay-as-you-go works. Often you have to just replace something completely. > 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 (v6.3.4#6332)