Re: Trademark issue

So it does. The PMC are looking into this now, good spot ! Tom On 07/01/16 14:04, Josh Tynjala wrote: If you remove the www, it should load properly. They seem to using a modified version of the Apache Flex logo with the "Apache" text removed.

Re: [FALCONJX][FLEXJS] "as" keyword handling

On 1/8/16, 7:23 AM, "Andy Dufilie" wrote: >On Fri, Jan 8, 2016 at 1:43 AM, Alex Harui wrote: > >> >> But, IMO, for FlexJS, what really matters is what should happen in the >>JS >> output, and the essence of this thread is that in many cases, we can >>

Re: [FALCONJX][FLEXJS] "as" keyword handling

I should add that I strongly agree with Andy that we shouldn't change the default behavior of the existing forms of casting. That's why I made the above proposal for a special function that the emitter would know to strip away. It would allow us preserve the existing casting behavior, while

Re: [FALCONJX][FLEXJS] "as" keyword handling

I wonder if we could define some kind of special global function that would make the compiler and IDEs happy with assignments that would normally require casting, but the JS emitter could strip out the function call and assign directly. We could take advantage of the fact that the * type can be

Re: [FALCONJX][FLEXJS] "as" keyword handling

In the Randori compiler, I wrote the emitter to strip the cast during the emit stage. Mike On Fri, Jan 8, 2016 at 2:38 PM, Josh Tynjala wrote: > I wonder if we could define some kind of special global function that would > make the compiler and IDEs happy with

Re: [FALCONJX][FLEXJS] "as" keyword handling

On 1/8/16, 11:03 AM, "Andy Dufilie" wrote: >On Fri, Jan 8, 2016 at 12:53 PM, Alex Harui wrote: > >> >> On 1/8/16, 7:23 AM, "Andy Dufilie" wrote: >> >> >In all above cases, if Foo is a primitive type, function-style casting

Re: [FALCONJX][FLEXJS] "as" keyword handling

On 1/8/16, 11:38 AM, "Josh Tynjala" wrote: >I wonder if we could define some kind of special global function that >would >make the compiler and IDEs happy with assignments that would normally >require casting, but the JS emitter could strip out the function call and

Re: [FALCONJX][FLEXJS] "as" keyword handling

I understand what you're trying to do, and I want the same things. The greatest thing about FlexJS is that I am able to easily port my large project (seven years of development work) with minimal change. However, since my project relies heavily on the exact behavior of every AS language feature,

Re: [FALCONJX][FLEXJS] "as" keyword handling

On 1/8/16, 12:11 PM, "Josh Tynjala" wrote: >I should add that I strongly agree with Andy that we shouldn't change the >default behavior of the existing forms of casting. That's why I made the >above proposal for a special function that the emitter would know to strip

[4.15.0] # Apache Flex SDK 4.15.0 nightly build 161: Failure

flex-sdk_release-candidate - Build #161 - Failure Changes since last build: No changes For more information, check the console output at http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/161/.

Re: [FALCONJX][FLEXJS] "as" keyword handling

On Fri, Jan 8, 2016 at 12:53 PM, Alex Harui wrote: > > On 1/8/16, 7:23 AM, "Andy Dufilie" wrote: > > >In all above cases, if Foo is a primitive type, function-style casting can > >never be optimized out because Foo(x) will actually change the type of x.

Re: [FALCONJX][FLEXJS] "as" keyword handling

I would expect it to keep the same behavior and take a performance hit in exchange. You can always add the option to "speed up" the JS version by removing any of the casting methods. Have you tested the difference with it and without it in JS? *"...but the Google Closure Compiler implies that

Re: [FALCONJX][FLEXJS] "as" keyword handling

On 1/8/16, 11:39 PM, "jude" wrote: >I would expect it to keep the same behavior and take a performance hit in >exchange. You can always add the option to "speed up" the JS version by >removing any of the casting methods. Have you tested the difference with >it >and

draft blog post for 4.15 release

Hi, Anyone care to put together a draft blog post for this release? https://issues.apache.org/jira/browse/FLEX-34969 Thanks, Justin

Re: draft 4.15 release announcement

Seems ok. Thanks for doing it, -Alex On 1/8/16, 8:22 PM, "Justin Mclean" wrote: >Hi, > >Anyone have feedback on this? If not once the vote passes and the release >has propagated on the mirrors I’ll send this out in a day or two. > >Thanks >Justin > >— draft below --

draft 4.15 release announcement

Hi, Anyone have feedback on this? If not once the vote passes and the release has propagated on the mirrors I’ll send this out in a day or two. Thanks Justin — draft below -- Hi, The Apache Flex community is pleased to announce the release of Apache Flex 4.15.0 Apache Flex is a highly

Re: [DISCUSSION] Apache Flex SDK 4.15 release candidate 1

Hi, Anyone have any further feedback on RC1 before I we officially make it a release? Thanks, Justin

Re: [VOTE] Release Apache Flex SDK 4.15 RC1

Hi, +1 binding I checked: - LICENSE and NOTICE good - source files have Apache header - no unexpected binaries in source release - can compile from source Tested on OS X, and was able to make a working SDK following the instructions (for FB). Tested a few projects including browser, mobile,

AW: [ApacheCon NA] Whose going and what topics?

A track makes it easier to get at least enough talks for the track selected. Without a track it has to sort of fit into another track. Depending on how they cut the tracks this could be difficult. We we want to go for a track, I could re-submit updated versions of my last submissions regarding

Please help to make we skilled immigrants' handcuffs a little bit loose

The high skilled workers have to be locked to one employer for close to 10 years, here is how you can help us: http://www.petition2congress.com/17887/support-i140-ead Locking the skilled ends up they try to keep a job instead of generating value! Thank you! -Gary

Re: AW: [ApacheCon NA] Whose going and what topics?

On Jan 8, 2016 9:17 AM, "Alex Harui" wrote: > > I've been wondering if there should be a "Client" track as an umbrella for > both Flex and Cordova talks. Especially since FlexJS Mobile is output via > Cordova. If folks think that's a good idea I will hit up the Cordova > folks

Re: AW: [ApacheCon NA] Whose going and what topics?

I've been wondering if there should be a "Client" track as an umbrella for both Flex and Cordova talks. Especially since FlexJS Mobile is output via Cordova. If folks think that's a good idea I will hit up the Cordova folks I know to see what they think. -Alex On 1/8/16, 1:56 AM, "Christofer