AW: AW: [FlexJS] Problem with some test cases (@export was changed to @expose)?

Well the Maven build went back to blue ... thanks for fixing :-) I guess as I finished my work on the site deployment so the build works again. It's always worth to have a look at the official ASF Jenkins: https://builds.apache.org/view/E-G/view/Flex/ Even if it builds with Maven, it does al

Re: AW: [FlexJS] Problem with some test cases (@export was changed to @expose)?

Chris, I was seeing something not working with Maven in typedefs, a patch not being applied cleanly. I did not see this with ant. Justin also checked and confirmed this. Not sure if another url has changed? On Wed, Sep 28, 2016 at 8:03 PM, Christofer Dutz wrote: > Well the Maven build went bac

AW: AW: [FlexJS] Problem with some test cases (@export was changed to @expose)?

Currently the framework seems to have problems ... I noticed that, but I was a little too consumed with my duties ad TAC member to deal with it ... I better have a look as soon as possible. Chris Von: Greg Dove Gesendet: Mittwoch, 28. September 2016 09:06:12 A

Re: [FlexJS] HTMLElementWrapper extending Sprite

The overhead to swfs seem to me like it’s really minimal. There’s not a lot of added code for using composition rather than inheritance. Improving events is probably something which should be done for the JS side as well, so I’m not convinced that’s a major problem either. Some of the event iss

Re: [FlexJS][VSCode-NextGenAS] Getting to work with VSCode

Thanks Josh, I updated asconfigc vía nom to 0.1.5 and now is working :) Now that is compiling, I must figure how to run a simple example with flexes components :) 2016-09-28 0:55 GMT+02:00 Josh Tynjala : > Hey Carlos, > > The "unknown configuration variable" error was actually a bug in asconfigc

Re: [Falcon] Proposal for new ActionScript language feature: Optionally rename an import

As Flex was evolving through the years and things like Swiz born, I always want all this things implemented. This haxe framework has more of the things you would want: http://hexmachina.org/ But AFAIK, it lacks of something critical: MXML (for this reason haxe is still no option for many of us, sin

AW: AW: [FlexJS] Problem with some test cases (@export was changed to @expose)?

Could one of you guys please have a look at what's going wrong? I could track it back to the Framework expecting some different implementation of Class.as This seems to be generated in the js externs module ... I could track it back to being generated by the missing.js (line 120ff) I have no

AW: AW: [FlexJS] Problem with some test cases (@export was changed to @expose)?

Ok ... so I found out what the problem was :-) I dug through the code and was confused why it didn't work, because it should have. Had a look at other changes applied to the compiler recently and these too didn't seem to have an effect. To me it looked as if it was using an old version of the

[FlexJS] Circular dependency detected

Hi, while porting the "PureMVC EmployeeAdmin" demo to FlexJS I stumbled over the "Circular dependency detected" issue several times. I noticed that this was discussed here in the past but I can't find any helpful informations. So what I'd like to know if this is a bug with FlexJS (The swf version w

Re: [FlexJS] Circular dependency detected

Forgot to mention: Tried it with 0.7.0 and the nightly build. -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-Circular-dependency-detected-tp55396p55397.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

AW: AW: [FlexJS] Problem with some test cases (@export was changed to @expose)?

Ok now the modules that were failing compile successfully. Unfortunately now a little more down the stream the examples seem to be failing. I am getting errors in the chart example (just the first example to be compiled) It seems the JS compilation is failing because it cant find generated class

Re: [Falcon] Proposal for new ActionScript language feature: Optionally rename an import

I like this idea and would propose taking it one step further: Currently transpiled javascript has fully qualified class names for pretty much everything. This is difficult for closure to minimize completely. I’d really like to have some way to “export” class names as well as “import” to define

AW: Generics (was: Re: AW: [Falcon] Proposal for new ActionScript language feature: Optionally rename an import)

Would also be a great opportunity to eventually cleanup some really anoying quirks in the Language specification ... stuff like if you try to cast to Array, you get a new one containing the input as single element ... var test:* = ["lalala", "dumdidum"]; var arr:Array = Array(test); trace(arr

Re: [Falcon] Proposal for new ActionScript language feature: Optionally rename an import

If I understand you right you speak about "Single name aliases" [1]. This feature would be very helpful! Seems to me that tt was dropped from AS3 for whatever reason. Maybe this is helpful [2][3]. Thanks, Olaf [1] http://apache-flex-users.246.n4.nabble.com/AS3-Alias-name-for-imports-td13245.

Re: Generics (was: Re: AW: [Falcon] Proposal for new ActionScript language feature: Optionally rename an import)

For core classes like Number, Array, Boolean, etc. what looks like a cast is actually a function call. There's a global function named Array, and calling that takes precedence over casting. Personally, I think we should avoid breaking changes like this. - Josh On Wed, Sep 28, 2016 at 4:58 AM, Ch

Re: [Falcon] Proposal for new ActionScript language feature: Optionally rename an import

Interesting! Thanks for sharing, Olaf. As I understand it, Adobe tried to be very conservative about what they put into AS3 because they wanted to avoid adding things that didn't end up in the final approved version of ES4. I think I heard that there were already some differences, and they didn't w

Re: [FlexJS] Circular dependency detected

On 9/28/16, 2:12 AM, "OK" wrote: >Hi, >while porting the "PureMVC EmployeeAdmin" demo to FlexJS I stumbled over >the >"Circular dependency detected" issue several times. >I noticed that this was discussed here in the past but I can't find any >helpful informations. >So what I'd like to know if

Re: AW: AW: [FlexJS] Problem with some test cases (@export was changed to @expose)?

The Ant build doesn't build the examples. Maybe it should. The ChartExample fails for me from Ant as well. I will look into it. -Alex On 9/28/16, 2:30 AM, "Christofer Dutz" wrote: >Ok now the modules that were failing compile successfully. Unfortunately >now a little more down the stream the

Variable Renaming (was Re: [Falcon] Proposal for new ActionScript language feature: Optionally rename an import)

On 9/28/16, 3:25 AM, "Harbs" wrote: >I like this idea and would propose taking it one step further: > >Currently transpiled javascript has fully qualified class names for >pretty much everything. This is difficult for closure to minimize >completely. I’d really like to have some way to “export”

Re: [FlexJS] Maven generated site online

Hi Chris, I checking the generated site, and can't see nothing related to asjs. Could I expect to see the flexjs components API there? btw, in other thread I ask you for a simple pom. I can't make it work for a simple project and would need one simple example to start. One not living in examples

Re: Generics (was: Re: AW: [Falcon] Proposal for new ActionScript language feature: Optionally rename an import)

On 9/28/16, 8:37 AM, "Josh Tynjala" wrote: >For core classes like Number, Array, Boolean, etc. what looks like a cast >is actually a function call. There's a global function named Array, and >calling that takes precedence over casting. > >Personally, I think we should avoid breaking changes lik

Re: [2/4] git commit: [flex-sdk] [refs/heads/develop] - FLEX-35126 Added a unit test to reprouce the bug. Currently it passes, as expected. (But if I manually put back the fix for FLEX-34088, it fails

Mihai, The http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_test/ job keeps hanging on this new test. I have disabled the job. Please investigate and re-enable the job when things are working again. Thanks, -Alex On 9/19/16, 4:36 AM, "mih...@apache.org" wrote: >FLEX-35126 Added a unit t

AW: [FlexJS] Maven generated site online

Hi Carlos, the Flex/Actionscript part is currently missing from that because we don't have ASDoc working properly. If I extended the maven plugin to run asdoc for the framework part, we could start shipping that the same way the javadoc is shipped. That's also the reason I haven't started addi

AW: Generics (was: Re: AW: [Falcon] Proposal for new ActionScript language feature: Optionally rename an import)

That was initially the reasoning for me suggesting an as4 instead of extending as3. An alternative would be to control this with a compiler switch ... sort of like the quirks mode in the browsers (does that still exist?). I'm just thinking of all of these "Fun with JavaScript" in which you can

Re: Variable Renaming (was Re: [Falcon] Proposal for new ActionScript language feature: Optionally rename an import)

Alex, I had also considered the same idea of doing the qualifiedName splitting in the reflection data because I think you would reduce a lot of long string variation in the GCC release build simply by doing 'org.apache.flex.'+'Package.'+'ClassName' etc Isn't using the reflection member definition

Re: Variable Renaming (was Re: [Falcon] Proposal for new ActionScript language feature: Optionally rename an import)

"reflection support could be opt-in (or opt-out)" On reflection (pun unintended) maybe that is not sensible, given it is baked in to the framework classes. If GCC does dead-code elimination, maybe that does the job anyhow. On Thu, Sep 29, 2016 at 7:02 AM, Greg Dove wrote: > Alex, I had also

Re: Variable Renaming (was Re: [Falcon] Proposal for new ActionScript language feature: Optionally rename an import)

In fact, when I last touched it, Reflection was optional. Unless you actually use a reflection API (whose code path access FLEXJS_REFLECTION_INFO), GCC did not output FLEXJS_REFLECTION_INFO in the minified results. Probably worth verifying that is still true. What I don't know is whether dead co

Re: Variable Renaming (was Re: [Falcon] Proposal for new ActionScript language feature: Optionally rename an import)

I hadn't investigated any of this, just wondered about it I will check the reflection results today. I had actually assumed that @export and @expose explicitly prevented renaming, but also had not checked this. On Thu, Sep 29, 2016 at 7:13 AM, Alex Harui wrote: > In fact, when I last touched i

Re: Variable Renaming (was Re: [Falcon] Proposal for new ActionScript language feature: Optionally rename an import)

OT: I am getting a lot of warnings in the GCC release build phase. I recall you mentioning something in the past about this being related to GCC versions - is there anything I can do to address this? On Thu, Sep 29, 2016 at 7:19 AM, Greg Dove wrote: > I hadn't investigated any of this, just wo

Re: Variable Renaming (was Re: [Falcon] Proposal for new ActionScript language feature: Optionally rename an import)

On 9/28/16, 11:19 AM, "Greg Dove" wrote: >I hadn't investigated any of this, just wondered about it I will check the >reflection results today. >I had actually assumed that @export and @expose explicitly prevented >renaming, but also had not checked this. > Maybe I wasn't clear. @export and @

Re: AW: AW: [FlexJS] Problem with some test cases (@export was changed to @expose)?

Looked into it. It appears to be related to Greg's changes in 0bde1ec7a47341294280082331ce8b2c023d756f In MXMLFlexJSEmitter, the namesToAdd is including internal classes which it shouldn't. Probably the subDocuments list can be used to further filter what gets added to namesToAdd. Also, the ref

Re: Variable Renaming (was Re: [Falcon] Proposal for new ActionScript language feature: Optionally rename an import)

Thanks for clarifying. I see that you mentioned that originally now :) I think if GCC is smart enough to follow the indirection between those reflection field names and all possible uses of reflection it would be quite impressive. I don't think it works as is, because if it wasn't for some static f

Re: Variable Renaming (was Re: [Falcon] Proposal for new ActionScript language feature: Optionally rename an import)

On 9/28/16, 11:23 AM, "Greg Dove" wrote: >OT: I am getting a lot of warnings in the GCC release build phase. I >recall >you mentioning something in the past about this being related to GCC >versions - is there anything I can do to address this? Every once in a while, we have to upgrade to the

Re: AW: AW: [FlexJS] Problem with some test cases (@export was changed to @expose)?

I will look at this now. I had intended for relection to always be at the end, so that definitely sounds wrong. I did find the usedNames/postProcess sequence to be a possible candidate for refactor at some point, but was not keen to mess with this at the moment. I think I found that some usedNames

Re: Variable Renaming (was Re: [Falcon] Proposal for new ActionScript language feature: Optionally rename an import)

On 9/28/16, 11:36 AM, "Greg Dove" wrote: >Thanks for clarifying. I see that you mentioned that originally now :) >I think if GCC is smart enough to follow the indirection between those >reflection field names and all possible uses of reflection it would be >quite impressive. I don't think it wo

Re: [FlexJS][Maven] Simple pom with js output

Hi Chris, final y I get a BUILD SUCCESS :) But there's no target and no output :( Do you know what could be happen? This is the pom.xml (notice that the project only has one file in src folder called 'HelloWorld.mxml'): http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2

AW: [FlexJS][Maven] Simple pom with js output

Hi Carlos, remove the pluginManagment tags and make the plugins a direct child of build. http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; XML Schema instance namespace - w3.org www.w3.org $Date: 200

Re: [FlexJS][Maven] Simple pom with js output

Hi Chris, thanks, I try to remove that tag but now I get a failure :( [INFO] [INFO] Building My Own TestFlexJS 0.1.0-SNAPSHOT [INFO] [INFO] [INFO]

Re: [FlexJS] HTMLElementWrapper extending Sprite

On 9/28/16, 12:21 AM, "Harbs" wrote: >The overhead to swfs seem to me like it’s really minimal. There’s not a >lot of added code for using composition rather than inheritance. Well, at Adobe, we said "the overhead is minimal" so many times in Flex that UIComponent grew to 13,000 lines of code.

AW: [FlexJS][Maven] Simple pom with js output

In contrast to the usual setup using Ant where you simply always add all framework SWCs, with maven you only add the ones you use, so you need some of the Framework dependencies in you pom. Let me whip up the artifacts ... I think that will help a lot :-) Chris __

Re: AW: AW: [FlexJS] Problem with some test cases (@export was changed to @expose)?

I got this working quite quickly for the charts but also experienced issues with FlexJSStore bulding, which I have since addressed. I am just checking all examples - the ant build of all examples now completes, I just want to visually check them all - and then I will run a full set of tests before

Re: AW: AW: [FlexJS] Problem with some test cases (@export was changed to @expose)?

Hi Greg, The build failed for some strange reason. Might be a threading issue unrelated to your changes. I pulled everything and was able to build. I've restarted the CI build to see if the same error comes up again. I also ran "ant sdk.dependent.tests flexjs.dependent.tests" and there were a c

Re: AW: AW: [FlexJS] Problem with some test cases (@export was changed to @expose)?

oh. I thought I had this sorted, I can run the ant and maven builds locally, and all the examples were building for me. I will check again. On Thu, Sep 29, 2016 at 6:00 PM, Alex Harui wrote: > Hi Greg, > > The build failed for some strange reason. Might be a threading issue > unrelated to your

Re: AW: AW: [FlexJS] Problem with some test cases (@export was changed to @expose)?

btw I added an extra case to the if chain in the css code in a recent commit. It was to cover an rgba variation in DatabindingExample_Flat iirc. But I don't think it processes the alpha part of the rgba anywhere... I added todo: comments for this, but I am not sure how important it might be On T

Re: AW: AW: [FlexJS] Problem with some test cases (@export was changed to @expose)?

The Ant build doesn't run flexjs.dependent.tests automatically. You have to run ant with that target. It could be my setup, but I think those files I mentioned need to be updated for the new reflection data. Thanks, -Alex On 9/28/16, 10:03 PM, "Greg Dove" wrote: >oh. I thought I had this sort

Re: AW: AW: [FlexJS] Problem with some test cases (@export was changed to @expose)?

On 9/28/16, 10:05 PM, "Greg Dove" wrote: >btw I added an extra case to the if chain in the css code in a recent >commit. It was to cover an rgba variation in DatabindingExample_Flat iirc. >But I don't think it processes the alpha part of the rgba anywhere... I >added todo: comments for this, bu

Re: AW: AW: [FlexJS] Problem with some test cases (@export was changed to @expose)?

ok great, thanks. I have to step aside for an hour or so. I will check it after that On Thu, Sep 29, 2016 at 6:11 PM, Alex Harui wrote: > The Ant build doesn't run flexjs.dependent.tests automatically. You have > to run ant with that target. It could be my setup, but I think those > files I m

Re: AW: AW: [FlexJS] Problem with some test cases (@export was changed to @expose)?

On 9/28/16, 10:13 PM, "Greg Dove" wrote: >ok great, thanks. I have to step aside for an hour or so. I will check it >after that I don't think there's a big rush. This is an opportunity to share where some of the pieces are and how I deal with them. Thanks for sticking with it, -Alex

First time user

Hi Apologies for the naivety of this question but I have successfully installed the latest SDK (windows) and want to start using it in Flash builder 4.6. If I try to create a new project I get the message 'Flash builder 4 only supports Flex SDK 3.9 and higher. Can someone tell me what I am missin

AW: AW: AW: [FlexJS] Problem with some test cases (@export was changed to @expose)?

Ok ... thanks for fixing ... ASF Jenkins' Maven builds are back to blue ... a day always starts good with all successful jobs ;-) Chris Von: Alex Harui Gesendet: Donnerstag, 29. September 2016 07:18:44 An: dev@flex.apache.org Betreff: Re: AW: AW: [FlexJS] Probl

Two of my Flex talks got accepted for ApacheCon EU 2016 in Ceville

Hi guys, I just wanted to tell you that two of my talks got accepted for this years european ApacheCon Core. - Apache FlexJS' Maven migration initiative - introducing the flexjs-maven-plugin - Frontends for IoT Systems built with Apache Flex ... really happy about that :-) Chris