I think there is confusion about what -createImages does. It creates new
baselines based on whatever the code and player on your computer generates
and says it passes if it can successfully create the bitmap. That option
should only be used to create a reference image, and nobody else running
tha
Well, from what I can see, the update of the build.properties like that
solve the problem:
#10.3
swf.version = 12
#11.0
#swf.version = 13
#11.1
#swf.version = 14
#11.3
#swf.version = 15
#11.4
#swf.version = 16
building the framework against a particular playerglobal and swf-version and
running
Alex,
Could you please enlighten me, I'm a bit confuse now, looking at the build
of the Mustella tests, I found it uses the flex-config.xml wherein I
defined the playerglobal and swf version thru the build.properties, so, the
mustella tests are also compile with those arguments or I'm wrong ?
Ok, I've got it.
I thought building the framework with the good swf-version was enough :$
So, I'm gonna wait for your thoughts doing some experiments thru time.
-Message d'origine-
From: Alex Harui
Sent: Saturday, October 27, 2012 6:58 PM
To: flex-dev@incubator.apache.org
Subject: Re:
I don't understand how your change to build.properties helps.
Running -createImages creates new baselines, so you would expect all tests
to pass. But if you check those in, then it will fail for other
swf-versions. I think the swf-version needs to be set at the SWF level in
the .compile file.
B
On 10/27/12 8:09 AM, "Frédéric THOMAS" wrote:
>> We could try changing the swf version on every test that doesn't require
>> it
> to a lower number and re-create all the baseline images.
>
> is the createImages option enough to build the baseline images?
Yes.
>
>> Explictly setting swf versio
If we can be sure that the swf-version drives how flash player draws fonts,
the correction is done.
Do you want me to attach a patch to the issue ?
-Message d'origine-
From: Frédéric THOMAS
Sent: Saturday, October 27, 2012 6:13 PM
To: flex-dev@incubator.apache.org
Subject: Re: About F
I updated the build.properties like that :
#10.3
swf.version = 12
#11.0
#swf.version = 13
#11.1
#swf.version = 14
#11.3
#swf.version = 15
#11.4
#swf.version = 16
building the framework against 10.3 and running the tests like that : sh
mini_run.sh tests/components/Label -createImages
The resul
We could try changing the swf version on every test that doesn't require
it
to a lower number and re-create all the baseline images.
is the createImages option enough to build the baseline images?
Explictly setting swf version might be the easiest to implement, and will
help expose where the
On 10/27/12 7:55 AM, "Frédéric THOMAS" wrote:
> I didn't changed the swf version at all, only the playerglobal.version =
> 10.3 in the build properties and the corresponding FP in env.properties :
>
>
> env.FLASHPLAYER_DEBUGGER=T:\\opt\\flashplayer-10.3.183.29\\flashplayer_debug.e
> xe
> #en
I didn't changed the swf version at all, only the playerglobal.version =
10.3 in the build properties and the corresponding FP in env.properties :
env.FLASHPLAYER_DEBUGGER=T:\\opt\\flashplayer-10.3.183.29\\flashplayer_debug.exe
#env.FLASHPLAYER_DEBUGGER=T:\\opt\\flashplayer-11.1.102.63\\flashpl
On 10/27/12 5:02 AM, "Frédéric THOMAS" wrote:
> Back on 10.3, I did some adjustments: setting
> DEFAULT_NUM_COLOR_VARIANCES:int = 255 and the default value of
> ignoreMaxColorVariance to true in the CompareBitmap class, I've been able to
> reduce the number of failed tests to 1 (only
> text_lo
On 10/27/12 5:32 AM, "Frédéric THOMAS" wrote:
>> Looks like 10.3 chooses antialiasing differently than 11.1
>
> I can be wrong but it doesn't seem relative to the version of the Flash
> Player because whatever the Flash Player version I was using during the
> tests while compiling with player
I did not even know that AS2 worked on AIR mobile :)
What i was afraid of, was that AIR mobile had a different backward
compatibility strategy than flash player on desktop has.
If not thats great news, and this ASNext, VMNext thing is not a survival
subject for flex, so thats great.
FYI, about
Hi,
I've spent some time on this today. I've created very a basic spreadsheet
[1] to keep track of the progress and don't clutter the list with jira
updates. I've shared it so anyone can check or update it.
Mike, this is the process I've been following so far:
1. Create the config file and update
Hi Thibault,
Thanks for your answers.
So if i understand well, and to get things straight, it means that we
will be able to target future mobile hardwares /OS that Adobe AIR
runtime will target in its new gaming and premium video stratey (windows
phone, for example) with captive runtime, even i
[
https://issues.apache.org/jira/browse/FLEX-33226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chema Balsas updated FLEX-33226:
Attachment: halo_compile.diff
Config files for halo compile target
> Convert sdk p
[
https://issues.apache.org/jira/browse/FLEX-33226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chema Balsas updated FLEX-33226:
Attachment: mobilecomponents_compile.diff
Config files for mobilecomponents compile target
[
https://issues.apache.org/jira/browse/FLEX-33226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chema Balsas updated FLEX-33226:
Attachment: mobiletheme_compile.diff
Config files for Mobiletheme compile target
>
Looks like 10.3 chooses antialiasing differently than 11.1
I can be wrong but it doesn't seem relative to the version of the Flash
Player because whatever the Flash Player version I was using during the
tests while compiling with playerglobal 10.3, the number of failures was the
same, can it
Back on 10.3, I did some adjustments: setting
DEFAULT_NUM_COLOR_VARIANCES:int = 255 and the default value of
ignoreMaxColorVariance to true in the CompareBitmap class, I've been able to
reduce the number of failed tests to 1 (only
text_long_property_Label_Spark.png doesn't pass and I can't get
[
https://issues.apache.org/jira/browse/FLEX-33226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chema Balsas updated FLEX-33226:
Attachment: spark_dmv_compile.diff
Config file for spark_dmv compile target
> Conv
[
https://issues.apache.org/jira/browse/FLEX-33236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tigran Najaryan updated FLEX-33236:
---
Description:
To reproduce:
1. Import attached project to Flash Builder and run in Profile mo
[
https://issues.apache.org/jira/browse/FLEX-33236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tigran Najaryan updated FLEX-33236:
---
Attachment: MemoryLeakTest.fxp
> Calling automationManager2.getChildren() on Spark DataGr
Tigran Najaryan created FLEX-33236:
--
Summary: Calling automationManager2.getChildren() on Spark
DataGrid causes memory leak
Key: FLEX-33236
URL: https://issues.apache.org/jira/browse/FLEX-33236
Proje
[
https://issues.apache.org/jira/browse/FLEX-33226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chema Balsas updated FLEX-33226:
Attachment: wireframe_compile.diff
Config file for wireframe compile target
> Conv
[
https://issues.apache.org/jira/browse/FLEX-33226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chema Balsas updated FLEX-33226:
Attachment: sparkskins_compile.diff
Config file for sparkskins compile target
> Co
[
https://issues.apache.org/jira/browse/FLEX-33228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chema Balsas updated FLEX-33228:
Attachment: rpc_compile.diff
Config file for compile target
> Config files for fra
[
https://issues.apache.org/jira/browse/FLEX-33227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chema Balsas updated FLEX-33227:
Attachment: framework_compile.diff
Config file for compile target
> Config files f
[
https://issues.apache.org/jira/browse/FLEX-33226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485391#comment-13485391
]
Chema Balsas edited comment on FLEX-33226 at 10/27/12 9:03 AM:
-
Forget my last post please, env.properties hasn't been saved.
The actual result for Label is :
[java] =
[java] Failed:
[java] =
[java]
[java]
[java] ==
[
https://issues.apache.org/jira/browse/FLEX-33226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485391#comment-13485391
]
Chema Balsas commented on FLEX-33226:
-
I've just compiled a basic spreadsheet to keep
Just did the tests on Label against the 11.4 and had the same failures than
the 10.3
-Message d'origine-
From: Justin Mclean
Sent: Saturday, October 27, 2012 2:19 AM
To: flex-dev@incubator.apache.org
Subject: Re: About Flex runtime
Hi,
Looks like 10.3 chooses antialiasing differentl
[
https://issues.apache.org/jira/browse/FLEX-33229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chema Balsas updated FLEX-33229:
Attachment: mx_compile.diff
Added apache header
> Config files for frameworks/proj
[
https://issues.apache.org/jira/browse/FLEX-33226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chema Balsas updated FLEX-33226:
Attachment: (was: mx_compile_config.diff)
> Convert sdk project compile targets to include
[
https://issues.apache.org/jira/browse/FLEX-33233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485381#comment-13485381
]
Frédéric THOMAS commented on FLEX-33233:
Here, the related failures output on Labe
This one https://issues.apache.org/jira/browse/FLEX-33233
-Message d'origine-
From: Om
Sent: Saturday, October 27, 2012 9:18 AM
To: flex-dev@incubator.apache.org
Subject: Re: About Flex runtime
On Fri, Oct 26, 2012 at 10:45 PM, Alex Harui wrote:
On 10/26/12 10:08 PM, "Om" wrote:
On Fri, Oct 26, 2012 at 10:45 PM, Alex Harui wrote:
>
>
> On 10/26/12 10:08 PM, "Om" wrote:
>
> > Alex,
> >
> > Is there a JIRA ticket for this?
> A JIRA ticket for what?
For this:
Alex:
> Haven't tried any other players. It would be great to see other community
> members try it out.
>
38 matches
Mail list logo
