On 10/28/12 12:37 AM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote:
>> Maybe I'm not understanding your strategy. If someone tries to use your
> proposed build.properties and changes player versions, they will get
> failures against your 10.3 baselines, won't they?
>
> If someone check out the sdk and in order to build it for another particular
> version, changes the build.properties to be in 10.3/12 for example, he will
> have to generate the baseline images before to do any change to the code,
> those baseline images in the context this playerglobal/swf-version are
> valids.
The SDK should not need to be built for particular player versions. The SDK
is all SWCs. Only when you build an app do you actually pick a player
version. If you choose an old player version and run SDK code that requires
newer player APIs then you will get a verify error. I'm interested to see
if we have any such code paths that aren't compartmentalized.
>
>> I'm set up for 11.1, how am I supposed to get mustella to pass if you
>> check
> in 10.3 baselines?
>
> The baseline images generated should not be check in to the svn server by
> contributors, the base still has to be the existing 11.1/14.
>
If you run -createImages locally, how will you verify that you are set up
correctly?
If you want to check in a change to the SDK, will you have to verify it on
11.x first?
Anyway, I'm leaning towards trying out the display-list comparision
technique again. I keep finding rendering differences between Flash and AIR
as well. That will potentially be too many combinations to track baselines
for.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
