[4.14] # Apache Flex SDK 4.14 nightly build 51: Successful

flex-sdk_release-candidate - Build #51 - Successful Changes since last build: [bigosmallm] Add non iOS7/Android skinclass and bring back old BusyIndicator behavior - to fix Mustella tests For more information, check the console output at http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_re

Re: How to know what playerglobalHome is set to?

On 12/29/14, 2:44 AM, "Left Right" wrote: >I'm trying to build a project previous built with SDK 4.6 and I'm getting >this: > >[mxmlc] /home/wvxvw/projects/flex-sdk/frameworks/flex-config.xml(65): >Error: unable to open '{playerglobalHome}/11.1/playerglobal.swc' >[mxmlc] >[mxmlc]

Re: [4.14] binary vs. source package legal docs

Digging into Saxon, I’m stuck on the CERN NOTICE. We are going to have to ask on legal-discuss to get approval to use Saxon. I will open a LEGAL JIRA shortly. A CERN license for something called COLT got approved, but instructions seem to be to ask for any other CERN code. I think we have the o

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Question: Is there a way to specify the order tests are run? One of the failures is in WritingModeTest. The arabicDirection test is failing when all the tests are run, but passing when the WritingModeTest is run by itself. I want to see what happens if I run WritingModeTest as the first test su

Re: [4.14] binary vs. source package legal docs

Hi, > Digging into Saxon, I’m stuck on the CERN NOTICE. We are going to have to > ask on legal-discuss to get approval to use Saxon. I will open a LEGAL > JIRA shortly. Do we know if the CERN license actually applies to anything in the jar? The GPL "notice" for instance refers to the .net vers

Re: Building Falcom

Re' patches: many of the jars loaded by the build script may already exist on the user's system. At least Guava, JFlex, ANTLR, Java CUP, JBurg and LZMA are all installable on Linux in a more conventional way (i.e. through the package manager). Wouldn't it be better to first test for installed jars

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Another question: One of the other failing tests is this one: [Test] public function bindableSpan():void { // Bindable span should not lose its formatting var textFlow:TextFlow = new TextFlow(); var paragraph:ParagraphElement = new Parag

Falcon internal error related to identifier resolution (?)

[mxmlc] /home/wvxvw/workspace/hx-player/player/as3/com/powtoon/ui/Stylable.as [mxmlc] Error: Internal error in ABC generator subsystem, when generating code for: /home/wvxvw/workspace/hx-player/player/as3/com/powtoon/ui/Stylable.as: java.lang.IllegalArgumentException: Label org.apache.flex

Falcon don't warn on assignment in while (condition) body

I looked into mxmlc -help warnings but I don't see an option to void the warning issued on assignment inside while (and maybe other such places). Is there one, or it simply isn't implemented yet? Thanks!

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Hi Harbs, Yes you can order items in your unit test class. Take a look [1] [1] https://cwiki.apache.org/confluence/display/FLEX/FlexUnit+Order Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/DISCUSS-R

Re: Falcon internal error related to identifier resolution (?)

I was able to find the error: private function loadDescriptionBytes(request:ByteArray, success:Function, failure:Function):void { var result:Object; try { try { result = request.read

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Okay, but how do we change the order in AllTestsSuite? I want to move WritingModeTest to the top. Changing the order of the variables does not seem to do anything. On Dec 30, 2014, at 11:51 AM, piotrz wrote: > Hi Harbs, > > Yes you can order items in your unit test class. Take a look [1] > >

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

BTW, I just made another commit. The only real error left seems to be an Operation test error where a new span is being inserted into a Link element rather than being inserted after it. On Dec 30, 2014, at 12:07 PM, Harbs wrote: > Okay, but how do we change the order in AllTestsSuite? I want t

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Try to put public var writingModeTest:WritingModeTest; in the first place in AllTestsSuite - It could help and run WritingModeTest as first. Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/DISCUSS-Relea

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

I tried that. It did not make a difference. On Dec 30, 2014, at 12:17 PM, piotrz wrote: > Try to put public var writingModeTest:WritingModeTest; in the first place in > AllTestsSuite - It could help and run WritingModeTest as first. > > Piotr > > > > - > Apache Flex PMC > piotrzarzyck...

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

The order the tests are run seems to have nothing to do with the order of variables or alphabetical order. On Dec 30, 2014, at 12:20 PM, Harbs wrote: > I tried that. It did not make a difference. > > On Dec 30, 2014, at 12:17 PM, piotrz wrote: > >> Try to put public var writingModeTest:Writi

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Java 1.8: Tests run: 428, Failures: 1, Errors: 0, Skipped: 42, Time elapsed: 257.348 sec Java 1.6: Tests run: 428, Failures: 2, Errors: 0, Skipped: 42, Time elapsed: 500.364 sec EdB On Tue, Dec 30, 2014 at 11:09 AM, Harbs wrote: > BTW, I just made another commit. The only real error left s

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Ok so try to add [TestCase(order=1)] tag to WritingModeTest class from my link. - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43990.html Sent from the Apache Flex D

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

The consistent failure was OperationTest.insertTextTest Right? The second one should be WritingModeTest.arabicDirection. It consistently fails for me when I run all the test, but passed when I only run WritingModeTest. On Dec 30, 2014, at 12:24 PM, Erik de Bruin wrote: > Java 1.8: > > Tests

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

That goes in WritingModeTest.as or in AllTestsSuite.as? (I still have no clue how these tests are working internally. It makes me very uncomfortable to be working with them as “black boxes”…) On Dec 30, 2014, at 12:27 PM, piotrz wrote: > Ok so try to add [TestCase(order=1)] tag to WritingModeT

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Put it in the WritingModeTest [TestCase(order=1)] public class WritingModeTest I haven't ordered unit test classes yet, so this is only my guess, whether this help. - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabb

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

It did not help. On Dec 30, 2014, at 12:45 PM, piotrz wrote: > Put it in the WritingModeTest > > [TestCase(order=1)] > public class WritingModeTest

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Ok. I will have some time on Saturday or Sunday and will try to look into that. - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43995.html Sent from the Apache Flex

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

I got: "insertTextTest in suite UnitTest.Tests.OperationTest" on both Javas; "paddingBottomTest ([object Object]) in suite UnitTest.Tests.ContainerAttributeTest failed." only on Java 1.6. HTH, EdB On Tue, Dec 30, 2014 at 11:29 AM, Harbs wrote: > The consistent failure was OperationTest.ins

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

I’ve been getting the ContainerAttributeTest failure on and off. I have a feeling it’s a rounding error problem. If so, I’ll fix the test to take that into account… On Dec 30, 2014, at 1:32 PM, Erik de Bruin wrote: > I got: > > "insertTextTest in suite UnitTest.Tests.OperationTest" > > on bo

Out of memory trying to uncompress SWFs generated with Falcon using ByteArray.uncompress()

I understand that not all LZMA variants are understood by ByteArray, but it would be super-friendly if Flex SDK generated such SWFs which could be read using ByteArray... Attached SWF was compiled using Falcon, but can't be read using ByteArray. Thanks! timeline.swf Description: application/sho

Re: Out of memory trying to uncompress SWFs generated with Falcon using ByteArray.uncompress()

PS. Is there a way to control what compression algorithm is chosen by the compiler to produce SWFs? On Tue, Dec 30, 2014 at 1:49 PM, Left Right wrote: > I understand that not all LZMA variants are understood by ByteArray, > but it would be super-friendly if Flex SDK generated such SWFs which > co

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Jup, that last commit took care of that "problem" ;-) EdB On Tue, Dec 30, 2014 at 12:35 PM, Harbs wrote: > I’ve been getting the ContainerAttributeTest failure on and off. I have a > feeling it’s a rounding error problem. If so, I’ll fix the test to take that > into account… > > On Dec 30, 2

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Yep Only one error left. I see some new errors, after last build we should see in ${output.dir}/apps/automation_apps/bin reports with unit tests results. Is it problem with file write ? Anyone know ? [flexunit] Tests run: 428, Failures: 1, Errors: 0, Skipped: 42, Time elapsed: 592.169 sec [fle

Falcon linking resources to ByteArray (rather than display objects)

I'm getting an error: TypeError: Error #2022: Class PlayerResource$ must inherit from DisplayObject to link to a symbol. for the class, which looks like this: package com.powtoon.assets { import flash.utils.ByteArray; [Embed(source="../../../../assets/hx-player.swf", mimeType="applicati

Re: Falcon linking resources to ByteArray (rather than display objects)

In addition to this, when linking symbols from other SWFs, the generated code must be incorrectly generated. The class below: package com.powtoon.assets { import flash.display.Sprite; [Embed(source="../../../../assets/WistiaPlayer2.swf", symbol="com.powtoon.assets.Scrubber")]

Re: Building Falcom

On 12/30/14, 1:06 AM, "Left Right" wrote: >Re' patches: many of the jars loaded by the build script may already >exist on the user's system. At least Guava, JFlex, ANTLR, Java CUP, >JBurg and LZMA are all installable on Linux in a more conventional way >(i.e. through the package manager). Would

Re: [4.14] binary vs. source package legal docs

On 12/30/14, 1:03 AM, "Justin Mclean" wrote: >Hi, > >> Digging into Saxon, I’m stuck on the CERN NOTICE. We are going to have >>to >> ask on legal-discuss to get approval to use Saxon. I will open a LEGAL >> JIRA shortly. > >Do we know if the CERN license actually applies to anything in the j

[FALCON] internal error related to identifier resolution (?)

Hi, thanks for finding that. I forgot to ask you to use [FALCON] in the subject of these discussions (I changed the subject). Things like errors in the ABC subsystem might require advice from Gordon or Darrell. Thanks, -Alex On 12/30/14, 2:02 AM, "Left Right" wrote: >I was able to find the er

[FALCON] don't warn on assignment in while (condition) body

I don’t know for sure. Maybe Gordon or Darrell know if warning suppression is supposed to work in Falcon. On 12/30/14, 1:35 AM, "Left Right" wrote: >I looked into mxmlc -help warnings but I don't see an option to void >the warning issued on assignment inside while (and maybe other such >places)

Re: Out of memory trying to uncompress SWFs generated with Falcon using ByteArray.uncompress()

On 12/30/14, 3:50 AM, "Left Right" wrote: >PS. Is there a way to control what compression algorithm is chosen by >the compiler to produce SWFs? > >On Tue, Dec 30, 2014 at 1:49 PM, Left Right wrote: >> I understand that not all LZMA variants are understood by ByteArray, >> but it would be super

[FALCON] linking resources to ByteArray (rather than display objects)

OK, sounds like there are issues with embedding. It might also be helpful to have JIRA issues to track these. -Alex On 12/30/14, 7:22 AM, "Left Right" wrote: >In addition to this, when linking symbols from other SWFs, the >generated code must be incorrectly generated. The class below: > >packa

Re: Building Falcom

I never packaged Java libraries for Linux, but I'm marginally familiar with packaging Common Lisp. Of course it's not the same, but some principles will most likely apply there too. So, the idea is that packages are made to depend on some other package, which handles their installation and provides

Re: Out of memory trying to uncompress SWFs generated with Falcon using ByteArray.uncompress()

Yes, some further investigation showed that the way the compiler writes the LZMA payload and the way ByteArray.uncompress() expects it to be are incompatible. But one can manipulate them to get ByteArray to load LZMA payload, see the end of this discussion: https://bugzilla.mozilla.org/show_bug.cgi

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Whoopee! I just fixed the last failing test just in time for the new year! TLF should now be good to go. :-) I’ll try to write a wiki on the table support sometime over the next few days. When I have some time, I’ll also try to take a look at the ignored tests and see which ones I can get oper

Re: rc_flex-sdk_mustella-mobile - Build # 73 - Still Failing!

I don't think my changes went through with this run. Also, the run number says #73, but only changes till #63 are shown. Is something going on with the job? Thanks, Om On Tue, Dec 30, 2014 at 9:27 AM, wrote: > rc_flex-sdk_mustella-mobile - Build # 73 - Still Failing: > > http://flex-mustella.

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Could someone take a look at the error on the CI server? The TLF build is passing, but there’s some kind of Java error: ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception java.io.IOException: remote file operation failed:

Re: flex-sdk_mustella - Build # 1319 - Still Failing!

On 12/29/14, 12:42 AM, "Erik de Bruin" wrote: >You can download the 'bad' pngs from this URL (mind the >'[buildnumber]' replacer): Yeah, I know, I was just musing that it would be even faster if we had a Flex app that would show you the diffs without having to download the bad.pngs. I looke

Re: rc_flex-sdk_mustella-mobile - Build # 73 - Still Failing!

Look to me like your last check in is mentioned in this log. On 12/30/14, 11:48 AM, "OmPrakash Muppirala" wrote: >I don't think my changes went through with this run. Also, the run number >says #73, but only changes till #63 are shown. Is something going on with >the job? > >Thanks, >Om > >On

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Harbs, Congratulations! You are absolutly the best! :) Do you still want me to look into tests ordering? Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p44

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Thanks. :-) I’m not getting that error any more, so I guess there’s no need. On Dec 31, 2014, at 12:36 AM, piotrz wrote: > Harbs, > > Congratulations! You are absolutly the best! :) > > Do you still want me to look into tests ordering? > > Piotr > > > > - > Apache Flex PMC > piotrza

[Mobile] [Mustella] Need help with the Mustella tests

I have spent more time than I wanted to on the failing Mustella tests. I have managed to fix quite a few, but there are a still a bunch of cases that are failing. They don't look that hard to fix, but for the life of me, I have not been able to figure out what's happening. Can someone take over

Re: [FALCON] don't warn on assignment in while (condition) body

The falcon compiler and the (old) mxmlc compiler handle errors and warnings differently. In the mxmlc compiler a message is always an error/warning/info message at creation. In falcon, messages have a default severity but can be treated as an error, warning, or ignored. The configuration options to

Re: [FALCON] internal error related to identifier resolution (?)

>{ >// result = >// { >// get: function():Object >// { >// return JSON.parse(request.toString()); >// } >// }; To further

[4.14] # Apache Flex SDK 4.14 nightly build 52: Successful

flex-sdk_release-candidate - Build #52 - Successful Changes since last build: [bigosmallm] Fixes the default rotationInterval Mustella test. For more information, check the console output at http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/52/.

Re: [FALCON] internal error related to identifier resolution (?)

Darrell, isn't that "get" simply a field/property with a function value? If the issue is with the get keyword as a property name, then the OP could try using json-style field naming, with quotes: result = { "get": function():Object { return JSON.parse(request.toString()); }

Re: [FALCON] internal error related to identifier resolution (?)

Yeah, I had to read it twice, but I believe result is supposed to be assigned to an Object with a property called “get” that points to a function. The {} after result is an Object literal. On 12/30/14, 8:03 PM, "Greg Dove" wrote: >Darrell, isn't that "get" simply a field/property with a functio

Re: Out of memory trying to uncompress SWFs generated with Falcon using ByteArray.uncompress()

On 12/30/14, 9:38 AM, "Left Right" wrote: >Yes, some further investigation showed that the way the compiler >writes the LZMA payload and the way ByteArray.uncompress() expects it >to be are incompatible. But one can manipulate them to get ByteArray >to load LZMA payload, see the end of this dis

Re: Jenkins build is back to normal : flex-tlf #265

This is AWESOME!!! Thanks Harbs and Piotr for sticking with this and giving the community a stable new version of TLF (not to mention making me feel much more relaxed about the upcoming release ;-)). EdB On Wed, Dec 31, 2014 at 8:24 AM, wrote: > See

Re: [jira] [Created] (FLEX-34657) SelectedIndices order is messed up

Justin, Can you please follow up on the status of your claim that the fix doesn't fix the issue? EdB On Sun, Dec 28, 2014 at 8:58 AM, Erik de Bruin wrote: >> 1. Select multiple items by holding down shift >> 2. Unselect and select the last selected item > > In this case, Shift-click selecting

Re: Jenkins build is back to normal : flex-tlf #265

This was a really nice email to get… ;-) Did someone do something to the CI server to make the Java errors go away? On Dec 31, 2014, at 9:28 AM, Erik de Bruin wrote: > This is AWESOME!!! > > Thanks Harbs and Piotr for sticking with this and giving the community > a stable new version of TLF (n