Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of aharui@adobe.com designates
 64.18.1.189 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
CC: Arnoud Bos <arnoud@artim-interactive.nl>
Date: Thu, 12 Jan 2012 16:42:53 -0800
Subject: Re: GPU / DisplayList / Future of Flex
Thread-Topic: GPU / DisplayList / Future of Flex
Thread-Index: AczRDHCgf2VJVwMITimGvGmJw9A97wAf9fxm
Message-ID: <CB34BE0D.39E3F%aharui@adobe.com>
In-Reply-To: <93183756-61F1-44EA-A704-852DFEB73B65@artim-interactive.nl>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


On 1/12/12 1:26 AM, "Arnoud Bos" <arnoud@artim-interactive.nl> 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.
=20
> So i wonder could the future version of Flex use a similar approach? I th=
ink
> if we can pull it of to render on the GPU it would be a massive performan=
ce
> gain. It would give Flex an extra egde.
> I know there are many people on this list with deeper understanding of th=
e
> flash player so please enlighten me. Is such an approach even possible fo=
r
> Flex?
Such a thing is possible, although there may be issues around accessibility=
.

--=20
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui