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.238 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Tue, 6 Nov 2012 15:03:05 -0800
Subject: Re: About Flex runtime
Thread-Topic: About Flex runtime
Thread-Index: Ac28cOzrXOeUoT9BTHGxqOqxN/TdIgAAfQIO
Message-ID: <CCBED729.481F3%aharui@adobe.com>
In-Reply-To: <BLU162-ds52D295971AE90676B0C34B46B0@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.13.0.120411
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


On 11/6/12 2:48 PM, "Fr=E9d=E9ric THOMAS" <webdoublefx@hotmail.com> wrote:

> ok, I see :)
>=20
> ps: Given it's slower, will it be mixed with the today pixel based framew=
ork
> in order to be used only when there is hassle dealing with differences in
> the rendering pipeline ?
>=20
I suppose we could do that.  We'll see as I get farther into it.  My fear i=
s
that the next player version will break the bitmaps again and we'll have to
go and replace all of the remaining CompareBitmaps.  It might be better to
just accept the fact that we need to spend extra time to do display list
comparision.  There may also be a way to speed up the current algorithm.

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