FlexSDK 4.16.0 installer errors

2017-03-16 Thread Justin Mclean
Hi,

Not sure what we can do about it but I’m seeing a higher than usual error rates 
with the installer in google analytics, especially on windows 

About 10% of all windows downloads are getting that 1000 error mention in the 
other thread , but we’re seeing a total error rate of about 60% for windows. On 
mac the total error rate is about 20%. (10-20% in the norm). For FlexJS the 
error rate is around 70% which is also a little higher than usual (it's 
normally in the 40-60% mark).

The windows errors more common that the 1000 one are the unknown  "info=Error” 
error and the 2032 error, which from memory is SSL related.

We're approaching 250 successful downloads which is some good news.

Thanks
Justin

Re: [FlexJS] Subflash, a clone of the Flash API for Flex JS, progress and questions

2017-03-16 Thread lizhi
https://cwiki.apache.org/confluence/display/FLEX/Using+CreateJS+with+FlexJS



-
spriteflexjs.com 
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Subflash-a-clone-of-the-Flash-API-for-Flex-JS-progress-and-questions-tp60395p60540.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.


Re: git commit: [flex-asjs] [refs/heads/develop] - Added MD5

2017-03-16 Thread Alex Harui
FWIW, we have a much faster MD5 in flex-utilities repo in ant_on_air.  And
that one we've released in the Installer.

-Alex

On 3/16/17, 5:53 PM, "Justin Mclean"  wrote:

>HI,
>
>Just out of interest where did that MD5 code come from? It looks very
>much like this [1]
>
>Thanks,
>Justin
>
>1. 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co
>m%2Fmikechambers%2Fas3corelib%2Fblob%2Fmaster%2Fsrc%2Fcom%2Fadobe%2Fcrypto
>%2FMD5.as=02%7C01%7C%7C3618d9c93eed4465a5a408d46cd06aaa%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636253089778311861=TA1OhAI4HDGiv5QX0
>Mdvldtn9Ee3ah7%2Bgrald6LWRr0%3D=0



Re: git commit: [flex-asjs] [refs/heads/develop] - Added MD5

2017-03-16 Thread Justin Mclean
HI,

Just out of interest where did that MD5 code come from? It looks very much like 
this [1]

Thanks,
Justin

1. 
https://github.com/mikechambers/as3corelib/blob/master/src/com/adobe/crypto/MD5.as

Re: AW: AW: [FlexJS] Dual branch

2017-03-16 Thread Alex Harui


On 3/16/17, 3:51 PM, "Christofer Dutz"  wrote:

>So typedefs produce only the js version? It should help make the Maven
>plugin simpler and the build easier to understand. So thumbs up for that.
>If I can help with the step in embedding the js in the "normal" one, just
>let me know.

IMO, typedefs swcs from flex-typedefs are different from the -js.swc.

In a -js.swc, the cross-compiled JS output is functional and goes in the
js/out folder in the swc package.
In a typedefs swc, the JS files are not always cross-compiled, and they go
in an externs folder in the swc package.  The js is not functional.  So I
left both a typedefs and js classifier around in the dual maven plugin.

Also, typedefs swcs go on the external-library-path while -js.swcs go on
the library-path.

Thoughts?
-Alex

>
>Chris
>
>
>
>Von meinem Samsung Galaxy Smartphone gesendet.
>
>
> Ursprüngliche Nachricht 
>Von: Alex Harui 
>Datum: 16.03.17 10:52 (GMT-05:00)
>An: dev@flex.apache.org
>Betreff: Re: AW: [FlexJS] Dual branch
>
>
>
>On 3/16/17, 4:52 AM, "Christofer Dutz"  wrote:
>
>>so i understand it correctly in the dual branch, the compiler produces
>>one swc per type? And if you do pure js you use the js-swcs and if flash,
>>you use the normal swcs?
>
>Yes.  That is correct.
>
>Thanks,
>-Alex
>



Re: Is it possible to upgrade to Gradle build ? Re: AIR 25 released

2017-03-16 Thread Carlos Rovira
Hi Gary,

at least for what I know, people here does not use to to work with Gradle.
Maybe Chris Dutz. I ear about it and wanted to try it , but finaly never
did. So IMHO if you want to build with gradle and know how to do it I
propose that you implement that build yourself and donate to the project in
order to have this done. If not I doubt someone else could bring it.

Thanks


2017-03-16 15:31 GMT+01:00 Gary Yang :

> I tried a few times digging into Flex build, did not prepare enough time
> and knowledge.
>
> I feel like it could be a lot easier if it could be built with Gradle, is
> it possible? how much effort could it be?
>
> -Gary
>
> On Thu, Mar 16, 2017 at 5:28 AM, hferreira  wrote:
>
> > Hello,
> >
> > AIR 25 is now released.
> > I would like to update to the lasted Flex 4.16 (thanks for provide that)
> > but
> > with AIR 25 directly from the installer.
> > Can you update the installer ?
> >
> > Regards,
> > Hugo.
> >
> >
> >
> > --
> > View this message in context: http://apache-flex-
> > development.247.n4.nabble.com/AIR-25-released-tp60504.html
> > Sent from the Apache Flex Development mailing list archive at Nabble.com.
> >
>



-- 

Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
http://www.avant2.es

Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.


AW: AW: [FlexJS] Dual branch

2017-03-16 Thread Christofer Dutz
So typedefs produce only the js version? It should help make the Maven plugin 
simpler and the build easier to understand. So thumbs up for that. If I can 
help with the step in embedding the js in the "normal" one, just let me know.

Chris



Von meinem Samsung Galaxy Smartphone gesendet.


 Ursprüngliche Nachricht 
Von: Alex Harui 
Datum: 16.03.17 10:52 (GMT-05:00)
An: dev@flex.apache.org
Betreff: Re: AW: [FlexJS] Dual branch



On 3/16/17, 4:52 AM, "Christofer Dutz"  wrote:

>so i understand it correctly in the dual branch, the compiler produces
>one swc per type? And if you do pure js you use the js-swcs and if flash,
>you use the normal swcs?

Yes.  That is correct.

Thanks,
-Alex



Re: AIR 25 released

2017-03-16 Thread hferreira
Tested on macOS.

Desktop project updated from Flex 4.15 + AIR 23 to Flex 4.16 + AIR 25.

Thank you very much.



--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/AIR-25-released-tp60504p60534.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.


AW: AW: [FlexJS] flex-asjs build failing

2017-03-16 Thread Christofer Dutz
Run the build with the "-X" flag to output more information and paste that 
please. Without it, Maven hides the exception.

Chris



Von meinem Samsung Galaxy Smartphone gesendet.


 Ursprüngliche Nachricht 
Von: yishayw 
Datum: 16.03.17 10:56 (GMT-05:00)
An: dev@flex.apache.org
Betreff: Re: AW: [FlexJS] flex-asjs build failing

Hi Chris,

The art is there so I guess the mavenizer is active. It looks like there's a
missing pom [1]?

[1] https://paste.apache.org/9gY2



--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-flex-asjs-build-failing-tp60461p60515.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.


AW: Is it possible to upgrade to Gradle build ? Re: AIR 25 released

2017-03-16 Thread Christofer Dutz
Well from my point of view gradle is the solution in half way in between ant 
and Maven. It should be easy to supply a gradle build in addition to ant and 
Maven, but we shouldn't relax the requirements on the build and give up on 
Maven.

Chris



Von meinem Samsung Galaxy Smartphone gesendet.


 Ursprüngliche Nachricht 
Von: Gary Yang 
Datum: 16.03.17 10:31 (GMT-05:00)
An: dev@flex.apache.org
Betreff: Is it possible to upgrade to Gradle build ? Re: AIR 25 released

I tried a few times digging into Flex build, did not prepare enough time
and knowledge.

I feel like it could be a lot easier if it could be built with Gradle, is
it possible? how much effort could it be?

-Gary

On Thu, Mar 16, 2017 at 5:28 AM, hferreira  wrote:

> Hello,
>
> AIR 25 is now released.
> I would like to update to the lasted Flex 4.16 (thanks for provide that)
> but
> with AIR 25 directly from the installer.
> Can you update the installer ?
>
> Regards,
> Hugo.
>
>
>
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/AIR-25-released-tp60504.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>


Re: 4.16.0 Install issues (was Re: [ANNOUNCE] Apache Flex 4.16.0 released)

2017-03-16 Thread OmPrakash Muppirala
You can use
FP/AIR 23 and older then use one of the upgrade scripts.


+1 for this approach.

I think we should add these steps to a wiki page and keep it handy for
folks who want this.

In fact,  simply copying over a different AIR SDK should work as well.

Thanks,
Om


Re: 4.16.0 Install issues (was Re: [ANNOUNCE] Apache Flex 4.16.0 released)

2017-03-16 Thread Alex Harui


On 3/16/17, 12:25 PM, "Nicholas Kwiatkowski"
 wrote:

>I think there is some reason to use very old versions of AIR ( < 4), but
>between AIR 4 and 23 it should be ok.   Do you know if it effects the old
>ones (which still support some older OSs)?

Probably.  The issue is the installer script tries to see AIR SDK is a
tbz2 or dmg file.  The Installer uses ant_on_air which uses Ant 1.7 logic
and it fails to detect tbz2 and always tries the dmg route.  That's why
actually using Ant 1.9 works.

So, AFAICT, the situation is that the Installer can install 4.16.0 with
FP/AIR 24 and newer, and 4.15.0 and earlier with FP/AIR 23 and older.
4.16.0 with FP/AIR 23 and older can be installed via Ant 1.9 or newer, and
4.15.0 with FP/AIR 24 and newer cannot be installed at all.  You can use
FP/AIR 23 and older then use one of the upgrade scripts.

-Alex



Re: [FlexJS] Dual branch

2017-03-16 Thread Harbs

> On Mar 16, 2017, at 6:54 PM, Alex Harui  wrote:
> 
> 
> 
> On 3/16/17, 9:41 AM, "Harbs"  wrote:
> 
>> So, as soon as you merge in dual, all the $displayObject references and
>> all will be gone. Correct?
> 
> I actually haven't done that yet ($displayObject points to itself), but I
> guess I should go and do that.

It might be safer to do that later?

>> 
>> Sounds scary.
>> 
>> I’d like to test my app on the dual branch before you do the merge. I
>> can’t afford a week of non-productivity right now.
>> 
>> Can you wait until Sunday or Monday to merge to give me time to test?
> 
> The merge won't happen for several days.  I have to get through your
> goog.require problem first, then I expect tons of conflicts.

I’m glad to hear that. :-)

Harbs



Re: 4.16.0 Install issues (was Re: [ANNOUNCE] Apache Flex 4.16.0 released)

2017-03-16 Thread Nicholas Kwiatkowski
I think there is some reason to use very old versions of AIR ( < 4), but
between AIR 4 and 23 it should be ok.   Do you know if it effects the old
ones (which still support some older OSs)?

-Nick

On Thu, Mar 16, 2017 at 2:54 PM, Alex Harui  wrote:

> Adding dev@...
>
> I just noticed that there is a bug in the installer.xml and the Installer
> will not install 4.16.0 on Mac with FP/AIR 23 and older.  It will only
> work with FP/AIR 24 and newer.  I haven't tried Windows, but it should be
> ok.
>
> I am hopeful very few people will want to install 4.16 with FP/AIR 23 and
> older on Mac.  Does anybody disagree?  Otherwise I will make FP/AIR 24 the
> default.  Folks who have to have 4.16 with FP/AIR 23 and older can use a
> recent version of Ant and install via Ant.
>
> Thoughts?
> -Alex
>
> On 3/16/17, 10:48 AM, "Alex Harui"  wrote:
>
> >
> >
> >On 3/16/17, 10:20 AM, "pol2095"  wrote:
> >
> >>When I choose Air 25, Air 24 is downloaded ?
> >>
> >
> >Good catch.  I mis-typed something.  Please try again.
> >
> >-Alex
> >
>
>


4.16.0 Install issues (was Re: [ANNOUNCE] Apache Flex 4.16.0 released)

2017-03-16 Thread Alex Harui
Adding dev@...

I just noticed that there is a bug in the installer.xml and the Installer
will not install 4.16.0 on Mac with FP/AIR 23 and older.  It will only
work with FP/AIR 24 and newer.  I haven't tried Windows, but it should be
ok.

I am hopeful very few people will want to install 4.16 with FP/AIR 23 and
older on Mac.  Does anybody disagree?  Otherwise I will make FP/AIR 24 the
default.  Folks who have to have 4.16 with FP/AIR 23 and older can use a
recent version of Ant and install via Ant.

Thoughts?
-Alex

On 3/16/17, 10:48 AM, "Alex Harui"  wrote:

>
>
>On 3/16/17, 10:20 AM, "pol2095"  wrote:
>
>>When I choose Air 25, Air 24 is downloaded ?
>>
>
>Good catch.  I mis-typed something.  Please try again.
>
>-Alex
>



Re: About legacy IDEs (Re: AW: [FALCONJX] Combining SWF and JS compilers)

2017-03-16 Thread Alex Harui
BTW, if you do upgrade FB to run on Java 7/8, you may also need to edit
the .ini file and add:

-Djava.util.Arrays.useLegacyMergeSort=true

Otherwise the regular Flex SDK compiler may start throwing errors.

HTH,
-Alex

On 2/7/17, 6:28 PM, "Alex Harui"  wrote:

>
>
>On 2/7/17, 6:17 PM, "Justin Mclean"  wrote:
>
>>Hi,
>>
>>For me re IDEs:
>>- FlexJS does work on FlashBuilder 4.6.
>
>This may apply to FlexJS as well as Apache Flex:
>http://mail-archives.apache.org/mod_mbox/flex-users/201308.mbox/%3cCE31514
>9
>.fe43%25aha...@adobe.com%3e
>
>>- FlashBuilder 4.7 doesn’t work on recent version of OSX for many people.
>
>Have you tried this?  Seemed to work for me.
>http://blogs.adobe.com/flashplayer/2016/09/running-adobe-flash-builder-on-
>m
>ac-with-java-78.html
>
>
>>- Moonshine while off to a good start is missing a few features like code
>>completion, git integration and maven support.
>>- IntelliJ is difficult to set up and may produce different results to
>>other build methods. This is probably fixable. FlexJS maven support is a
>>little broken however.
>>- FDT only supports older version of FLexJS?
>>- Visual Studio could be an option [1] but not looked into it.
>
>FlashDevelop is yet another IDE?
>
>



Re: [FlexJS] Dual branch

2017-03-16 Thread Carlos Rovira
Ok Alex, thanks for clearing it

2017-03-16 18:49 GMT+01:00 Alex Harui :

>
>
> On 3/16/17, 10:38 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
> 
> wrote:
>
> >So, in order to understand what I'm missing, "Basic" will be in the
> >diagram
> >I did in place of "FlexJS"?
> >
> >In Core be should have things like UIBase, UIButtonBase, Container...
> >since
> >HTML (Div, H1, P...) will need it.
> >
> >Then in Basic we should have FlexJS set (i.e: js:Button, js:TextInput,
> >js:CheckBox...) and Express will depend on Basic.
> >
> >At least that is the way I see it...
> >
>
> Yes, will get there, but maybe after the merge.
>
> -Alex
>
>


-- 

Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
http://www.avant2.es

Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.


Re: [FlexJS] Datagrid?

2017-03-16 Thread Peter Ent
I just saw this - sorry for the delay.

I'm working on changing the structure of the container classes which also
affects list and therefore DataGrid. Once I have things stable and checked
in I'll look at the bugs and see if they are resolved and if not, start
addressing them.

Regards,
Peter Ent
Adobe Systems/Apache Flex Project

On 3/14/17, 4:19 PM, "piotrz"  wrote:

>Hi Harbs,
>
>Great that you are touching it! There are couple of jiras related to
>DataGrid. If you won't see some of those  issues let us know.
>
>https://issues.apache.org/jira/browse/FLEX-34241
>https://issues.apache.org/jira/browse/FLEX-34240
>https://issues.apache.org/jira/browse/FLEX-34998
>https://issues.apache.org/jira/browse/FLEX-35222
>
>Thanks,
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/FlexJS-Datagrid-tp604
>06p60411.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.



Re: [FlexJS] Dual branch

2017-03-16 Thread Alex Harui


On 3/16/17, 10:38 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>So, in order to understand what I'm missing, "Basic" will be in the
>diagram
>I did in place of "FlexJS"?
>
>In Core be should have things like UIBase, UIButtonBase, Container...
>since
>HTML (Div, H1, P...) will need it.
>
>Then in Basic we should have FlexJS set (i.e: js:Button, js:TextInput,
>js:CheckBox...) and Express will depend on Basic.
>
>At least that is the way I see it...
>

Yes, will get there, but maybe after the merge.

-Alex



Re: [FlexJS] Dual branch

2017-03-16 Thread Carlos Rovira
So, in order to understand what I'm missing, "Basic" will be in the diagram
I did in place of "FlexJS"?

In Core be should have things like UIBase, UIButtonBase, Container... since
HTML (Div, H1, P...) will need it.

Then in Basic we should have FlexJS set (i.e: js:Button, js:TextInput,
js:CheckBox...) and Express will depend on Basic.

At least that is the way I see it...




2017-03-16 18:00 GMT+01:00 Alex Harui :

>
>
> On 3/16/17, 9:44 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>  wrote:
>
> >Hi Alex,
> >
> >2017-03-16 15:54 GMT+01:00 Alex Harui :
> >
> >>
> >> The components in the HTML project that are not direct wrappers (like A,
> >> Div, H1, etc) now live in the Basic folder.  HTML will just contain
> >>these
> >> direct wrappers.
> >>
> >
> >it's strange for me that refactor. I proposed just some time ago that HTML
> >should have all tags that are html (Div, A, P, H1,...) and nothing more,
> >HTML should depend on Core, then we should have CreateJS, MDL,...and
> >FlexJS
> >set (Express). This latest one should be where we'll concentrate efforts.
> >
> >Core --- HTML. - CreateJS
> > -- MDL
> > -- FlexJS (Buttom, TextInput, Container...)
> > ThemeX
> >
> > -ThemeY
> >
> >In this way we could avoid CSS defaults in the rest of non-flexjs
> >implementations that right now affects that efforts. As well HTML should
> >not impose any defaults (position relative or things like that hard coded
> >in classes)
> >
> >Makes this sense?
>
> I think I'm doing what you wanted.  If not, I think it is a step closer
> and we can make more changes after the merge, such as moving UIBase back
> to Core.  Currently in "develop" both HTML and Basic have a different
> version of UIBase.
>
> Regarding CSS defaults, after the merge we can see if other refactoring is
> needed so that MDL doesn't have dependencies on Basic.
>
> Thanks,
> -Alex
>
>


-- 

Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
http://www.avant2.es

Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.


Re: [FlexJS] Dual branch

2017-03-16 Thread Alex Harui


On 3/16/17, 9:44 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>Hi Alex,
>
>2017-03-16 15:54 GMT+01:00 Alex Harui :
>
>>
>> The components in the HTML project that are not direct wrappers (like A,
>> Div, H1, etc) now live in the Basic folder.  HTML will just contain
>>these
>> direct wrappers.
>>
>
>it's strange for me that refactor. I proposed just some time ago that HTML
>should have all tags that are html (Div, A, P, H1,...) and nothing more,
>HTML should depend on Core, then we should have CreateJS, MDL,...and
>FlexJS
>set (Express). This latest one should be where we'll concentrate efforts.
>
>Core --- HTML. - CreateJS
> -- MDL
> -- FlexJS (Buttom, TextInput, Container...)
> ThemeX
>
> -ThemeY
>
>In this way we could avoid CSS defaults in the rest of non-flexjs
>implementations that right now affects that efforts. As well HTML should
>not impose any defaults (position relative or things like that hard coded
>in classes)
>
>Makes this sense?

I think I'm doing what you wanted.  If not, I think it is a step closer
and we can make more changes after the merge, such as moving UIBase back
to Core.  Currently in "develop" both HTML and Basic have a different
version of UIBase.

Regarding CSS defaults, after the merge we can see if other refactoring is
needed so that MDL doesn't have dependencies on Basic.

Thanks,
-Alex



Re: [FlexJS] Dual branch

2017-03-16 Thread Alex Harui


On 3/16/17, 9:41 AM, "Harbs"  wrote:

>So, as soon as you merge in dual, all the $displayObject references and
>all will be gone. Correct?

I actually haven't done that yet ($displayObject points to itself), but I
guess I should go and do that.

>
>Sounds scary.
>
>I’d like to test my app on the dual branch before you do the merge. I
>can’t afford a week of non-productivity right now.
>
>Can you wait until Sunday or Monday to merge to give me time to test?

The merge won't happen for several days.  I have to get through your
goog.require problem first, then I expect tons of conflicts.

Thanks,
-Alex



Re: [FlexJS] Dual branch

2017-03-16 Thread Carlos Rovira
Hi Alex,

2017-03-16 15:54 GMT+01:00 Alex Harui :

>
> The components in the HTML project that are not direct wrappers (like A,
> Div, H1, etc) now live in the Basic folder.  HTML will just contain these
> direct wrappers.
>

it's strange for me that refactor. I proposed just some time ago that HTML
should have all tags that are html (Div, A, P, H1,...) and nothing more,
HTML should depend on Core, then we should have CreateJS, MDL,...and FlexJS
set (Express). This latest one should be where we'll concentrate efforts.

Core --- HTML. - CreateJS
 -- MDL
 -- FlexJS (Buttom, TextInput, Container...)
 ThemeX

 -ThemeY

In this way we could avoid CSS defaults in the rest of non-flexjs
implementations that right now affects that efforts. As well HTML should
not impose any defaults (position relative or things like that hard coded
in classes)

Makes this sense?

thanks



-- 
Carlos Rovira
http://about.me/carlosrovira


Re: [FlexJS] Dual branch

2017-03-16 Thread Harbs
So, as soon as you merge in dual, all the $displayObject references and all 
will be gone. Correct?

Sounds scary.

I’d like to test my app on the dual branch before you do the merge. I can’t 
afford a week of non-productivity right now.

Can you wait until Sunday or Monday to merge to give me time to test?

Harbs

> On Mar 16, 2017, at 4:54 PM, Alex Harui  wrote:
> 
> 
> 
> On 3/16/17, 12:37 AM, "Harbs"  wrote:
> 
>> I have not had the time.
>> 
>> Is there anything to be aware of when you merge it in from an application
>> development stand-point?
> 
> I was sort of wondering if it would compile a big app and produce a valid
> SWF and whether it would miss errors or report false-positives.
> 
>> 
>> Have you done anything regarding the Basic vs. HTML projects?
> 
> The components in the HTML project that are not direct wrappers (like A,
> Div, H1, etc) now live in the Basic folder.  HTML will just contain these
> direct wrappers.
> 
> Thanks,
> -Alex
> 



Re: AIR 25 released

2017-03-16 Thread Alex Harui
I think I've added it.  Please try and let us know.

Thanks,
-Alex

On 3/16/17, 2:28 AM, "hferreira"  wrote:

>Hello,
>
>AIR 25 is now released.
>I would like to update to the lasted Flex 4.16 (thanks for provide that)
>but
>with AIR 25 directly from the installer.
>Can you update the installer ?
>
>Regards,
>Hugo.
>
>
>
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/AIR-25-released-tp605
>04.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.



Re: Just need to vent...

2017-03-16 Thread Alex Harui


On 3/16/17, 12:35 AM, "Harbs"  wrote:

>I think that’s a good plan.
>
>Here’s what (I think) should solve the problem:
>
>1. The compiler goes through the require chain once and build a list of
>all inheritance chains.
>2. It also builds a list of requires that either have no inheritance, or
>are at the end of an inheritance chain.
>3. It removes all requires with the exception of inherited ones, and
>places the entire list of requires from #2 in the main app class.
>4. The order of the addDependencies should then not matter with the
>exception of inheritance chains where the bases need to be at the bottom
>of the list.
>
>The only thing this does not address (unless I’m missing the boat), is
>static vars and consts. That’s a problem which is I believe is unsolvable
>anyway.

I thought about doing something like that.  Then I stared wondering if the
goog.require system was intended to support lazy or just-in-time loading.
I guess there is no way to interrupt the resolution of goog.requires once
it starts?

BTW, for those who like these kinds of logic puzzles, the puzzle is to
present the three files in an order where the base class is before the sub
class but the goog.requires do not result in a circularity.  AFAICT, there
is no way to remove one or more goog.requires and pick an order that
satisfies these requirements.

-Alex



Re: AW: [FlexJS] flex-asjs build failing

2017-03-16 Thread yishayw
Hi Chris,

The art is there so I guess the mavenizer is active. It looks like there's a
missing pom [1]?

[1] https://paste.apache.org/9gY2



--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-flex-asjs-build-failing-tp60461p60515.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.


Re: [FlexJS] Dual branch

2017-03-16 Thread Alex Harui


On 3/16/17, 12:37 AM, "Harbs"  wrote:

>I have not had the time.
>
>Is there anything to be aware of when you merge it in from an application
>development stand-point?

I was sort of wondering if it would compile a big app and produce a valid
SWF and whether it would miss errors or report false-positives.

>
>Have you done anything regarding the Basic vs. HTML projects?

The components in the HTML project that are not direct wrappers (like A,
Div, H1, etc) now live in the Basic folder.  HTML will just contain these
direct wrappers.

Thanks,
-Alex



Re: AW: [FlexJS] Dual branch

2017-03-16 Thread Alex Harui


On 3/16/17, 4:52 AM, "Christofer Dutz"  wrote:

>so i understand it correctly in the dual branch, the compiler produces
>one swc per type? And if you do pure js you use the js-swcs and if flash,
>you use the normal swcs?

Yes.  That is correct.

Thanks,
-Alex



Is it possible to upgrade to Gradle build ? Re: AIR 25 released

2017-03-16 Thread Gary Yang
I tried a few times digging into Flex build, did not prepare enough time
and knowledge.

I feel like it could be a lot easier if it could be built with Gradle, is
it possible? how much effort could it be?

-Gary

On Thu, Mar 16, 2017 at 5:28 AM, hferreira  wrote:

> Hello,
>
> AIR 25 is now released.
> I would like to update to the lasted Flex 4.16 (thanks for provide that)
> but
> with AIR 25 directly from the installer.
> Can you update the installer ?
>
> Regards,
> Hugo.
>
>
>
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/AIR-25-released-tp60504.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>


Re: [2/2] git commit: [flex-asjs] [refs/heads/develop] - Initial commit of Text

2017-03-16 Thread Harbs
FYI:

The ant build of Text should work. (Although it’s not yet functional.) I have 
not added this to the general build and I don’t know how to set up the maven 
build. I will need help with that.

The TLF project should land later today. (which will have build problems)

I realized after I committed this that I should have created a TLF branch. I 
will do so before my next commit.

Harbs

> On Mar 16, 2017, at 2:23 PM, ha...@apache.org wrote:
> 
> Initial commit of Text
> 
> 
> Project: http://git-wip-us.apache.org/repos/asf/flex-asjs/repo
> Commit: http://git-wip-us.apache.org/repos/asf/flex-asjs/commit/a77bfe4f
> Tree: http://git-wip-us.apache.org/repos/asf/flex-asjs/tree/a77bfe4f
> Diff: http://git-wip-us.apache.org/repos/asf/flex-asjs/diff/a77bfe4f
> 
> Branch: refs/heads/develop
> Commit: a77bfe4f23402162ab471e1923b33c127e6b1a98
> Parents: 2695a91
> Author: Harbs 
> Authored: Thu Mar 16 14:23:05 2017 +0200
> Committer: Harbs 
> Committed: Thu Mar 16 14:23:05 2017 +0200
> 



AW: FlexJS / Jenkins on Unix

2017-03-16 Thread Christofer Dutz
Hi Justin,

Well haven't changed anything since Tuesday ... Haven't got IntelliJ on my 
phone ... Yet ;-)

But happy it's working.

Chris



Von meinem Samsung Galaxy Smartphone gesendet.


 Ursprüngliche Nachricht 
Von: Justin Mclean 
Datum: 16.03.17 02:25 (GMT-05:00)
An: dev@flex.apache.org
Betreff: Re: FlexJS / Jenkins on Unix

Hi,

Was just taking a look at this again and it’s now working.

Not 100% sure what has changed but a GitHub change triggered the CI server 
which got the latest FlexJS 0.8 snapshots and the application compiled to 
completion, and build past that have also worked. If you changed something 
Chris - thanks!

So it is possible to have your FlexJS applications compiled on a Jenkins CI 
server on Linux.

Thanks,
Justin


Re: [FlexJS] Container work status

2017-03-16 Thread Peter Ent
Thanks for letting me know. I will try to be quick.

‹peter

On 3/16/17, 4:11 AM, "Justin Mclean"  wrote:

>Hi,
>
>The current changes have broken the layout in our application (not
>unexpected). When you feel it at a stable state just say so and we set if
>we can fix it up and report back any issues.
>
>Thanks,
>Justin



Re: [MDL Dialogs] was: Re: [FlexJS] MDL - Dynamic Child Problem

2017-03-16 Thread Carlos Rovira
Hi Piotr,

sorry, just see this, but as you said I'm very busy this days and even
can't take the time to look to all the threads going on.
I can't analyze right now the changes you want to do, but I trust you and
I'm sure what you plan will be the right way to go.
Hope I can return in some days as I get all the overload controlled.

Thanks and sorry to get late!

Carlos



2017-03-16 12:24 GMT+01:00 sankar :

> piotrz wrote
> > I'm thinking on adding as "default" to components ability for dynamic
> > creation without any "isDynamic" property etc. I wanted to discuss it
> with
> > Carlos in the other thread, but he is busy currently, so I'm still
> waiting
> > for his input.
>
> Hi Piotr,
>
> That sounds nice. Although I don't know if there'll be any stress to
> processing, which Carlos and others can suggest. But I'm fine with this
> solution and I haven't seen any noticeable delay/stress to my browser even
> when I give quite heavy application codes.
>
> I'm using following codes in my modified UIBase class at this moment, and
> this working expecedly.
>
>
> > public function addElement(c:IChild, dispatchEvent:Boolean = true):void
> > {
> >  ...
> >  COMPILE::JS
> >  {
> >   if ("componentHandler" in document.defaultView)
> >   {
> >   var componentHandler:Object = window["componentHandler"];
> >   componentHandler["upgradeElement"](c.positioner);
> >   }
> >   element.appendChild(c.positioner);
> >   (c as IUIBase).addedToParent();
> >  }
> > }
>
> Thanks!
>
>
>
>
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/FlexJS-MDL-Dynamic-Child-
> Problem-tp59595p60506.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>



-- 

Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
http://www.avant2.es

Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.


AW: [FlexJS] Dual branch

2017-03-16 Thread Christofer Dutz
so i understand it correctly in the dual branch, the compiler produces one swc 
per type? And if you do pure js you use the js-swcs and if flash, you use the 
normal swcs?

Chris



Von meinem Samsung Galaxy Smartphone gesendet.


 Ursprüngliche Nachricht 
Von: Alex Harui 
Datum: 15.03.17 21:01 (GMT-05:00)
An: dev@flex.apache.org
Betreff: Re: [FlexJS] Dual branch

Has anyone else looked at the dual branch?  If you want to know more about
it before it gets merged let me know soon, otherwise I am going to merge
it.

Thanks,
-Alex

On 3/11/17, 10:49 PM, "Alex Harui"  wrote:

>
>
>On 3/11/17, 10:34 AM, "Christofer Dutz"  wrote:
>
>>Hi Alex,
>>
>>I just had a look and the changes look valid. The only thing I think I
>>should change, is that it seems as if prior to your change, I needed two
>>compilations AS & JS and therefore there were two Mojos: CompileASMojo
>>and CompileJSMojo. I think now we need only one. If the current state it
>>also looks as if both the AS and the JS mojo would do a dual compilation.
>>
>>If you confirm, that now I need only one Mojo, I would refactor it and
>>create a “CompileLibMojo” and remove the other two CompileASMojo and
>>CompileJSMojo.
>
>Well, we still build two SWCs per project.  We might want to rename the
>Mojos, but the CompileASMojo builds a SWC that has a library.swf with
>COMPILE::SWF=true but includes JS files compiled with COMPILE::JS=true,
>then CompileJSMojo builds a SWC that has a library.swf with
>COMPILE::JS=true and the JS files with COMPILE::JS=true and the artifact
>has the -js classifier.
>
>At some point we can try combining the two and renaming one of the
>library.swf and catalog.xml files, but for now we still need a SWC with
>library.swf with COMPILE::SWF=true and a SWC with library.swf with
>COMPILE::JS=true.
>
>Thanks,
>-Alex
>



Re: [MDL Dialogs] was: Re: [FlexJS] MDL - Dynamic Child Problem

2017-03-16 Thread sankar
piotrz wrote
> I'm thinking on adding as "default" to components ability for dynamic
> creation without any "isDynamic" property etc. I wanted to discuss it with
> Carlos in the other thread, but he is busy currently, so I'm still waiting
> for his input.

Hi Piotr,

That sounds nice. Although I don't know if there'll be any stress to
processing, which Carlos and others can suggest. But I'm fine with this
solution and I haven't seen any noticeable delay/stress to my browser even
when I give quite heavy application codes. 

I'm using following codes in my modified UIBase class at this moment, and
this working expecedly.


> public function addElement(c:IChild, dispatchEvent:Boolean = true):void
> {
>  ...
>  COMPILE::JS
>  {
>   if ("componentHandler" in document.defaultView)
>   {
>   var componentHandler:Object = window["componentHandler"];
>   componentHandler["upgradeElement"](c.positioner);
>   }
>   element.appendChild(c.positioner);
>   (c as IUIBase).addedToParent();
>  }
> }

Thanks!




--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Dynamic-Child-Problem-tp59595p60506.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.


AIR 25 released

2017-03-16 Thread hferreira
Hello,

AIR 25 is now released.
I would like to update to the lasted Flex 4.16 (thanks for provide that) but
with AIR 25 directly from the installer.
Can you update the installer ?

Regards,
Hugo.



--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/AIR-25-released-tp60504.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.


Re: Build failed in Jenkins: flex-sdk #1453

2017-03-16 Thread Mihai Chira
I'm just taking a look at this

On 15 March 2017 at 11:56,   wrote:
> See 
>
> --
> [...truncated 2049 lines...]
> main:
>  [echo] Compiling frameworks/locale/en_US/automation_rb.swc
> [compc] Loading configuration file 
> C:\Jenkins\workspace\flex-sdk\frameworks\projects\automation\bundle-config.xml
> [compc] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
> [compc] 
> C:\Jenkins\workspace\flex-sdk\frameworks\locale\en_US\automation_rb.swc (2132 
> bytes)
>
> tool_air:
>
> bundles-clean:
>  [echo] IN bundles clean
>
> tool_air_bundles-clean:
>
> tool_air_bundles-clean:
>
> tool_air_bundles-clean:
>
> tool_air_bundles-clean:
>
> tool_air_bundles-clean:
>
> tool_air_bundles-clean:
>
> tool_air_bundles-clean:
>
> tool_air_bundles-clean:
>
> tool_air_bundles-clean:
>
> tool_air_bundles-clean:
>
> tool_air_bundles-clean:
>
> tool_air_bundles-clean:
>
> tool_air_bundles-clean:
>
> tool_air_bundles-clean:
>
> tool_air_bundles-clean:
>
> tool_air_bundles-clean:
>
> tool_air_bundles-clean:
>
> tool_air_bundles-clean:
>
> clean:
>
> compile:
>  [echo] Compiling tool_air.swc
>  [echo] Using c:\Adobe\AIRSDK40/frameworks/libs/air/airglobal.swc
> [compc] Loading configuration file 
> C:\Jenkins\workspace\flex-sdk\frameworks\projects\tool_air\compile-config.xml
> [compc] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
> [compc] 
> C:\Jenkins\workspace\flex-sdk\frameworks\libs\automation\tool_air.swc (67238 
> bytes)
>
> main:
>
> automation_spark:
>
> clean:
>
> compile:
>  [echo] Compiling frameworks/libs/automation/automation_spark.swc
> [compc] Loading configuration file 
> C:\Jenkins\workspace\flex-sdk\frameworks\projects\automation_spark\compile-config.xml
> [compc] 
> C:\Jenkins\workspace\flex-sdk\frameworks\libs\automation\automation_spark.swc 
> (87001 bytes)
> [compc] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
>
> main:
>
> automation_flashflexkit:
>
> clean:
>
> compile:
>  [echo] Compiling frameworks/libs/automation/automation_flashflexkit.swc
> [compc] Loading configuration file 
> C:\Jenkins\workspace\flex-sdk\frameworks\projects\automation_flashflexkit\compile-config.xml
> [compc] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
> [compc] 
> C:\Jenkins\workspace\flex-sdk\frameworks\libs\automation\automation_flashflexkit.swc
>  (7331 bytes)
>
> main:
>
> automation_air:
>
> clean:
>
> compile:
>  [echo] Compiling frameworks/libs/automation/automation_air.swc
> [compc] Loading configuration file 
> C:\Jenkins\workspace\flex-sdk\frameworks\projects\automation_air\compile-config.xml
> [compc] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
> [compc] 
> C:\Jenkins\workspace\flex-sdk\frameworks\libs\automation\automation_air.swc 
> (16016 bytes)
>
> main:
>
> automation_airspark:
>
> clean:
>
> compile:
>  [echo] Compiling frameworks/libs/automation/automation_airspark.swc
>  [echo] Using c:\Adobe\AIRSDK40/frameworks/libs/air/airglobal.swc
> [compc] Loading configuration file 
> C:\Jenkins\workspace\flex-sdk\frameworks\projects\automation_airspark\compile-config.xml
> [compc] 
> C:\Jenkins\workspace\flex-sdk\frameworks\libs\automation\automation_airspark.swc
>  (4534 bytes)
> [compc] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
>
> main:
>
> flatspark:
>
> clean:
>
> compile:
>  [echo] Compiling frameworks/libs/flatspark.swc
> [compc] Loading configuration file 
> C:\Jenkins\workspace\flex-sdk\frameworks\projects\flatspark\compile-config.xml
> [compc] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
> [compc] C:\Jenkins\workspace\flex-sdk\frameworks\libs\flatspark.swc 
> (479358 bytes)
>
> main:
>
> javascript:
>
> clean:
>
> compile-swfs:
>  [echo] Compiling 
> 
> [mxmlc] Loading configuration file 
> C:\Jenkins\workspace\flex-sdk\frameworks\flex-config.xml
> [mxmlc] 
> C:\Jenkins\workspace\flex-sdk\frameworks\javascript\FABridge\samples\EmptySwf.swf
>  (5753 bytes)
> [mxmlc] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
>  [echo] Compiling 
> 
> [mxmlc] Loading configuration file 
> C:\Jenkins\workspace\flex-sdk\frameworks\flex-config.xml
> [mxmlc] 
> C:\Jenkins\workspace\flex-sdk\frameworks\javascript\FABridge\samples\app.swf 
> (517080 bytes)
> [mxmlc] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
>
> samples:
>
> main:
>
> main:
>
> ide:
>
> create-config-files:
>  [copy] Copying 3 files to 
> 
>
> expand-config-tokens:
>  [echo] expanding {airHome} and {playerglobalHome} tokens
>
> main:
>
> 

Re: [ANNOUNCE] Apache Flex 4.16.0 released

2017-03-16 Thread bschleicher
Hi!

I  had problems with the subscribtion of the mailing list. Sorry if this
message is now a cross-posting.

Thanks for the release of the Flex SDK 4.16.0

On the same day of the Flex SDK release, Adobe has released AIR SDK 25.0. It
would be nice if somone will update the installer to support the release
version of AIR SDK 25.

https://helpx.adobe.com/flash-player/release-note/fp_25_air_25_release_notes.html

Regards,
Bernhard Schleicher



--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/ANNOUNCE-Apache-Flex-4-16-0-released-tp60427p60503.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.


Home for FlexJS TLF

2017-03-16 Thread Harbs
I will likely be donating the TLF code migrated to FlexJS soon.

First of all, I’d like to set expectations:
1. It will be non-functional at first.
2. Even when it will be functional, it will require a text engine to drive. I’m 
trying to put together a basic text engine, but it will be very basic.
3. Even once TLF is functional, it will probably not support all the features 
without a more advanced engine that I’m probably not donating.

My question is where to put it. The original TLF had its own repo — I believe 
because it did not rely on Flex. My TLF port WILL rely on Core of FlexJS. I’m 
thinking that TLF can simply be its own project within flex-asjs. I would 
create two new projects: Text (for the engine), and TLF.

Any objections? Thoughts? Other suggestions?

Thanks,
Harbs

Re: [FlexJS] Container work status

2017-03-16 Thread Justin Mclean
Hi,

The current changes have broken the layout in our application (not unexpected). 
When you feel it at a stable state just say so and we set if we can fix it up 
and report back any issues.

Thanks,
Justin

Re: Just need to vent...

2017-03-16 Thread Harbs
I think that’s a good plan.

Here’s what (I think) should solve the problem:

1. The compiler goes through the require chain once and build a list of all 
inheritance chains.
2. It also builds a list of requires that either have no inheritance, or are at 
the end of an inheritance chain.
3. It removes all requires with the exception of inherited ones, and places the 
entire list of requires from #2 in the main app class.
4. The order of the addDependencies should then not matter with the exception 
of inheritance chains where the bases need to be at the bottom of the list.

The only thing this does not address (unless I’m missing the boat), is static 
vars and consts. That’s a problem which is I believe is unsolvable anyway.

Harbs

> On Mar 16, 2017, at 8:58 AM, Alex Harui  wrote:
> 
> FWIW, I think I've reproduced it.  There is a circularity of goog.requires
> that cannot be fixed by removing circulars that I can see.
> 
> Essentially, if StandardFlowComposer extends FlowComposerBase which
> references FactoryComposer which extends StandardFlowComposer, then the
> following goog.requires are in play
> 
> --StandardFlowComposer.as--
> goog.require(FlowComposerBase);
> 
> --FlowComposerBase.as--
> Goog.require(FactoryComposer);
> 
> --FactoryComposer.as--
> goog.require(StandardFlowComposer);
> 
> This is a cycle.  AFAICT, removing the only goog.requires that isn't an
> inheritance chain dependency means that FactoryComposer will not be linked
> into the movie.
> 
> I think that instead of removing goog.requires, we need to move them to
> the main app.  I'll try that tomorrow.
> 
> Anyone have any thoughts on this topic?
> 
> Thanks,
> -Alex
> 
> 
> 
> On 3/15/17, 6:53 AM, "Harbs"  wrote:
> 
>> Enjoy: ;-)
>> 
>> https://paste.apache.org/UK5X 
>> 
>>> On Mar 15, 2017, at 3:32 PM, Alex Harui  wrote:
>>> 
>>> Please post all console output. Thanks
>>> 
>>> Get Outlook for Android
>>> 
>>> 
>>> 
>>> From: Harbs 
>>> Sent: Tuesday, March 14, 2017 11:52:50 PM
>>> To: dev@flex.apache.org
>>> Subject: Re: Just need to vent...
>>> 
>>> I just pulled in the latests changes and the build now “completes” with
>>> a different problem:
>>> 
>>>[java] Mar 15, 2017 8:49:42 AM
>>> com.google.javascript.jscomp.LoggerErrorManager println
>>>[java] SEVERE:
>>> /Users/harbs/Documents/git/PrintUI/printui-flexjs/text_engine/test/HelloW
>>> orldTLF/bin/js-debug/org/apache/flex/textLayout/compose/StandardFlowCompo
>>> ser.js:12: ERROR - required
>>> "org.apache.flex.textLayout.compose.FlowComposerBase" namespace not
>>> provided yet
>>>[java] 
>>> goog.require('org.apache.flex.textLayout.compose.FlowComposerBase');
>>>[java] 
>>> ^^^
>>>[java]
>>>[java] Mar 15, 2017 8:49:42 AM
>>> com.google.javascript.jscomp.LoggerErrorManager println
>>>[java] SEVERE:
>>> /Users/harbs/Documents/git/PrintUI/printui-flexjs/text_engine/test/HelloW
>>> orldTLF/bin/js-debug/org/apache/flex/textLayout/compose/StandardFlowCompo
>>> ser.js:14: ERROR - required
>>> "org.apache.flex.textLayout.events.CompositionCompleteEvent" namespace
>>> not provided yet
>>>[java] 
>>> goog.require('org.apache.flex.textLayout.events.CompositionCompleteEvent'
>>> );
>>>[java] 
>>> ^
>>> ^
>>>[java]
>>>[java] Mar 15, 2017 8:49:42 AM
>>> com.google.javascript.jscomp.LoggerErrorManager println
>>>[java] SEVERE:
>>> /Users/harbs/Documents/git/PrintUI/printui-flexjs/text_engine/test/HelloW
>>> orldTLF/bin/js-debug/org/apache/flex/textLayout/compose/StandardFlowCompo
>>> ser.js:15: ERROR - required
>>> "org.apache.flex.textLayout.utils.ComposeUtils" namespace not provided
>>> yet
>>>[java] 
>>> goog.require('org.apache.flex.textLayout.utils.ComposeUtils');
>>>[java] ^
>>> 
>>> 
>>> I’m not sure how you’re trying to resolve the order on these files, but
>>> it’s obviously not straight-forward…
>>> 
 On Mar 15, 2017, at 12:38 AM, Alex Harui  wrote:
 
 Hmm.  I wonder what that is.  I just pushed an attempt to report on why
 that is.
 
 -Alex
 
 
 On 3/14/17, 2:16 PM, "Harbs"  wrote:
 
> Got an error:
> https://paste.apache.org/KgxC 
> 
>> On Mar 14, 2017, at 10:34 PM, Harbs  wrote:
>> 
>> Pulling now. I’ll let you know how it goes.
>> 
>>> On Mar 14, 2017, at 9:44 PM, Alex Harui  wrote:
>>> 
>>> 
>>> 
>>> On 3/14/17, 12:20 AM, "Harbs"  wrote:
>>> 
 That’s great! I’m anxiously waiting to see what you can do! ;-)
>>> 
>>> OK, I 

Re: [FlexJS] Dual branch

2017-03-16 Thread Harbs
I have not had the time.

Is there anything to be aware of when you merge it in from an application 
development stand-point?

Have you done anything regarding the Basic vs. HTML projects?

Harbs

> On Mar 16, 2017, at 3:01 AM, Alex Harui  wrote:
> 
> Has anyone else looked at the dual branch?  If you want to know more about
> it before it gets merged let me know soon, otherwise I am going to merge
> it.
> 
> Thanks,
> -Alex
> 
> On 3/11/17, 10:49 PM, "Alex Harui"  wrote:
> 
>> 
>> 
>> On 3/11/17, 10:34 AM, "Christofer Dutz"  wrote:
>> 
>>> Hi Alex,
>>> 
>>> I just had a look and the changes look valid. The only thing I think I
>>> should change, is that it seems as if prior to your change, I needed two
>>> compilations AS & JS and therefore there were two Mojos: CompileASMojo
>>> and CompileJSMojo. I think now we need only one. If the current state it
>>> also looks as if both the AS and the JS mojo would do a dual compilation.
>>> 
>>> If you confirm, that now I need only one Mojo, I would refactor it and
>>> create a “CompileLibMojo” and remove the other two CompileASMojo and
>>> CompileJSMojo.
>> 
>> Well, we still build two SWCs per project.  We might want to rename the
>> Mojos, but the CompileASMojo builds a SWC that has a library.swf with
>> COMPILE::SWF=true but includes JS files compiled with COMPILE::JS=true,
>> then CompileJSMojo builds a SWC that has a library.swf with
>> COMPILE::JS=true and the JS files with COMPILE::JS=true and the artifact
>> has the -js classifier.
>> 
>> At some point we can try combining the two and renaming one of the
>> library.swf and catalog.xml files, but for now we still need a SWC with
>> library.swf with COMPILE::SWF=true and a SWC with library.swf with
>> COMPILE::JS=true.
>> 
>> Thanks,
>> -Alex
>> 
> 



Re: Just need to vent...

2017-03-16 Thread Alex Harui
FWIW, I think I've reproduced it.  There is a circularity of goog.requires
that cannot be fixed by removing circulars that I can see.

Essentially, if StandardFlowComposer extends FlowComposerBase which
references FactoryComposer which extends StandardFlowComposer, then the
following goog.requires are in play

--StandardFlowComposer.as--
goog.require(FlowComposerBase);

--FlowComposerBase.as--
Goog.require(FactoryComposer);

--FactoryComposer.as--
goog.require(StandardFlowComposer);

This is a cycle.  AFAICT, removing the only goog.requires that isn't an
inheritance chain dependency means that FactoryComposer will not be linked
into the movie.

I think that instead of removing goog.requires, we need to move them to
the main app.  I'll try that tomorrow.

Anyone have any thoughts on this topic?

Thanks,
-Alex



On 3/15/17, 6:53 AM, "Harbs"  wrote:

>Enjoy: ;-)
>
>https://paste.apache.org/UK5X 
>
>> On Mar 15, 2017, at 3:32 PM, Alex Harui  wrote:
>> 
>> Please post all console output. Thanks
>> 
>> Get Outlook for Android
>> 
>> 
>> 
>> From: Harbs 
>> Sent: Tuesday, March 14, 2017 11:52:50 PM
>> To: dev@flex.apache.org
>> Subject: Re: Just need to vent...
>> 
>> I just pulled in the latests changes and the build now “completes” with
>>a different problem:
>> 
>> [java] Mar 15, 2017 8:49:42 AM
>>com.google.javascript.jscomp.LoggerErrorManager println
>> [java] SEVERE:
>>/Users/harbs/Documents/git/PrintUI/printui-flexjs/text_engine/test/HelloW
>>orldTLF/bin/js-debug/org/apache/flex/textLayout/compose/StandardFlowCompo
>>ser.js:12: ERROR - required
>>"org.apache.flex.textLayout.compose.FlowComposerBase" namespace not
>>provided yet
>> [java] 
>>goog.require('org.apache.flex.textLayout.compose.FlowComposerBase');
>> [java] 
>>^^^
>> [java]
>> [java] Mar 15, 2017 8:49:42 AM
>>com.google.javascript.jscomp.LoggerErrorManager println
>> [java] SEVERE:
>>/Users/harbs/Documents/git/PrintUI/printui-flexjs/text_engine/test/HelloW
>>orldTLF/bin/js-debug/org/apache/flex/textLayout/compose/StandardFlowCompo
>>ser.js:14: ERROR - required
>>"org.apache.flex.textLayout.events.CompositionCompleteEvent" namespace
>>not provided yet
>> [java] 
>>goog.require('org.apache.flex.textLayout.events.CompositionCompleteEvent'
>>);
>> [java] 
>>^
>>^
>> [java]
>> [java] Mar 15, 2017 8:49:42 AM
>>com.google.javascript.jscomp.LoggerErrorManager println
>> [java] SEVERE:
>>/Users/harbs/Documents/git/PrintUI/printui-flexjs/text_engine/test/HelloW
>>orldTLF/bin/js-debug/org/apache/flex/textLayout/compose/StandardFlowCompo
>>ser.js:15: ERROR - required
>>"org.apache.flex.textLayout.utils.ComposeUtils" namespace not provided
>>yet
>> [java] 
>>goog.require('org.apache.flex.textLayout.utils.ComposeUtils');
>> [java] ^
>> 
>> 
>> I’m not sure how you’re trying to resolve the order on these files, but
>>it’s obviously not straight-forward…
>> 
>>> On Mar 15, 2017, at 12:38 AM, Alex Harui  wrote:
>>> 
>>> Hmm.  I wonder what that is.  I just pushed an attempt to report on why
>>> that is.
>>> 
>>> -Alex
>>> 
>>> 
>>> On 3/14/17, 2:16 PM, "Harbs"  wrote:
>>> 
 Got an error:
 https://paste.apache.org/KgxC 
 
> On Mar 14, 2017, at 10:34 PM, Harbs  wrote:
> 
> Pulling now. I’ll let you know how it goes.
> 
>> On Mar 14, 2017, at 9:44 PM, Alex Harui  wrote:
>> 
>> 
>> 
>> On 3/14/17, 12:20 AM, "Harbs"  wrote:
>> 
>>> That’s great! I’m anxiously waiting to see what you can do! ;-)
>> 
>> OK, I put in a fix for my simple case.  See if it helps on your case
>> and
>> if compile times really bog down.
>> 
>> Basically, we are trying to list the contents of a DAG, but when you
>> run
>> into a node a again, you not only have to shift the order of items
>>in
>> the
>> list, we also have to fix up the goog.requires.  That requires a
>>lot of
>> revisiting.  I'm wondering if there is a better strategy, like
>>fixing
>> up
>> the goog.requires at the very end once the order is otherwise
>> determined.
>> 
>> That's more risky work than I'd like to do, but maybe we have to
>>just
>> do
>> it.
>> 
>> -Alex
>> 
> 
 
>>> 
>> 
>



Re: [FlexJS] ASDoc (was Re: [FlexJS] maven faling (WeakMap)

2017-03-16 Thread Alex Harui
OK, I removed the Flex SDK ASDoc part of the build.  Next build is
probably less than 2 hours away.

-Alex

On 3/15/17, 11:21 PM, "piotrz"  wrote:

>Alex,
>
>I think we have enough agreed on switching it to FlexJS ASDoc. We have
>failing build on jenkins [1] for a long time, which means that none can
>try
>the fresh changes through the installer.
>
>[1] http://apacheflexbuild.cloudapp.net:8080/job/flex-asjs/
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/FlexJS-ASDoc-was-Re-F
>lexJS-maven-faling-WeakMap-tp60325p60496.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.



Re: [FlexJS] ASDoc (was Re: [FlexJS] maven faling (WeakMap)

2017-03-16 Thread piotrz
Alex,

I think we have enough agreed on switching it to FlexJS ASDoc. We have
failing build on jenkins [1] for a long time, which means that none can try
the fresh changes through the installer. 

[1] http://apacheflexbuild.cloudapp.net:8080/job/flex-asjs/

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-ASDoc-was-Re-FlexJS-maven-faling-WeakMap-tp60325p60496.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.


Re: FlexJS / Jenkins on Unix

2017-03-16 Thread Justin Mclean
Hi,

Was just taking a look at this again and it’s now working. 

Not 100% sure what has changed but a GitHub change triggered the CI server 
which got the latest FlexJS 0.8 snapshots and the application compiled to 
completion, and build past that have also worked. If you changed something 
Chris - thanks!

So it is possible to have your FlexJS applications compiled on a Jenkins CI 
server on Linux.

Thanks,
Justin

Re: [MDL Dialogs] was: Re: [FlexJS] MDL - Dynamic Child Problem

2017-03-16 Thread piotrz
Hi Santanau,

I'm thinking on adding as "default" to components ability for dynamic
creation without any "isDynamic" property etc. I wanted to discuss it with
Carlos in the other thread, but he is busy currently, so I'm still waiting
for his input. If I got it positiv I will start work and you shouldn't have
problem for dynamic creation of component even in mxml. - I hope ;)

Thanks,
Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Dynamic-Child-Problem-tp59595p60494.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.