Re: [3/8] git commit: [flex-asjs] [refs/heads/feature/amf] - ClassAliasBead for registering class aliases for AMF

Hi Greg, Yeah, thanks for doing that. I'm just trying to get things to run in order to understand the pieces. I assume we'll end up using your cross-platform versions at some point. -Alex On 8/22/17, 9:09 PM, "Greg Dove" wrote: >Hi Alex, I see you are working on amf. >

Re: Re: [3/8] git commit: [flex-asjs] [refs/heads/feature/amf] - ClassAliasBead for registering class aliases for AMF

Bonjour, En congés jusqu'au 4 septembre, je prendrais connaissance de votre message à mon retour. Cordialement, Vincent/AFTER24

Re: [3/8] git commit: [flex-asjs] [refs/heads/feature/amf] - ClassAliasBead for registering class aliases for AMF

Hi Alex, I see you are working on amf. Not sure if you noticed already or not, but just in case I did add class alias support methods in the reflection package for both targets. I tested this to work the same for swf and js. (for multiple aliases etc). registerClassAlias getAliasByClass

Re: [Flex/FlexJS] External dependencies (Adobe, Google, ...)

Thanks Alex, that helps! -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Flex-FlexJS-External-dependencies-Adobe-Google-tp63945p63950.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [Flex/FlexJS] External dependencies (Adobe, Google, ...)

>What sort of commitment are you looking for? I was not sure about if there something is needed in the AIR source code to support Flex. But of course as you said it's all about AS3 and that should work... Thanks, Olaf -- View this message in context:

Re: [Flex/FlexJS] External dependencies (Adobe, Google, ...)

For JS output, there shouldn't be any dependencies for FlexJS on anything that isn't open source and with an Apache compatible license. I suppose someone could remove some of the third party files we use from the internet, but I think that's unlikely. FlexJS SWF output should work just fine on

Re: FlexJS Closure warnings

We don't do any rewriting right now, but we might be able to rewrite them in the future. One warning I see is from this code: /** * @export * @type {org.apache.flex.core.WrappedHTMLElement} */ positioner: { get: org.apache.flex.core.UIBase.prototype.get__positioner, set:

Re: [Flex/FlexJS] External dependencies (Adobe, Google, ...)

On 8/22/2017 10:54 AM, Olaf Krueger wrote: Hi, we have to do a decision in near future what we will do with our Flex apps. So I'd like to know if there are any external dependencies that could stop our Flex or FlexJS apps from working. Flex: Is there something needed to do at Adobes side to

[Flex/FlexJS] External dependencies (Adobe, Google, ...)

Hi, we have to do a decision in near future what we will do with our Flex apps. So I'd like to know if there are any external dependencies that could stop our Flex or FlexJS apps from working. Flex: Is there something needed to do at Adobes side to ensure that Flex apps will work with future AIR

Re: FlexJS Closure warnings

Alex, What do you mean by rewriting those getter/setters ? Could you point to an some example ? Thanks, Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-Closure-warnings-tp63939p63944.html Sent

Re: FlexJS Closure warnings

Some are from Closure Library. I haven't really looked into why. I don't think we are on the absolute latest, so we might need to move there. Others are from our code because we are now annotating the Object.defineProperties getter/setters with @type information, but we don't force the inclusion

Re: FlexJS Closure warnings

I did it for Maven as I remember [1], but it seems that we are missing it here [2]. - It doesn't have influence on warnings. - Could I miss some places ? As for the ant I think closure library has been downloaded from master without pointing any specific version, but I'm not sure - It has to be

Re: FlexJS Closure warnings

I remember seeing that Alex updated to a newer version of Closure compiler recently. I don't recall if he updated Closure library at the same time. As I understand it, it's a good idea to keep them both in sync. - Josh On Aug 22, 2017 3:43 AM, "Harbs" wrote: > I’ve been

Re: FlexJS Closure warnings

Hi Harbs, I can confirm that I have also a lot of warnings in Maven build. Even with simple project. Thanks, Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context:

FlexJS Closure warnings

I’ve been getting hundreds of warnings when FlexJS runs GCC. It’s kind of weird that the errors seem to be in the Google library files. FlexJSStore generates 119 warnings for me. My app generates over 300 warnings. Some of additional ones are in the typedef files. Harbs

Re: [FlexJS] ManualTests updates

The JS build seems to need -remove-circulars as well. > On Aug 22, 2017, at 2:56 AM, Greg Dove wrote: > > -FlexJSTest_HTML5 broken (swf build)

Re: [FlexJS] ManualTests updates

I partially fixed this, but it appears to be swf-only and is currently failing on the js build. Not sure what to do about that… > On Aug 22, 2017, at 2:56 AM, Greg Dove wrote: > > -FormatExample build completely broken

Re: [FlexJS] ManualTests updates

I just fixed some of the errors. There appear to be three remaining errors: 1. Missing labelFields property in IDataGridModel. I’m not sure whether it’s supposed to have this. 2. Missing removeAllElements() in IItemRendererParent 3. Missing index property in IItemRenderer. I’m not sure of the

Re: Re: [FlexJS] ManualTests updates

Bonjour, En congés jusqu'au 4 septembre, je prendrais connaissance de votre message à mon retour. Cordialement, Vincent/AFTER24

Re: [FlexJS] ManualTests updates

Thanks for working on this. > -TLFEditTestFlexJS result is broken in JS (I see missing dependencies - is > this is compiler problem?) It needed -remove-circulars. I just fixed that. > On Aug 22, 2017, at 2:56 AM, Greg Dove wrote: > > I just made some changes in manual