Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F3302BB16 for ; Sat, 14 Jan 2012 09:56:21 +0000 (UTC) Received: (qmail 46905 invoked by uid 500); 14 Jan 2012 09:56:21 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 46597 invoked by uid 500); 14 Jan 2012 09:56:08 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 46579 invoked by uid 99); 14 Jan 2012 09:56:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Jan 2012 09:56:05 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mattjpoole@gmail.com designates 209.85.216.175 as permitted sender) Received: from [209.85.216.175] (HELO mail-qy0-f175.google.com) (209.85.216.175) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Jan 2012 09:55:59 +0000 Received: by qcsp14 with SMTP id p14so648306qcs.6 for ; Sat, 14 Jan 2012 01:55:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=aWfPfzBSKiRatbaMD/ufVoVmoKb7Tr1p/skFur75GJw=; b=U8X5Czz5YLBWNGf812Vhz/WFaf8QyMM3tfWEoZ9a+sI5l1dYvqaeN+1o75gfr5bpzZ y0aSozV9d8fTKTd3HaT1jtGf7qB3Vvi1jnTZfhN5B4PechsSLTI3mX1j5VG7HzOxb2AW eEhoReXWXGzR1M3StqVzZdSCs1+5x20sjDI2k= MIME-Version: 1.0 Received: by 10.229.136.84 with SMTP id q20mr1712890qct.152.1326534938236; Sat, 14 Jan 2012 01:55:38 -0800 (PST) Received: by 10.229.53.136 with HTTP; Sat, 14 Jan 2012 01:55:38 -0800 (PST) In-Reply-To: References: <93183756-61F1-44EA-A704-852DFEB73B65@artim-interactive.nl> Date: Sat, 14 Jan 2012 09:55:38 +0000 Message-ID: Subject: Re: GPU / DisplayList / Future of Flex From: Matthew Poole To: flex-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=00248c76901ac69a9f04b679fb52 X-Virus-Checked: Checked by ClamAV on apache.org --00248c76901ac69a9f04b679fb52 Content-Type: text/plain; charset=ISO-8859-1 >> Such a thing is possible, although there may be issues around accessibility are you thinking screen readers or something else? On 13 January 2012 00:42, Alex Harui wrote: > > > > On 1/12/12 1:26 AM, "Arnoud Bos" wrote: > > > So i tend to think that Adobe dropped flex for this reason too (there > are of > > course more reasons, but this one is never outspoken). > > Performance might never come close to native as it's al based on the > > displaylist. > I doubt that was factor in anyone's mind. Adobe did not "drop" Flex, Adobe > is donating it to Apache. > > > So i wonder could the future version of Flex use a similar approach? I > think > > if we can pull it of to render on the GPU it would be a massive > performance > > gain. It would give Flex an extra egde. > > I know there are many people on this list with deeper understanding of > the > > flash player so please enlighten me. Is such an approach even possible > for > > Flex? > Such a thing is possible, although there may be issues around > accessibility. > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > > --00248c76901ac69a9f04b679fb52--