Re: Update for FlexJS Falcon JX

Hi Suraj, We are far away farther. FlexJS changed it's name to Apache Royale. Take a look here [1] [1] https://royale.apache.org/ Thanks, Piotr On Wed, Jul 3, 2019, 9:00 PM suraj sethi wrote: > Hi Flex Dev Team, > > I am member of a project who is looking to compile a lot of > ActionScript/MX

Update for FlexJS Falcon JX

Hi Flex Dev Team, I am member of a project who is looking to compile a lot of ActionScript/MXML code to Javascript. I stumbled upon FlexJS and see that it can do the task that I am looking for. Though I see that it is in beta state and not production ready. Can you please provide an update on

Re: git commit: [flex-falcon] [refs/heads/develop] - FLEX-35359 fixed issue where absolute path for output compiler option on windows could result in empty source map file

I merged it and pushed. > On Sep 29, 2017, at 1:40 PM, Harbs wrote: > > Josh, > > flex-falcon has been moved to https://github.com/apache/royale-compiler/ > <https://github.com/apache/royale-compiler/> > > Could you change your origin to there and push? >

Re: git commit: [flex-falcon] [refs/heads/develop] - FLEX-35359 fixed issue where absolute path for output compiler option on windows could result in empty source map file

Harbs, Maven wasn't touch yet, but I hope to get my hands on that, once I got clear signal from Alex that Ant build is ready. Thanks, Piotr 2017-09-29 12:40 GMT+02:00 Harbs : > Josh, > > flex-falcon has been moved to https://github.com/apache/royale-compiler/ < > https

Re: git commit: [flex-falcon] [refs/heads/develop] - FLEX-35359 fixed issue where absolute path for output compiler option on windows could result in empty source map file

Josh, flex-falcon has been moved to https://github.com/apache/royale-compiler/ <https://github.com/apache/royale-compiler/> Could you change your origin to there and push? FYI to update for the new repos you need to do the following: 1. Point your origins to: https://github.com/apache/

Re: [1/2] git commit: [flex-falcon] [refs/heads/develop] - upgrade to Google Closure Compiler 20170626. They deprecated a lot of APIs so lots of changes were required. The primary change is that GCC i

http%3A%2F%2Fapache-fle >x-development.247.n4.nabble.com%2FRe-1-2-git-commit-flex-falcon-refs-h >eads-develop-upgrade-to-Google-Closure-Compiler-20170626-They-den-tp63822p >63823.html&data=02%7C01%7C%7Ce15ea38cf5764490c95708d4e192c559%7Cfa7b1b5a7b >34438794aed2c178decee1%7C0%7C0%7C636

Re: [1/2] git commit: [flex-falcon] [refs/heads/develop] - upgrade to Google Closure Compiler 20170626. They deprecated a lot of APIs so lots of changes were required. The primary change is that GCC i

I didn't see binaries for the newer source releae. On 8/12/17, 7:54 AM, "Piotr Zarzycki" wrote: >Hi Alex, > >I' wondering why you have switched to version "v20170626" instead of >newest "v20170806" ? > >Thanks, >Piotr > >

Re: [1/2] git commit: [flex-falcon] [refs/heads/develop] - upgrade to Google Closure Compiler 20170626. They deprecated a lot of APIs so lots of changes were required. The primary change is that GCC i

- Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Re-1-2-git-commit-flex-falcon-refs-heads-develop-upgrade-to-Google-Closure-Compiler-20170626-They-den-tp63822p63823.html Sent from the Apache Flex Development mailing

Re: [1/2] git commit: [flex-falcon] [refs/heads/develop] - upgrade to Google Closure Compiler 20170626. They deprecated a lot of APIs so lots of changes were required. The primary change is that GCC i

Hi Alex, I'm wondering why you have switched to version "v20170626" instead of newest "v20170806" ? Thanks, Piotr 2017-08-12 5:55 GMT+02:00 : > Repository: flex-falcon > Updated Branches: > refs/heads/develop 8d7e14740 -> 207a95872 > > > upgr

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

It seems that there is: https://jsperf.com/isnan-performance/2 I did not see much difference between methods in terms of performance. > On Aug 3, 2017, at 4:30 PM, Harbs wrote: > > I wonder if there’s a difference between Flash and JS.

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

IMO, it matters whether you are strictly/strongly typing or not. I have not spent the time to see what the compiler does for: var foo:String; if (isNaN(foo)) Do you get a compiler error? Or is it allowed and auto-coercion in the Flash runtime will do what JS does? You are correct that if you n

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

It seems dangerous to replace isNaN with someNumber !== someNumber. In that article, they said that isNaN() could return false positives, but I don't actually consider their example to be a false positive at all. I would fully expect isNaN() to return true for a string value. If we replaced that ex

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

Here's an article about isNaN is JS. http://adripofjavascript.com/blog/drips/the-problem-with-testing-for-nan-in -javascript.html Maybe the transpiler should not output isNaN and instead "someNumber !== someNumber" -Alex On 8/3/17, 6:30 AM, "Harbs" wrote: >Cool. > >I wonder if there’s a diffe

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

Cool. I wonder if there’s a difference between Flash and JS. The tests seem to indicate that isNaN() is very efficient in JS. It might be an interesting project to compare badly performing cases in Flash to their JS counterparts. BTW, I just ran into a case where booleans behave differently in

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

Switching away from isNaN() in Feathers improved performance in a measurable way. It wasn't just a guess. - Josh On Aug 2, 2017 11:53 PM, "Harbs" wrote: Ah. Thanks. (I haven’t had my coffee yet) ;-) It would be interesting to know if that really is more efficient. > On Aug 3, 2017, at 9:33 AM

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

Ah. Thanks. (I haven’t had my coffee yet) ;-) It would be interesting to know if that really is more efficient. > On Aug 3, 2017, at 9:33 AM, Greg Dove wrote: > > I assume it is if (unknownNumOrNaN != unknownNumOrNaN ) > > I have used things like if (unknownNumOrNaN *0 !=0) in the past but the

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

I assume it is if (unknownNumOrNaN != unknownNumOrNaN ) I have used things like if (unknownNumOrNaN *0 !=0) in the past but the above seems better On Thu, Aug 3, 2017 at 6:20 PM, Harbs wrote: > I’m curious. How does that work? > unknownNumOrNaN != NaN will always be true > > > On Aug 3, 2017,

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

I’m curious. How does that work? unknownNumOrNaN != NaN will always be true > On Aug 3, 2017, at 1:37 AM, Josh Tynjala wrote: > > Good one! To avoid the overhead of the isNaN() function call, I frequently > rely on the fact that NaN != NaN. > > - Josh > > On Wed, Aug 2, 2017 at 3:32 PM, Harbs

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

I like the idea of having the FlexJS framework specify non-initialization with its config files, and then most users will get initialization by default (obviously, with the option to have non-initialization too, if desired). - Josh On Wed, Aug 2, 2017 at 2:16 PM, Alex Harui wrote: > We have fle

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

Good one! To avoid the overhead of the isNaN() function call, I frequently rely on the fact that NaN != NaN. - Josh On Wed, Aug 2, 2017 at 3:32 PM, Harbs wrote: > Thanks for the history lesson. :-) > > This does bring up another difference between an initialized value of NaN > and undefined: >

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

https://jonnyjordan.com/blog/remove-send-email-button-off-macbook-2016-touch-bar-apple-mail/ > On Aug 3, 2017, at 1:00 AM, Dave Fisher wrote: > > I hate this Macbook’s touch top bar which puts a send

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

Thanks for the history lesson. :-) This does bring up another difference between an initialized value of NaN and undefined: NaN != NaN, while undefined == undefined > On Aug 3, 2017, at 1:00 AM, Dave Fisher wrote: > > I hate this Macbook’s touch top bar which puts a send button directly above

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

I hate this Macbook’s touch top bar which puts a send button directly above the delete key. > On Aug 2, 2017, at 2:50 PM, Dave Fisher wrote: > > Hi Folks, > > A peanut gallery look at NaN which is really a bit encoding for various kinds > of floating point number errors like underflow, overfl

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

Hi Folks, A peanut gallery look at NaN which is really a bit encoding for various kinds of floating point number errors like underflow, overflow, divided by 0, etc. In my Fortran past life we used XMISS as a special valu > On Aug 1, 2017, at 3:21 PM, Greg Dove wrote: > > Yes it does. NaN is a

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

We have flex-config.xml, air-config.xml, js-config.xml, etc. These config files are (or can be) different sets of defaults. Meanwhile, we currently build the FlexJS framework via compile-swf-config.xml and compile-js-config.xml and its equivalent in pom.xml. I have no problem using different def

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

> To me, this is all related to PAYG. To me, making the compiler generate PAYG code by default sounds like the FlexJS framework leaking into the rest of the ecosystem. Maybe this is a place where mxmlc and asjsc should go in different directions. It makes perfect sense to me for the compiler to do

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

ntext: http://apache-flex-development.247.n4.nabble.com/Re-git-commit-flex-falcon-refs-heads-develop-compiler-jx-Added-js-default-initializers-option-to-for-tp63636p63658.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

> My guess is that they would prefer to avoid 'Pain as you go' from incompatible > as3 justified by pay as you go. > The challenge for us then is to come up with the optimizations that both > you and Alex have mentioned, so that wherever possible the unneccessary > initializations are not expressed

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

Yes. I just tried the new compiler option and I can confirm that this is the case. Only local variables are initialized. Additionally: This: var len:int; Compiles to: var /** @type {number} */ len = 0 = null; > On Aug 2, 2017, at 7:34 AM, Alex Harui wrote: > > BTW, IIRC, VarDeclarationEmitter

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

That sounds great Harbs. It will be interesting to see the gzip comparisons. I suspect that there would have to be massive quantities of redundant initializations to cause a meaningful performance impact, but keen to see the data. >From my perspective I think the baseline should be as3 compatibil

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

I’m planning on using the new compiler options to compile my app with and without initialization. I want to compare the app size of those two options after gzipping to see if there’s an impact on code size. I’d also like to write up a doc with the pros and cons of both approaches and see if I c

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

To me, this is all related to PAYG. And also, coding "style" matters. If we want to allow every possible existing AS statement work as-is, then we must initialize every variable that has a different default in JS. I thought the results of the set of tests I ran was that some of those patterns th

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

What I mean is that if we can somehow have the values uninitialized in JS, but in all cases where uninitialized values somehow diverge with ActionScript behavior be solved (so the use cases would behave correctly), then we’d have the advantages of undefined together with expected AS behavior. I

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

I'll bet that most of time that non-initialized values bite me is when I'm checking if a member variable is null or not. I frequently rely on the fact that Object, String, and most classes default to null, and then I do something like this: if(this._myVar === null) { } I dread the day I need to g

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

I’d prefer if we could somehow get the best of both worlds. Sorry Harbs, but I don't get it. I think the agreement is already to 'have the best of both worlds'. The issue is what the default should be. I know that you don't think you could have both behaviours as the default :). If we take away p

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

Hi, > I think if booleans could fail even non-strict equality checks when they > are not initialized, then we should always initialize booleans, like we > currently do with int and uint. +1 > I would still like the see the compiler initialize everything by default so > that ActionScript behaves

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

I’d prefer if we could somehow get the best of both worlds. I don’t see a solution to that dilemma at the moment, but maybe we’ll come up with something... Harbs > On Aug 2, 2017, at 1:24 AM, Josh Tynjala wrote: > > Don't get me wrong. If you see value in it, then we definitely shouldn't > re

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

Don't get me wrong. If you see value in it, then we definitely shouldn't remove it as an option. However, for compatibility with the existing language, I'd prefer to see initialization be the default instead. - Josh On Tue, Aug 1, 2017 at 3:14 PM, Harbs wrote: > Any maybe vice versa... ;-p > >

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

Yes it does. NaN is an 'instance' of the Number type (even though it is 'Not a Number' ;) ) On Wed, Aug 2, 2017 at 10:18 AM, Harbs wrote: > Interesting. > > I’m not sure that I realized that NaN passes that test. Does it? > > > On Aug 2, 2017, at 1:12 AM, Greg Dove wrote: > > > > I agree unde

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

Interesting. I’m not sure that I realized that NaN passes that test. Does it? > On Aug 2, 2017, at 1:12 AM, Greg Dove wrote: > > I agree undefined works the same as NaN for many things for example, but it > fails on very basic things like if (x is Number)

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

Any maybe vice versa... ;-p Alex was planning on looking into whether he can solve the boolean problem, so let’s hold off until he does that. I think comparing two booleans is pretty rare although I have already run into if(myBool == false) not working. Changing it to if(!myBool) was simple eno

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

d value which basically without fail exposes > the > > bug. Initializing the values to NaN would mask the issues and make them > > harder to find. > > > > My $0.02, > > Harbs > > > > > On Aug 1, 2017, at 1:02 AM, joshtynj...@apache.org wrote: > >

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

ake them > harder to find. > > My $0.02, > Harbs > > > On Aug 1, 2017, at 1:02 AM, joshtynj...@apache.org wrote: > > > > Repository: flex-falcon > > Updated Branches: > > refs/heads/develop b04074bf0 -> c500b3fe5 > > > > > > co

Re: git commit: [flex-falcon] [refs/heads/develop] - compiler-jx: Added -js-default-initializers option to force uninitialized variables to default to the same values in JS as they do in SWF.

017, at 1:02 AM, joshtynj...@apache.org wrote: > > Repository: flex-falcon > Updated Branches: > refs/heads/develop b04074bf0 -> c500b3fe5 > > > compiler-jx: Added -js-default-initializers option to force uninitialized > variables to default to the same values in

Re: [FlexJS] Falcon AsJS Mismatch?

>>>> If I knew how, I’d help. >>>>>> >>>>>> Harbs >>>>>> >>>>>>> On Jul 16, 2017, at 6:30 PM, Alex Harui >>>>>>> wrote: >>>>>>> >>>>>>> Someo

Re: [FlexJS] Falcon AsJS Mismatch?

, I’d help. >>>>> >>>>> Harbs >>>>> >>>>>> On Jul 16, 2017, at 6:30 PM, Alex Harui >>>>>> wrote: >>>>>> >>>>>> Someone else is welcome to take over. This stuff is not something I >&

Re: [FlexJS] Falcon AsJS Mismatch?

oy >>>>> doing at all. >>>>> >>>>> -Alex >>>>> >>>>> On 7/16/17, 5:17 AM, "Harbs" >>>> <mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>> wrote: >>>>> >

Re: [FlexJS] Falcon AsJS Mismatch?

/17, 5:17 AM, "Harbs" >>> <mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>> wrote: >>>> >>>>> Is this with Alex’s latest changes? >>>>> >>>>> These backslash escapes seem really diffi

Re: [FlexJS] Falcon AsJS Mismatch?

.com <mailto:harbs.li...@gmail.com>>> wrote: >>> >>>> Is this with Alex’s latest changes? >>>> >>>> These backslash escapes seem really difficult to get right… :-( >>>> >>>>> On Jul 16, 2017, at

Re: [Falcon] operand stack underflow?

j%2BQLhaog >> 6J7PtqxlFPFzv7AhOSN6OMMkyOQS5poGs%3D&reserved=0 >> >> From: Yishay Weiss<mailto:yishayj...@hotmail.com> >> Sent: Monday, July 17, 2017 4:24 PM >> To: dev@flex.apache.org<mailto:dev@flex.apache.org> >> Subject: RE: [Falcon] operand st

Re: [Falcon] operand stack underflow?

data=02%7C01%7C%7Cf1bb25daf78840b0f68e08d4cd191b07%7Cfa7b1b >5a7b34438794aed2c178decee1%7C0%7C0%7C636358955087940048&sdata=SMj%2BQLhaog >6J7PtqxlFPFzv7AhOSN6OMMkyOQS5poGs%3D&reserved=0 > >From: Yishay Weiss<mailto:yishayj...@hotmail.com> >Sent: Monday, July 17, 2017 4:24 PM >To: dev

RE: [Falcon] operand stack underflow?

[1] https://paste.apache.org/STWV From: Yishay Weiss<mailto:yishayj...@hotmail.com> Sent: Monday, July 17, 2017 4:24 PM To: dev@flex.apache.org<mailto:dev@flex.apache.org> Subject: RE: [Falcon] operand stack underflow? I’m actually able to build after running the following batch file: cd \dev\flexj

RE: [Falcon] operand stack underflow?

I’m actually able to build after running the following batch file: cd \dev\flexjs\flex-falcon git pull call ant wipe-all cd \dev\flexjs\flex-typedefs call ant wipe git pull cd \dev\flexjs\flex-asjs call ant super-clean git pull ant clean all I am however getting a runtime error because of the

Re: [Falcon] operand stack underflow?

The previous error was what I got when using asconfigc in VS Code. Here’s the stack trace when building using Ant: https://paste.apache.org/Sy93 <https://paste.apache.org/Sy93> > On Jul 17, 2017, at 3:09 PM, Harbs wrote: > > I just updated flex-falcon and flex-asjs. After rebuil

[Falcon] operand stack underflow?

I just updated flex-falcon and flex-asjs. After rebuilding everything, I’m getting the following error when compiling my app: https://paste.apache.org/3wBr <https://paste.apache.org/3wBr> This is a new one for me… Suggestions? Harbs

Re: [FlexJS] Falcon AsJS Mismatch?

nges? >>> >>> These backslash escapes seem really difficult to get right… :-( >>> >>>> On Jul 16, 2017, at 2:41 PM, yishayw wrote: >>>> >>>> Looks like falcon is incompatible with TabStopsPropety.as in TLF. Wh

Re: [FlexJS] Falcon AsJS Mismatch?

ot; <mailto:harbs.li...@gmail.com>> wrote: > >> Is this with Alex’s latest changes? >> >> These backslash escapes seem really difficult to get right… :-( >> >>> On Jul 16, 2017, at 2:41 PM, yishayw wrote: >>> >>> Looks like falco

Re: [FlexJS] Falcon AsJS Mismatch?

, at 2:41 PM, yishayw wrote: >> >> Looks like falcon is incompatible with TabStopsPropety.as in TLF. When >> initializing that file I'm getting the following RTE: >> >> Uncaught syntax error: Invalid regular expression: missing / >> >> which ori

RE: [FlexJS] Falcon AsJS Mismatch?

Yea, flex-falcon is up2date. My ‘fix’ was to change TabStopsProperty.as:191 to private static const _escapeBackslashRegex:RegExp = new RegExp("\\" + "\\", "g"); I’m not pushing this yet so Alex or others can debug the RTE. From: Harbs<mailto:ha

Re: [FlexJS] Falcon AsJS Mismatch?

Is this with Alex’s latest changes? These backslash escapes seem really difficult to get right… :-( > On Jul 16, 2017, at 2:41 PM, yishayw wrote: > > Looks like falcon is incompatible with TabStopsPropety.as in TLF. When > initializing that file I'm getting the following RT

[FlexJS] Falcon AsJS Mismatch?

Looks like falcon is incompatible with TabStopsPropety.as in TLF. When initializing that file I'm getting the following RTE: Uncaught syntax error: Invalid regular expression: missing / which originates in TabStopsProperty.as:191 private static

Re: Build failed in Jenkins: flex-falcon #1627

Looks like it was the aborted flex-sdk build. Right now, many of our builds are dependent on the flex-sdk build, even the FlexJS builds. This is probably not a good thing, but I don't want to take the time right now to reconfigure our builds to use the "last good build" instead of the workspaces

Re: Build failed in Jenkins: flex-falcon #1627

-flex-falcon-1627-tp62646p62654.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: Build failed in Jenkins: flex-falcon #1627

Not sure. I've been looking into it for a while. I'm just kicked off a new SDK build. The most recent one was aborted and may have left the other downstream builds in a bad setup. -Alex On 6/27/17, 10:16 PM, "piotrz" wrote: >Does this failure is related to failing MD5Checker ? > >Piotr > > >

Re: Build failed in Jenkins: flex-falcon #1627

Hi, > Does this failure is related to failing MD5Checker ? I don't think so. It looks like one of the unit tests has failed. BUILD FAILED <http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/ws/build.xml <http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/ws/build.x

Re: Build failed in Jenkins: flex-falcon #1627

Does this failure is related to failing MD5Checker ? Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Re-Build-failed-in-Jenkins-flex-falcon-1627-tp62646p62651.html Sent from the Apache Flex

Re: Build failed in Jenkins: flex-falcon #1627

Hi, develop branch is failing. Can someone take a look into that ? I cannot figure out what is happening. Thanks, Piotr 2017-06-27 21:42 GMT+02:00 : > See <http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/1627/> > > -- > [...tr

Re: [1/2] git commit: [flex-falcon] [refs/heads/initializers] - make default initialisers configurable

Hi, > It is default swtich on as I understand ? No you use it to turn initialisers off. if you don’t use the compiler option then uninitialised Booleans will default to false and Numbers will default to NaN. This is different to how the current compiler does it. if you do use it then initiali

Re: [1/2] git commit: [flex-falcon] [refs/heads/initializers] - make default initialisers configurable

It is default swtich on as I understand ? Thanks, Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Re-1-2-git-commit-flex-falcon-refs-heads-initializers-make-default-initialisers-configurable

Re: [1/2] git commit: [flex-falcon] [refs/heads/initializers] - make default initialisers configurable

Hi, > Is this mean that if this property is true in config and I set my boolean > property to false it will be ignored ? No. If you do this it will be false. var prop:Boolean = false; If you do this it will be true. var prop:Boolean = true; If you do this: var prop:Boolean; it will be false a

Re: [1/2] git commit: [flex-falcon] [refs/heads/initializers] - make default initialisers configurable

Hi Justin, Is this mean that if this property is true in config and I set my boolean property to false it will be ignored ? var myProperty:Boolean = false; When I trace it I will see: undefined Piotr 2017-06-24 10:46 GMT+02:00 : > Repository: flex-falcon > Updated Branches: > r

Re: git commit: [flex-falcon] [refs/heads/develop] - [maven-release-plugin] prepare branch release/0.8.0

gt; [Discuss] thread. - If I'm not right let me know. > > Thanks for help! > Piotr > > > > - > Apache Flex PMC > piotrzarzyck...@gmail.com > -- > View this message in context: http://apache-flex- > development.247.n4.nabble.com/Re-git-commit-flex-falcon- >

Re: git commit: [flex-falcon] [refs/heads/develop] - [maven-release-plugin] prepare branch release/0.8.0

ntext: http://apache-flex-development.247.n4.nabble.com/Re-git-commit-flex-falcon-refs-heads-develop-maven-release-plugin-prepare-branch-release-0-8-0-tp62391p62396.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: git commit: [flex-falcon] [refs/heads/develop] - [maven-release-plugin] prepare branch release/0.8.0

che Flex PMC > piotrzarzyck...@gmail.com > -- > View this message in context: http://apache-flex- > development.247.n4.nabble.com/Re-git-commit-flex-falcon- > refs-heads-develop-maven-release-plugin-prepare-branch- > release-0-8-0-tp62391p62393.html > Sent from the Apache Flex Development mailing list archive at Nabble.com. >

Re: git commit: [flex-falcon] [refs/heads/develop] - [maven-release-plugin] prepare branch release/0.8.0

go with current release ? > > Piotr > > > > - > Apache Flex PMC > piotrzarzyck...@gmail.com > -- > View this message in context: http://apache-flex- > development.247.n4.nabble.com/Re-git-commit-flex-falcon- > refs-heads-develop-maven-release-plugin-prepare-branch- &g

Re: git commit: [flex-falcon] [refs/heads/develop] - [maven-release-plugin] prepare branch release/0.8.0

-- View this message in context: http://apache-flex-development.247.n4.nabble.com/Re-git-commit-flex-falcon-refs-heads-develop-maven-release-plugin-prepare-branch-release-0-8-0-tp62391p62393.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: git commit: [flex-falcon] [refs/heads/develop] - [maven-release-plugin] prepare branch release/0.8.0

ntext: http://apache-flex-development.247.n4.nabble.com/Re-git-commit-flex-falcon-refs-heads-develop-maven-release-plugin-prepare-branch-release-0-8-0-tp62391p62392.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: git commit: [flex-falcon] [refs/heads/develop] - [maven-release-plugin] prepare branch release/0.8.0

4, 2017 at 6:45 AM, wrote: > Repository: flex-falcon > Updated Branches: > refs/heads/develop 1ab66ebe9 -> cee43a034 > > > [maven-release-plugin] prepare branch release/0.8.0 > > > Project: http://git-wip-us.apache.org/repos/asf/flex-falcon/repo > Commit: http://gi

Re: Falcon build failing

(aside) Your client knows there are top level domains with more than 4 characters ? And that neither local parts or domain names are limited to ASCII any more ? Tom On 20/04/17 17:50, Harbs wrote: private static const emailRegExp:RegExp = /^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i;

Re: Falcon build failing

THANK YOU!!! That did it. Phew! I’m going to push my change to NativeUtils as well. > On Apr 20, 2017, at 11:16 PM, Alex Harui wrote: > > > > On 4/20/17, 7:44 PM, "Harbs" wrote: > >> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apa >> che.org%2FElpk&data=02%7C01%7

Re: Falcon build failing

On 4/20/17, 7:44 PM, "Harbs" wrote: >https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apa >che.org%2FElpk&data=02%7C01%7C%7C163cde5e1733430a17ff08d488605310%7Cfa7b1b >5a7b34438794aed2c178decee1%7C0%7C0%7C636283394673664681&sdata=yjTVit%2FtW8 >5rsXtx%2FRJZODRK15PM1GrpZNUf5C

Re: Falcon build failing

t;>>> public static var MAIL_PROTOCOL_PATTERN:RegExp = /^ *mailto:.*/i; >>>> public static var PAGE_PROTOCOL_PATTERN:RegExp = /^ *page: *(\d+) */i; >>>> public static var KEY_PROTOCOL_PATTERN:RegExp = /^ *key: *(\d+) */i; // >>>> /^key:(\d+)\s+$/; >>&

Re: Falcon build failing

/i; >>> public static var KEY_PROTOCOL_PATTERN:RegExp = /^ *key: *(\d+) */i; // >>> /^key:(\d+)\s+$/; >>> >>> private static const emailRegExp:RegExp = >>> /^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i; >>> >>> private static const urlRegExp:Re

Re: Falcon build failing

Exp:RegExp = >> /^(?:(?:https?|ftp):\/\/)?(?:[-\w]+\.)(?:[a-zA-Z\.]{2,6})(?:[?\/\w\.&=-]*) >> \/?$/i; >> >> >> Is there any way I can see what’s causing the error? I have no idea how >> to debug Falcon. >> >>> On Apr 20, 2017, at 10:39 AM, Alex

Re: Falcon build failing

[a-zA-Z\.]{2,6})(?:[?\/\w\.&=-]*) >\/?$/i; > > >Is there any way I can see what’s causing the error? I have no idea how >to debug Falcon. > >> On Apr 20, 2017, at 10:39 AM, Alex Harui wrote: >> >> What RegExp are you using? I can try it in HelloWorldTLF. &g

Re: Falcon build failing

ebug Falcon. > On Apr 20, 2017, at 10:39 AM, Alex Harui wrote: > > What RegExp are you using? I can try it in HelloWorldTLF. > > On 4/20/17, 7:18 AM, "Harbs" wrote: > >> No. I’m getting this in my app. >> >> I have not been able to figure ou

Re: Falcon build failing

gt;>1b5a7b34438794aed2c178decee1%7C0%7C0%7C636282947035930968&sdata=ykrDo05QM >>%2FE3G4aj45PuuOpSeOtdE4VwRQj2%2BeLX7Uk%3D&reserved=0> >> >> >> ____ >> From: Harbs >> Sent: Thursday, April 20, 2017 6:21:56 AM >> To: dev@flex.apach

Re: Falcon build failing

ui wrote: >> >> Should I be able to reproduce by building the branch? >> >> Get Outlook for Android<https://aka.ms/ghei36> >> >> >> >> From: Harbs >> Sent: Thursday, April 20, 2017 6:21:56 AM >

Re: Falcon build failing

ps://aka.ms/ghei36> > > > > From: Harbs > Sent: Thursday, April 20, 2017 6:21:56 AM > To: dev@flex.apache.org > Subject: Re: Falcon build failing > > Right. But I need the TLF build to work… ;-) > > FWIW, I’m having trouble coming up with a test

Re: Falcon build failing

Should I be able to reproduce by building the branch? Get Outlook for Android<https://aka.ms/ghei36> From: Harbs Sent: Thursday, April 20, 2017 6:21:56 AM To: dev@flex.apache.org Subject: Re: Falcon build failing Right. But I need the TLF build t

Re: Falcon build failing

Right. But I need the TLF build to work… ;-) FWIW, I’m having trouble coming up with a test case which shows the problem. > On Apr 20, 2017, at 8:53 AM, Christofer Dutz > wrote: > > Even if there is currently an issue not making all parts of the build chain > run automatically … the Maven bu

Re: Falcon build failing

Even if there is currently an issue not making all parts of the build chain run automatically … the Maven build is currently fully operational (as far as I can tell) Chris Am 20.04.17, 12:30 schrieb "Harbs" : This issue has me stalled. If anyone could help with this, it would be greatly

Re: Falcon build failing

This issue has me stalled. If anyone could help with this, it would be greatly appreciated. > On Apr 19, 2017, at 6:27 PM, Harbs wrote: > > FWIW, I tried adding RegExp("RegExp”), to NativeUtils.NativeJSType, but for > some reason it did not help. > >> On Apr 19, 2017, at 5:05 PM, Harbs wrote

Re: Falcon build failing

gt; getListOfFiles. >>>>>> >>>>>> -Alex >>>>>> >>>>>> On 3/28/17, 9:42 AM, "Harbs" wrote: >>>>>> >>>>>>> Looking at you change, I doubt it’ll fix my problem

Re: Falcon build failing

;>> >>>>> -Alex >>>>> >>>>> On 3/28/17, 9:42 AM, "Harbs" wrote: >>>>> >>>>>> Looking at you change, I doubt it’ll fix my problem because I WAS >>>>>> using >>>>>> remove-c

Re: Falcon build failing

Well, I just pushed more changes so FlexJSStore compiles and loads without errors, but it doesn't look right yet. I'll be digging into that shortly. Thanks, -Alex On 3/30/17, 12:18 PM, "Alex Harui" wrote: >I pushed some changes that might fix that. Let me know. FlexJSStore >still isn't runni

Re: [2/2] git commit: [flex-falcon] [refs/heads/develop] - block some goog classes from the list

These commits seem to fix the latest problems, but I’m still having the missing Application dependencies. Harbs > On Mar 31, 2017, at 10:35 AM, aha...@apache.org wrote: > > block some goog classes from the list > > > Project: http://git-wip-us.apache.org/repos/asf/flex-fa

Re: Falcon build failing

Alex, Your last commit had to break something. On jenkins and locally I'm getting following error [1] [1] https://paste.apache.org/MoHw Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Falcon-

Re: Falcon build failing

Now something else seems to be broken. The test_project I linked to earlier now gets no js files from the SDK other than Application.js and ApplicationBase.js. The compiler errs on Could not find file for class: org.apache.flex.core.UIHTMLElementWrapper Sorry… ;-) Harbs > On Mar 30, 2017, at

Re: Falcon build failing

I pushed some changes that might fix that. Let me know. FlexJSStore still isn't running with -remove-circulars so I'm using that as my test case. -Alex On 3/29/17, 2:06 PM, "Harbs" wrote: >I pulled in your latest changes. The NaN error is fixed, but I’m still >having the problem with the miss

  1   2   3   4   5   6   7   8   9   10   >