Return-Path: X-Original-To: apmail-flex-dev-archive@www.apache.org Delivered-To: apmail-flex-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 62DB211251 for ; Sun, 6 Apr 2014 17:29:10 +0000 (UTC) Received: (qmail 69906 invoked by uid 500); 6 Apr 2014 17:29:09 -0000 Delivered-To: apmail-flex-dev-archive@flex.apache.org Received: (qmail 69825 invoked by uid 500); 6 Apr 2014 17:29:09 -0000 Mailing-List: contact dev-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 dev@flex.apache.org Received: (qmail 69817 invoked by uid 99); 6 Apr 2014 17:29:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Apr 2014 17:29:09 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: unknown (athena.apache.org: error in processing during lookup of aharui@adobe.com) Received: from [207.46.163.204] (HELO na01-bl2-obe.outbound.protection.outlook.com) (207.46.163.204) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Apr 2014 17:29:02 +0000 Received: from BL2PR02MB500.namprd02.prod.outlook.com (10.141.95.147) by BL2PR02MB497.namprd02.prod.outlook.com (10.141.95.140) with Microsoft SMTP Server (TLS) id 15.0.913.9; Sun, 6 Apr 2014 17:28:27 +0000 Received: from BL2PR02MB500.namprd02.prod.outlook.com ([10.141.95.147]) by BL2PR02MB500.namprd02.prod.outlook.com ([10.141.95.147]) with mapi id 15.00.0913.002; Sun, 6 Apr 2014 17:28:27 +0000 From: Alex Harui To: "dev@flex.apache.org" Subject: Re: Table Cell Composition Thread-Topic: Table Cell Composition Thread-Index: AQHPUXzT6xZr7znoZ0OTiHTvhQ4I85sEYuaA Date: Sun, 6 Apr 2014 17:28:27 +0000 Message-ID: References: <064E1E11-9285-4914-B9B2-3AC699555509@gmail.com> In-Reply-To: <064E1E11-9285-4914-B9B2-3AC699555509@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.9.131030 x-originating-ip: [204.201.224.50] x-forefront-prvs: 0173C6D4D5 x-forefront-antispam-report: SFV:NSPM;SFS:(10019001)(6009001)(428001)(24454002)(479174003)(51704005)(189002)(377454003)(199002)(81342001)(77982001)(90146001)(81542001)(59766001)(98676001)(87936001)(79102001)(65816001)(2656002)(66066001)(47446002)(94946001)(83506001)(80022001)(74876001)(95416001)(97336001)(76796001)(97186001)(76786001)(74366001)(95666003)(53806001)(49866001)(47736001)(99396002)(54356001)(93136001)(92566001)(80976001)(4396001)(94316002)(50986001)(47976001)(92726001)(56816005)(85306002)(69226001)(63696002)(76482001)(81686001)(36756003)(74706001)(83072002)(46102001)(87266001)(93516002)(85852003)(86362001)(56776001)(19580405001)(19580395003)(20776003)(83322001)(54316002)(81816001)(31966008)(74502001)(74662001);DIR:OUT;SFP:1102;SCL:1;SRVR:BL2PR02MB497;H:BL2PR02MB500.namprd02.prod.outlook.com;FPR:B6F5FE4D.3CEBDCD9.B6E39D0F.8CE78939.20207;MLV:sfv;PTR:InfoNoRecords;MX:1;A:1;LANG:en; received-spf: None (: adobe.com does not designate permitted sender hosts) Content-Type: text/plain; charset="us-ascii" Content-ID: <7C5EEB8FFA7F2C43B530D45217A2D229@namprd02.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: adobe.com X-Virus-Checked: Checked by ClamAV on apache.org On 4/6/14 2:42 AM, "Harbs" wrote: >While working on TLF tables, I came to the conclusion that the simplest >way to handle the composition is to create a separate TExtFlow for each >cell in a table. The reason for this being that the composition of each >cell is in fact completely separate from the composition of the main >text, and by separating it, we can compose all the cells before starting >composition of the table. Once the cells are composed, composing the >table is very straight-forward because we are dealing with known sizes. Makes sense to me. > >I think each cell would have its own EditManager, but share an >UndoManager with the main text. > >Does anyone have any concerns with this approach? Performance and memory, of course. Don't know if pooling would help or avoiding spending too much time on cells that are off-screen. > >Also: I'd like to reuse the composed cells of header and footer cells. >I'm not sure exactly where the text content is actually drawn. Can anyone >point me in the right direction? Not sure what you mean here. -Alex