date:20170501

On 4/30/17, 7:44 AM, "Christofer Dutz"  wrote:

>Hi Gyus,
>
>I guess the reason is that the default Ant job tries to read the file
>into memory. This isn’t needed in order to calculate the md5 hash … If
>the target used a streaming implementation, it should work with a few KB
>of memory.

True.  Volunteers are welcome to work on that as well.  However, my
computer has enough memory to do the job.  Maybe Tom or others can help
out as well.  I've beefed up the Wiki page here [1]

[1] 
https://cwiki.apache.org/confluence/display/FLEX/MD5Checker+Instruction+Man
ual

-Alex

Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0

On 5/1/17, 3:30 PM, "Greg Dove"  wrote:

>Thanks Alex,  I can see it in the swc, so I'm not sure what is causing the
>issue.
>I will have to revert and use the pre-dual code today, but will come back
>to it in two days to try to figure it out again, after an imminent
>deadline
>that I need to focus on.

OK.  In the js-debug output, there should be at least one file that has a
goog.require for HTMLElementWrapper, and the console should have shown
that HTMLElementWrapper got copied to js-debug.

Thanks,
-Alex

Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0

Thanks Alex,  I can see it in the swc, so I'm not sure what is causing the
issue.
I will have to revert and use the pre-dual code today, but will come back
to it in two days to try to figure it out again, after an imminent deadline
that I need to focus on.

On Tue, May 2, 2017 at 8:41 AM, Alex Harui  wrote:

>
>
> On 5/1/17, 1:33 PM, "Greg Dove"  wrote:
>
> >Just as a quick follow-up (in case anyone else is looking for the same)
> >
> >adding:
> >js
> >to all the swc dependencies in the pom meant I could compile the js-only
> >project. JS alone was not enough.
> >
> >However I am seeing some runtime errors with things like
> >base.js:628 goog.require could not find:
> >org.apache.flex.core.HTMLElementWrapper
>
> Unzip the SWCs and see if HTMLElementWrapper is Basic.swc and/or
> BasicJS.swc.  Basic is "new" so it may need to be added to some POMs.  The
> examples build for me, so I think I got it right in the repo.
>
> HTH,
> -Alex
>
>

Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0

On 5/1/17, 1:33 PM, "Greg Dove"  wrote:

>Just as a quick follow-up (in case anyone else is looking for the same)
>
>adding:
>js
>to all the swc dependencies in the pom meant I could compile the js-only
>project. JS alone was not enough.
>
>However I am seeing some runtime errors with things like
>base.js:628 goog.require could not find:
>org.apache.flex.core.HTMLElementWrapper

Unzip the SWCs and see if HTMLElementWrapper is Basic.swc and/or
BasicJS.swc.  Basic is "new" so it may need to be added to some POMs.  The
examples build for me, so I think I got it right in the repo.

HTH,
-Alex

Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0

Just as a quick follow-up (in case anyone else is looking for the same)

adding:
js
to all the swc dependencies in the pom meant I could compile the js-only
project. JS alone was not enough.

However I am seeing some runtime errors with things like
base.js:628 goog.require could not find:
org.apache.flex.core.HTMLElementWrapper

and similar.

I'm currently trying to figure this out.


On Tue, May 2, 2017 at 5:19 AM, Greg Dove  wrote:

> Thanks Alex,
>
> This helps
> JS
> Still some stuff left to figure out, but that is progress. Pretty sure
> that falls into "I am hoping there is something simple that I didn't see" -
> thanks again.
>
> btw I think :
> true
>
> is presumably redundant in any pom.xml now, including that example. My
> reason for thinking that is that it is coming up 'red', with tooltip
> "Element outputJavaScript is not allowed here", for a local project via
> code highlighting in Intellij (which was really helpful initially to
> understand this change).
>
>
>
> On Tue, May 2, 2017 at 4:42 AM, Alex Harui  wrote:
>
>> I believe examples/native/ButtonExample only produces JS output.
>>
>> -Alex
>>
>> On 5/1/17, 9:11 AM, "Greg Dove"  wrote:
>>
>> >Chris, or perhaps Alex:
>> >With the latest changes for maven, I am trying to figure out how to get
>> >the
>> >same result with maven as
>> >true
>> >
>> >which previously permitted js-only compilation so that COMPILE::JS was
>> not
>> >needed in js-only target project, and it was possible to use, for
>> example,
>> >var style:CSSStyleDeclaration,
>> >window['Intl'] etc
>> >outside of COMPILE::JS
>> >
>> >Is this still possible in some way after the change? I can see options
>> for
>> >maven like
>> >skipAS etc, but have not figured out a combination that achieves the
>> same.
>> >
>> >I am hoping there is something simple that I didn't see - I am still
>> >getting my head around using maven, (apart from finding it mostly very
>> >intuitive to 'read').
>> >If not, I can always go through the code and wrap things in COMPILE::JS,
>> >was just hoping that I don't need to do that.
>> >Thanks,
>> >Greg
>> >
>> >
>> >On Tue, May 2, 2017 at 2:51 AM, Christofer Dutz
>> >
>> >wrote:
>> >
>> >> But in general, “mvn clean compile” should have worked. I even double
>> >> checked with the debugger … if the other modules are part of the build
>> >>it
>> >> would acutally resolve the artifacts from the target directories
>> >>instead of
>> >> from the maven local repo … I’ll continue investigating this.
>> >>
>> >> Chris
>> >>
>> >> Am 30.04.17, 23:42 schrieb "Justin Mclean" :
>> >>
>> >> Hi,
>> >>
>> >> > You are running “mvn clean compile” which compiles each module
>> and
>> >> created the swcs in the target directories. Unfortunately, they just
>> >>stay
>> >> there as they are not copied to your maven local repository.
>> >>
>> >> Thanks Chris that would explain the error.
>> >>
>> >> > To do that, you need to run “mvn clean install”. I would give
>> >>that a
>> >> try.
>> >>
>> >> Looks like typedef is now broken as I’m getting this:
>> >>
>> >> [INFO] --- exec-maven-plugin:1.5.0:exec (patch-js) @
>> >> flexjs-typedefs-js ---
>> >> error: patch failed: js/target/downloads/svg.js:401
>> >> error: js/target/downloads/svg.js: patch does not apply
>> >> [ERROR] Command execution failed.
>> >>
>> >> I’m assume the patch file no longer matches what’s at [1]?
>> >>
>> >> Thanks,
>> >> Justin
>> >>
>> >> 1.
>> >>https://na01.safelinks.protection.outlook.com/?url=https%3
>> A%2F%2Fstorage.
>> >>googleapis.com%2Fgoogle-code-archive-=02%7C01%7C%7C6d
>> 802edc936741aa1
>> >>c4e08d490acbcb6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0
>> %7C636292518959
>> >>818809=XnKepN4BFugfoG%2BrYp3Kpsc%2F8ZGRT64IpOKGuJ0%2
>> Fk%2Fo%3D
>> >>ved=0
>> >> downloads/v2/code.google.com/closureidl/svg.js
>> >>
>> >>
>> >>
>> >>
>>
>>
>

Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0



On 5/1/17, 10:19 AM, "Greg Dove"  wrote:
>
>btw I think :
>true
>
>is presumably redundant in any pom.xml now,

Yes, I'm pretty sure those can be removed.  Volunteers are welcome to do
that.  I'm still chasing down other issues.

Thanks,
-Alex

Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0

2017-05-01 Thread OmPrakash Muppirala

flex-falcon and flex-typedefs built fine for me.

The flex-asjs build is broken for me on the Fonts project.

Here is the relevant log:

https://paste.apache.org/kATQ

Can someone please take a look?

Thanks,
Om

On Mon, May 1, 2017 at 11:50 AM, OmPrakash Muppirala 
wrote:

> For folks who want to help out but are not sure how to, please follow the
> step by step instructions here on how to build the FlexJS SDK from the
> sources:
>
> https://cwiki.apache.org/confluence/display/FLEX/
> Building+FlexJS+with+Maven
>
> Thanks,
> Om
>
> On Mon, May 1, 2017 at 10:19 AM, Greg Dove  wrote:
>
>> Thanks Alex,
>>
>> This helps
>> JS
>> Still some stuff left to figure out, but that is progress. Pretty sure
>> that
>> falls into "I am hoping there is something simple that I didn't see" -
>> thanks again.
>>
>> btw I think :
>> true
>>
>> is presumably redundant in any pom.xml now, including that example. My
>> reason for thinking that is that it is coming up 'red', with tooltip
>> "Element outputJavaScript is not allowed here", for a local project via
>> code highlighting in Intellij (which was really helpful initially to
>> understand this change).
>>
>>
>>
>> On Tue, May 2, 2017 at 4:42 AM, Alex Harui  wrote:
>>
>> > I believe examples/native/ButtonExample only produces JS output.
>> >
>> > -Alex
>> >
>> > On 5/1/17, 9:11 AM, "Greg Dove"  wrote:
>> >
>> > >Chris, or perhaps Alex:
>> > >With the latest changes for maven, I am trying to figure out how to get
>> > >the
>> > >same result with maven as
>> > >true
>> > >
>> > >which previously permitted js-only compilation so that COMPILE::JS was
>> not
>> > >needed in js-only target project, and it was possible to use, for
>> example,
>> > >var style:CSSStyleDeclaration,
>> > >window['Intl'] etc
>> > >outside of COMPILE::JS
>> > >
>> > >Is this still possible in some way after the change? I can see options
>> for
>> > >maven like
>> > >skipAS etc, but have not figured out a combination that achieves the
>> same.
>> > >
>> > >I am hoping there is something simple that I didn't see - I am still
>> > >getting my head around using maven, (apart from finding it mostly very
>> > >intuitive to 'read').
>> > >If not, I can always go through the code and wrap things in
>> COMPILE::JS,
>> > >was just hoping that I don't need to do that.
>> > >Thanks,
>> > >Greg
>> > >
>> > >
>> > >On Tue, May 2, 2017 at 2:51 AM, Christofer Dutz
>> > >
>> > >wrote:
>> > >
>> > >> But in general, “mvn clean compile” should have worked. I even double
>> > >> checked with the debugger … if the other modules are part of the
>> build
>> > >>it
>> > >> would acutally resolve the artifacts from the target directories
>> > >>instead of
>> > >> from the maven local repo … I’ll continue investigating this.
>> > >>
>> > >> Chris
>> > >>
>> > >> Am 30.04.17, 23:42 schrieb "Justin Mclean" > >:
>> > >>
>> > >> Hi,
>> > >>
>> > >> > You are running “mvn clean compile” which compiles each module
>> and
>> > >> created the swcs in the target directories. Unfortunately, they just
>> > >>stay
>> > >> there as they are not copied to your maven local repository.
>> > >>
>> > >> Thanks Chris that would explain the error.
>> > >>
>> > >> > To do that, you need to run “mvn clean install”. I would give
>> > >>that a
>> > >> try.
>> > >>
>> > >> Looks like typedef is now broken as I’m getting this:
>> > >>
>> > >> [INFO] --- exec-maven-plugin:1.5.0:exec (patch-js) @
>> > >> flexjs-typedefs-js ---
>> > >> error: patch failed: js/target/downloads/svg.js:401
>> > >> error: js/target/downloads/svg.js: patch does not apply
>> > >> [ERROR] Command execution failed.
>> > >>
>> > >> I’m assume the patch file no longer matches what’s at [1]?
>> > >>
>> > >> Thanks,
>> > >> Justin
>> > >>
>> > >> 1.
>> > >>https://na01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Fstorage
>> > .
>> > >>googleapis.com%2Fgoogle-code-archive-=02%7C01%7C%
>> > 7C6d802edc936741aa1
>> > >>c4e08d490acbcb6%7Cfa7b1b5a7b34438794aed2c178de
>> > cee1%7C0%7C0%7C636292518959
>> > >>818809=XnKepN4BFugfoG%2BrYp3Kpsc%2F8ZGRT64IpOKGuJ0%
>> > 2Fk%2Fo%3D
>> > >>ved=0
>> > >> downloads/v2/code.google.com/closureidl/svg.js
>> > >>
>> > >>
>> > >>
>> > >>
>> >
>> >
>>
>
>

Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0

2017-05-01 Thread OmPrakash Muppirala

For folks who want to help out but are not sure how to, please follow the
step by step instructions here on how to build the FlexJS SDK from the
sources:

https://cwiki.apache.org/confluence/display/FLEX/Building+FlexJS+with+Maven

Thanks,
Om

On Mon, May 1, 2017 at 10:19 AM, Greg Dove  wrote:

> Thanks Alex,
>
> This helps
> JS
> Still some stuff left to figure out, but that is progress. Pretty sure that
> falls into "I am hoping there is something simple that I didn't see" -
> thanks again.
>
> btw I think :
> true
>
> is presumably redundant in any pom.xml now, including that example. My
> reason for thinking that is that it is coming up 'red', with tooltip
> "Element outputJavaScript is not allowed here", for a local project via
> code highlighting in Intellij (which was really helpful initially to
> understand this change).
>
>
>
> On Tue, May 2, 2017 at 4:42 AM, Alex Harui  wrote:
>
> > I believe examples/native/ButtonExample only produces JS output.
> >
> > -Alex
> >
> > On 5/1/17, 9:11 AM, "Greg Dove"  wrote:
> >
> > >Chris, or perhaps Alex:
> > >With the latest changes for maven, I am trying to figure out how to get
> > >the
> > >same result with maven as
> > >true
> > >
> > >which previously permitted js-only compilation so that COMPILE::JS was
> not
> > >needed in js-only target project, and it was possible to use, for
> example,
> > >var style:CSSStyleDeclaration,
> > >window['Intl'] etc
> > >outside of COMPILE::JS
> > >
> > >Is this still possible in some way after the change? I can see options
> for
> > >maven like
> > >skipAS etc, but have not figured out a combination that achieves the
> same.
> > >
> > >I am hoping there is something simple that I didn't see - I am still
> > >getting my head around using maven, (apart from finding it mostly very
> > >intuitive to 'read').
> > >If not, I can always go through the code and wrap things in COMPILE::JS,
> > >was just hoping that I don't need to do that.
> > >Thanks,
> > >Greg
> > >
> > >
> > >On Tue, May 2, 2017 at 2:51 AM, Christofer Dutz
> > >
> > >wrote:
> > >
> > >> But in general, “mvn clean compile” should have worked. I even double
> > >> checked with the debugger … if the other modules are part of the build
> > >>it
> > >> would acutally resolve the artifacts from the target directories
> > >>instead of
> > >> from the maven local repo … I’ll continue investigating this.
> > >>
> > >> Chris
> > >>
> > >> Am 30.04.17, 23:42 schrieb "Justin Mclean"  >:
> > >>
> > >> Hi,
> > >>
> > >> > You are running “mvn clean compile” which compiles each module
> and
> > >> created the swcs in the target directories. Unfortunately, they just
> > >>stay
> > >> there as they are not copied to your maven local repository.
> > >>
> > >> Thanks Chris that would explain the error.
> > >>
> > >> > To do that, you need to run “mvn clean install”. I would give
> > >>that a
> > >> try.
> > >>
> > >> Looks like typedef is now broken as I’m getting this:
> > >>
> > >> [INFO] --- exec-maven-plugin:1.5.0:exec (patch-js) @
> > >> flexjs-typedefs-js ---
> > >> error: patch failed: js/target/downloads/svg.js:401
> > >> error: js/target/downloads/svg.js: patch does not apply
> > >> [ERROR] Command execution failed.
> > >>
> > >> I’m assume the patch file no longer matches what’s at [1]?
> > >>
> > >> Thanks,
> > >> Justin
> > >>
> > >> 1.
> > >>https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fstorage
> > .
> > >>googleapis.com%2Fgoogle-code-archive-=02%7C01%7C%
> > 7C6d802edc936741aa1
> > >>c4e08d490acbcb6%7Cfa7b1b5a7b34438794aed2c178de
> > cee1%7C0%7C0%7C636292518959
> > >>818809=XnKepN4BFugfoG%2BrYp3Kpsc%2F8ZGRT64IpOKGuJ0%
> > 2Fk%2Fo%3D
> > >>ved=0
> > >> downloads/v2/code.google.com/closureidl/svg.js
> > >>
> > >>
> > >>
> > >>
> >
> >
>

Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0

Thanks Alex,

This helps
JS
Still some stuff left to figure out, but that is progress. Pretty sure that
falls into "I am hoping there is something simple that I didn't see" -
thanks again.

btw I think :
true

is presumably redundant in any pom.xml now, including that example. My
reason for thinking that is that it is coming up 'red', with tooltip
"Element outputJavaScript is not allowed here", for a local project via
code highlighting in Intellij (which was really helpful initially to
understand this change).



On Tue, May 2, 2017 at 4:42 AM, Alex Harui  wrote:

> I believe examples/native/ButtonExample only produces JS output.
>
> -Alex
>
> On 5/1/17, 9:11 AM, "Greg Dove"  wrote:
>
> >Chris, or perhaps Alex:
> >With the latest changes for maven, I am trying to figure out how to get
> >the
> >same result with maven as
> >true
> >
> >which previously permitted js-only compilation so that COMPILE::JS was not
> >needed in js-only target project, and it was possible to use, for example,
> >var style:CSSStyleDeclaration,
> >window['Intl'] etc
> >outside of COMPILE::JS
> >
> >Is this still possible in some way after the change? I can see options for
> >maven like
> >skipAS etc, but have not figured out a combination that achieves the same.
> >
> >I am hoping there is something simple that I didn't see - I am still
> >getting my head around using maven, (apart from finding it mostly very
> >intuitive to 'read').
> >If not, I can always go through the code and wrap things in COMPILE::JS,
> >was just hoping that I don't need to do that.
> >Thanks,
> >Greg
> >
> >
> >On Tue, May 2, 2017 at 2:51 AM, Christofer Dutz
> >
> >wrote:
> >
> >> But in general, “mvn clean compile” should have worked. I even double
> >> checked with the debugger … if the other modules are part of the build
> >>it
> >> would acutally resolve the artifacts from the target directories
> >>instead of
> >> from the maven local repo … I’ll continue investigating this.
> >>
> >> Chris
> >>
> >> Am 30.04.17, 23:42 schrieb "Justin Mclean" :
> >>
> >> Hi,
> >>
> >> > You are running “mvn clean compile” which compiles each module and
> >> created the swcs in the target directories. Unfortunately, they just
> >>stay
> >> there as they are not copied to your maven local repository.
> >>
> >> Thanks Chris that would explain the error.
> >>
> >> > To do that, you need to run “mvn clean install”. I would give
> >>that a
> >> try.
> >>
> >> Looks like typedef is now broken as I’m getting this:
> >>
> >> [INFO] --- exec-maven-plugin:1.5.0:exec (patch-js) @
> >> flexjs-typedefs-js ---
> >> error: patch failed: js/target/downloads/svg.js:401
> >> error: js/target/downloads/svg.js: patch does not apply
> >> [ERROR] Command execution failed.
> >>
> >> I’m assume the patch file no longer matches what’s at [1]?
> >>
> >> Thanks,
> >> Justin
> >>
> >> 1.
> >>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstorage
> .
> >>googleapis.com%2Fgoogle-code-archive-=02%7C01%7C%
> 7C6d802edc936741aa1
> >>c4e08d490acbcb6%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636292518959
> >>818809=XnKepN4BFugfoG%2BrYp3Kpsc%2F8ZGRT64IpOKGuJ0%
> 2Fk%2Fo%3D
> >>ved=0
> >> downloads/v2/code.google.com/closureidl/svg.js
> >>
> >>
> >>
> >>
>
>

Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0

I believe examples/native/ButtonExample only produces JS output.

-Alex

On 5/1/17, 9:11 AM, "Greg Dove"  wrote:

>Chris, or perhaps Alex:
>With the latest changes for maven, I am trying to figure out how to get
>the
>same result with maven as
>true
>
>which previously permitted js-only compilation so that COMPILE::JS was not
>needed in js-only target project, and it was possible to use, for example,
>var style:CSSStyleDeclaration,
>window['Intl'] etc
>outside of COMPILE::JS
>
>Is this still possible in some way after the change? I can see options for
>maven like
>skipAS etc, but have not figured out a combination that achieves the same.
>
>I am hoping there is something simple that I didn't see - I am still
>getting my head around using maven, (apart from finding it mostly very
>intuitive to 'read').
>If not, I can always go through the code and wrap things in COMPILE::JS,
>was just hoping that I don't need to do that.
>Thanks,
>Greg
>
>
>On Tue, May 2, 2017 at 2:51 AM, Christofer Dutz
>
>wrote:
>
>> But in general, “mvn clean compile” should have worked. I even double
>> checked with the debugger … if the other modules are part of the build
>>it
>> would acutally resolve the artifacts from the target directories
>>instead of
>> from the maven local repo … I’ll continue investigating this.
>>
>> Chris
>>
>> Am 30.04.17, 23:42 schrieb "Justin Mclean" :
>>
>> Hi,
>>
>> > You are running “mvn clean compile” which compiles each module and
>> created the swcs in the target directories. Unfortunately, they just
>>stay
>> there as they are not copied to your maven local repository.
>>
>> Thanks Chris that would explain the error.
>>
>> > To do that, you need to run “mvn clean install”. I would give
>>that a
>> try.
>>
>> Looks like typedef is now broken as I’m getting this:
>>
>> [INFO] --- exec-maven-plugin:1.5.0:exec (patch-js) @
>> flexjs-typedefs-js ---
>> error: patch failed: js/target/downloads/svg.js:401
>> error: js/target/downloads/svg.js: patch does not apply
>> [ERROR] Command execution failed.
>>
>> I’m assume the patch file no longer matches what’s at [1]?
>>
>> Thanks,
>> Justin
>>
>> 1. 
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstorage.
>>googleapis.com%2Fgoogle-code-archive-=02%7C01%7C%7C6d802edc936741aa1
>>c4e08d490acbcb6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636292518959
>>818809=XnKepN4BFugfoG%2BrYp3Kpsc%2F8ZGRT64IpOKGuJ0%2Fk%2Fo%3D
>>ved=0
>> downloads/v2/code.google.com/closureidl/svg.js
>>
>>
>>
>>

Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0

2017-05-01 Thread Christofer Dutz

Hi Greg,

I must admit that I currently don’t quite know the changes Alex did. It seems 
the normal build scenarios inside the framework still seem to work, but I can’t 
tell about any of the others. But I think it should be easy to provide the 
functionality you are looking for as soon as Alex provides me with information 
on what we have to change.

Chris

Am 01.05.17, 18:11 schrieb "Greg Dove" :

Chris, or perhaps Alex:
With the latest changes for maven, I am trying to figure out how to get the
same result with maven as
true

which previously permitted js-only compilation so that COMPILE::JS was not
needed in js-only target project, and it was possible to use, for example,
var style:CSSStyleDeclaration,
window['Intl'] etc
outside of COMPILE::JS

Is this still possible in some way after the change? I can see options for
maven like
skipAS etc, but have not figured out a combination that achieves the same.

I am hoping there is something simple that I didn't see - I am still
getting my head around using maven, (apart from finding it mostly very
intuitive to 'read').
If not, I can always go through the code and wrap things in COMPILE::JS,
was just hoping that I don't need to do that.
Thanks,
Greg

On Tue, May 2, 2017 at 2:51 AM, Christofer Dutz 
wrote:

> But in general, “mvn clean compile” should have worked. I even double
> checked with the debugger … if the other modules are part of the build it
> would acutally resolve the artifacts from the target directories instead 
of
> from the maven local repo … I’ll continue investigating this.
>
> Chris
>
> Am 30.04.17, 23:42 schrieb "Justin Mclean" :
>
> Hi,
>
> > You are running “mvn clean compile” which compiles each module and
> created the swcs in the target directories. Unfortunately, they just stay
> there as they are not copied to your maven local repository.
>
> Thanks Chris that would explain the error.
>
> > To do that, you need to run “mvn clean install”. I would give that a
> try.
>
> Looks like typedef is now broken as I’m getting this:
>
> [INFO] --- exec-maven-plugin:1.5.0:exec (patch-js) @
> flexjs-typedefs-js ---
> error: patch failed: js/target/downloads/svg.js:401
> error: js/target/downloads/svg.js: patch does not apply
> [ERROR] Command execution failed.
>
> I’m assume the patch file no longer matches what’s at [1]?
>
> Thanks,
> Justin
>
> 1. https://storage.googleapis.com/google-code-archive-
> downloads/v2/code.google.com/closureidl/svg.js
>
>
>
>

Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0

Chris, or perhaps Alex:
With the latest changes for maven, I am trying to figure out how to get the
same result with maven as
true

which previously permitted js-only compilation so that COMPILE::JS was not
needed in js-only target project, and it was possible to use, for example,
var style:CSSStyleDeclaration,
window['Intl'] etc
outside of COMPILE::JS

Is this still possible in some way after the change? I can see options for
maven like
skipAS etc, but have not figured out a combination that achieves the same.

I am hoping there is something simple that I didn't see - I am still
getting my head around using maven, (apart from finding it mostly very
intuitive to 'read').
If not, I can always go through the code and wrap things in COMPILE::JS,
was just hoping that I don't need to do that.
Thanks,
Greg


On Tue, May 2, 2017 at 2:51 AM, Christofer Dutz 
wrote:

> But in general, “mvn clean compile” should have worked. I even double
> checked with the debugger … if the other modules are part of the build it
> would acutally resolve the artifacts from the target directories instead of
> from the maven local repo … I’ll continue investigating this.
>
> Chris
>
> Am 30.04.17, 23:42 schrieb "Justin Mclean" :
>
> Hi,
>
> > You are running “mvn clean compile” which compiles each module and
> created the swcs in the target directories. Unfortunately, they just stay
> there as they are not copied to your maven local repository.
>
> Thanks Chris that would explain the error.
>
> > To do that, you need to run “mvn clean install”. I would give that a
> try.
>
> Looks like typedef is now broken as I’m getting this:
>
> [INFO] --- exec-maven-plugin:1.5.0:exec (patch-js) @
> flexjs-typedefs-js ---
> error: patch failed: js/target/downloads/svg.js:401
> error: js/target/downloads/svg.js: patch does not apply
> [ERROR] Command execution failed.
>
> I’m assume the patch file no longer matches what’s at [1]?
>
> Thanks,
> Justin
>
> 1. https://storage.googleapis.com/google-code-archive-
> downloads/v2/code.google.com/closureidl/svg.js
>
>
>
>

Re: [FlexJS] Layout Issue/Change

Without having looked at every layout, it does make sense to me that
LayoutBase should not need to watch children for size changes on the JS
side.  That's because the browser already has installed those listeners
and will re-calculate the layout as needed.  The SWF-side will continue to
need to watch the children since there is no runtime support for layout.

Even on the JS side, some layouts still need to "visit the children".
Basic needs to set position:absolute, the old VerticalLayout will set
display:block.  When is the right time to do that is up to the layout.
childrenAdded is a good time.

And even on the JS side, someone should still be allowed to write a layout
that doesn't rely on CSS and needs to visit the children and watch for
size changes in the children.

It is true that having display objects dispatch size changing events when
nobody is listening is wasteful.  There might be fancier ways for us to
make that more PAYG on the JS-side, but I don't think that is a priority
right now.

The original vision for "layoutNeeded" event is for "other scenarios".
That's why there is a LayoutChangeNotifier that allows you to set a
binding expression to trigger a layoutNeeded somewhere else when a
component's property changes, so we don't waste as much code watching for
things "just-in-case".

HTH,
-Alex

On 5/1/17, 7:59 AM, "Peter Ent"  wrote:

>The current listeners in LayoutBase (Basic Project) are for the children
>of a component. Right now, if you have a Group with 10 buttons and
>VerticalLayout, and you resize one of those buttons,
>LayoutBase/VerticalLayout will detect that and automatically re-run the
>VerticalLayout algorithm.
>
>What I propose is to eliminate those event listeners on the children. So
>if you resize one of the buttons you will have dispatch "layoutNeeded" on
>the Group to get the VerticalLayout to reformat the Group.
>
>If you resize the Group, that will continue to re-run the layout.
>
>Another example is FirstFlexibleChildHorizontalLayout (or whatever that's
>called). If you delete that first child, the layout will not run. My
>change will not affect this situation - you must still dispatch
>"layoutNeeded" to get the layout to recalculate the next child as the
>flexible item. On the JS side, this is crucial because this layout sets
>flex-grow:1 on the first child and flex-grow:0 on the rest. When you
>remove the first child, all children have flex-grow:0, so you must re-run
>the layout.
>
>This is the inconsistency: sometimes you need to dispatch "layoutNeeded"
>and sometimes you do not. I propose you always dispatch "layoutNeeded"
>whenever you add a child, remove a child, resize a child, or do anything
>that would require the layout to run.
>
>‹peter
>
>On 5/1/17, 10:27 AM, "piotrz"  wrote:
>
>>Hi Peter,
>>
>>It look like we have partially implemented "layoutNeeded".
>>
>>Your suggestion in #1 - is to completely remove current listeners which
>>are
>>dispatch "layoutNeeded". - Am I understand correctly ? - So if I will add
>>children later - those will resize itself, but in order to correct parent
>>resizing it will need to dispatch "layoutNeeded" ? Am I understand
>>correctly
>>?
>>
>>In case of #2 and #3 - I think both cases are good for express
>>components,
>>but Option #3 seems to me to complicated in case of later usage.
>>
>>Piotr
>>
>>
>>
>>-
>>Apache Flex PMC
>>piotrzarzyck...@gmail.com
>>--
>>View this message in context:
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fl
>>e
>>x-development.247.n4.nabble.com%2FFlexJS-Layout-Issue-Change-tp61440p
>>6
>>1442.html=02%7C01%7C%7C3f4bcd255fbb43120cbc08d4909fcd58%7Cfa7b1b5a7b
>>3
>>4438794aed2c178decee1%7C0%7C0%7C636292463395237341=stp%2Fct7tHsUCkn
>>8
>>X5ZeFclHxbyIal3vC%2F5KUoRYin4Y%3D=0
>>Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

Re: [FlexJS, MDL] Null Pointer Exception in HorizontalFlexLayout

OK. I will look at the other layouts and probably do the same for them
where it makes sense.

On 5/1/17, 10:06 AM, "piotrz"  wrote:

>Thank you Peter. That helped. I was thinking about such solution, but
>wasn't
>sure whether it won't break anything. If I'm thinking more about that it
>makes sense do not bother non UIBase component here.
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-MDL-Null-Pointer-Exception-in
>-HorizontalFlexLayout-tp61437p61441.html=02%7C01%7C%7C61b665f8d3134b4
>d5cf708d4909cf543%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63629245119
>9825874=7%2Bpqd%2FKFt%2FRaA%2Bvml%2BcTIspcY2r9iuxYRUcdKegANRg%3D
>erved=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Layout Issue/Change

The current listeners in LayoutBase (Basic Project) are for the children
of a component. Right now, if you have a Group with 10 buttons and
VerticalLayout, and you resize one of those buttons,
LayoutBase/VerticalLayout will detect that and automatically re-run the
VerticalLayout algorithm.

What I propose is to eliminate those event listeners on the children. So
if you resize one of the buttons you will have dispatch "layoutNeeded" on
the Group to get the VerticalLayout to reformat the Group.

If you resize the Group, that will continue to re-run the layout.

Another example is FirstFlexibleChildHorizontalLayout (or whatever that's
called). If you delete that first child, the layout will not run. My
change will not affect this situation - you must still dispatch
"layoutNeeded" to get the layout to recalculate the next child as the
flexible item. On the JS side, this is crucial because this layout sets
flex-grow:1 on the first child and flex-grow:0 on the rest. When you
remove the first child, all children have flex-grow:0, so you must re-run
the layout.

This is the inconsistency: sometimes you need to dispatch "layoutNeeded"
and sometimes you do not. I propose you always dispatch "layoutNeeded"
whenever you add a child, remove a child, resize a child, or do anything
that would require the layout to run.

‹peter

On 5/1/17, 10:27 AM, "piotrz"  wrote:

>Hi Peter,
>
>It look like we have partially implemented "layoutNeeded".
>
>Your suggestion in #1 - is to completely remove current listeners which
>are
>dispatch "layoutNeeded". - Am I understand correctly ? - So if I will add
>children later - those will resize itself, but in order to correct parent
>resizing it will need to dispatch "layoutNeeded" ? Am I understand
>correctly
>?
>
>In case of #2 and #3 - I think both cases are good for express components,
>but Option #3 seems to me to complicated in case of later usage.
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-Layout-Issue-Change-tp61440p6
>1442.html=02%7C01%7C%7C3f4bcd255fbb43120cbc08d4909fcd58%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636292463395237341=stp%2Fct7tHsUCkn8
>X5ZeFclHxbyIal3vC%2F5KUoRYin4Y%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0

2017-05-01 Thread Christofer Dutz

But in general, “mvn clean compile” should have worked. I even double checked 
with the debugger … if the other modules are part of the build it would 
acutally resolve the artifacts from the target directories instead of from the 
maven local repo … I’ll continue investigating this.

Chris

Am 30.04.17, 23:42 schrieb "Justin Mclean" :

Hi,

> You are running “mvn clean compile” which compiles each module and 
created the swcs in the target directories. Unfortunately, they just stay there 
as they are not copied to your maven local repository.

Thanks Chris that would explain the error.

> To do that, you need to run “mvn clean install”. I would give that a try.

Looks like typedef is now broken as I’m getting this:

[INFO] --- exec-maven-plugin:1.5.0:exec (patch-js) @ flexjs-typedefs-js ---
error: patch failed: js/target/downloads/svg.js:401
error: js/target/downloads/svg.js: patch does not apply
[ERROR] Command execution failed.

I’m assume the patch file no longer matches what’s at [1]?

Thanks,
Justin

1. 
https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/closureidl/svg.js

Re: [FlexJS] Layout Issue/Change

Hi Peter,

It look like we have partially implemented "layoutNeeded".

Your suggestion in #1 - is to completely remove current listeners which are
dispatch "layoutNeeded". - Am I understand correctly ? - So if I will add
children later - those will resize itself, but in order to correct parent
resizing it will need to dispatch "layoutNeeded" ? Am I understand correctly
?

In case of #2 and #3 - I think both cases are good for express components,
but Option #3 seems to me to complicated in case of later usage.  

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Layout-Issue-Change-tp61440p61442.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS, MDL] Null Pointer Exception in HorizontalFlexLayout

Thank you Peter. That helped. I was thinking about such solution, but wasn't
sure whether it won't break anything. If I'm thinking more about that it
makes sense do not bother non UIBase component here.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Null-Pointer-Exception-in-HorizontalFlexLayout-tp61437p61441.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

[FlexJS] Layout Issue/Change

Hi,

My main goal of the recent set of changes to containers and layouts was to make 
the HTML/CSS/JS side as minimal as possible, letting the browser and friends 
take care of things as much as possible. For the most part, I think it works.  
But there is an issue that has been bothering me.

Right now, the LayoutBase class sets up event listeners on the layout host to 
automatically re-run the layout under certain conditions. The more I think 
about this the less PAYG it is and it is also inconsistent how things are 
handled.

The layout code is set up to recognize changes in the layout host's size. When 
that happens the layout is re-run. That, to me, is a good thing.

The layout code also waits for the initial "childrenAdded" event and if it sees 
it, the layout code will set event listeners for size changes on the children. 
If you later add children, those new children may not have listeners attached 
(this is an inconsistency). It is the responsibility of the app developer to 
dispatch a "layoutNeeded" event on the layout host to trigger the layout. 
Again, this is inconsistent as a component could dispatch "childrenAdded" while 
another component may not.

I see three possibilities here:


  1.  Do nothing with children (PAYG). The layout code would listen for size 
changes to the layout host, but it would not set up listeners on the children. 
An application that changes an items size or adds or removes an item will have 
to dispatch "layoutNeeded" on the item's (or items') parent. This way you can 
change a component frequently and only trigger its layout when the changes are 
complete.
  2.  Do everything (Pay Heavily). The layout code would really try to listen 
for all sorts of events on the layout host and respond to them.  The cost would 
be high however, if a large number of items were being changed inside of a 
loop: the layout code would be run for each pass of the loop.
  3.  Do everything, but wait (Partial Payment). The layout code would do the 
same as #2, but allow for updating loops. A number of systems have this: 
host.beginUpdate(); /* do a bunch of things */ host.endUpdate(). While the loop 
is running the layout would ask the host if it is OK to update and if not, the 
layout would not run. Once the endUpdate() was executed, the host would 
dispatch a final "layoutNeeded" and the layout would run once.

I am in favor of #1. It is in the spirit of PAYG and if you decided you needed 
either #2 or #3, you could extend a layout and build that yourself. Or we could 
add it to the Express package or something like that.

In choice 1, changing an item's size trigger's its own layout. If you have a 
Group with 100 elements, all of which are Groups themselves, and you were to 
resize each sub-Group in a loop, the resize of a sub-Group would trigger its 
layout. This is desired behavior. Once that loop has completed, the outer Group 
would also need its layout run to account of the newly resized children and 
that's where you do: outer.dispatchEvent(new Event("layoutNeeded")); In choice 
2 or choice 3, each time a sub-Group was resized, the outer Group's layout 
would run for a total of 100 times, which may even cause some of the 
sub-Group's layouts to run again, depending on the layout algorithm.

If I were to remove the child event listeners in the layout code, any place 
your app or example that counted on the layout running, you would need to add a 
dispatch event for "layoutNeeded" if you did not resize the component.

I hope that made sense.
Peter

Re: [FlexJS, MDL] Null Pointer Exception in HorizontalFlexLayout

Hi Piotr,

I mostly understand. It seems like the child is not UIBase so it is null,
at least in one of the cases. The layout code should be changed to check
for null and skip that child.  Can you see if that helps?

‹peter

On 5/1/17, 8:35 AM, "piotrz"  wrote:

>Hi Peter,
>
>During creation of DropDownList component in MDL I have experienced Null
>Pointer Exception in HorizontalFlexLayout. [1]
>
>Issue:
>My DropDownList contains 3 elements: Div with selected text, Material icon
>(i) and Menu.
>
>Case 1: If I create DropDownList in MXML - MDL library handle properly
>upgrading. 
>
>Menu is a simple ul, but once upgrade is done MDL library surround it by
>additional div [2] "mdl-menu__container".
>
>HorizontalFlexLayout is going through the children of View in function
>"layout". Array contains 3 elements from my DropDownList - the last one is
>menu - in moment of layout perform it contains "ul" not
>"mdl-menu__container".
>
>ex-development.247.n4.nabble.com%2Ffile%2Fn61437%2Fhorizontalflex_layo
>ut.png=02%7C01%7C%7C92f8ef48e030413571a708d490902c50%7Cfa7b1b5a7b3443
>8794aed2c178decee1%7C0%7C0%7C636292396295241298=TTsjYE1G7SohYeujGKKB
>DvIAC7JYha3fPcUbkF4TbaY%3D=0>
>
>This "ul" has been created by FlexJS and has element.flexjs_wrapper. and
>function getElementAt returns child one by one.
>
>Case 2 - ISSUE:
>
>I would like to create DropDownList dynamically:
>
>var dropDown:DropDownList = new DropDownList();
>addElement(dropDown);
>
>In order to do this Menu inside DropDownList need to be "upgraded"
>manually
>- I need to tell MDL library that I've created Menu component - I have
>bead
>for that purpose which doing his job: UpgradeElement.
>
>Upgrade is completed successfully and MDL is surrounding "ul" by
>"mdl-menu__container".
>
>Now HorizontalFlexLayout is doing "layout" and trying to go through the
>children. In array for some reason there is no "ul" MDL Menu, but this
>"mdl-menu__container" which wasn't created by FlexJS. In that case it
>doesn't have element.flexjs_wrapper, so getElementAt returns null. And we
>are getting NPE.
>
>It look like everything what HorizontalFlexLayout is doing in Case 1
>happened before upgrading - in case 2 I'm doing upgrade during whole life
>cycle performance.
>
>I hope this long explanation help you understand issue and provide some
>feedback. I'm attaching simple project where you can reproduce this issue
>[3]
>
>[1] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apa
>che.org%2F9oRP=02%7C01%7C%7C92f8ef48e030413571a708d490902c50%7Cfa7b1b
>5a7b34438794aed2c178decee1%7C0%7C0%7C636292396295241298=O3iz6XdYaDIO
>6408JrznUhIN%2BU3oiBC2U4eqj4rMTsE%3D=0
>[2] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apa
>che.org%2FiN4K=02%7C01%7C%7C92f8ef48e030413571a708d490902c50%7Cfa7b1b
>5a7b34438794aed2c178decee1%7C0%7C0%7C636292396295241298=6ur7OO4g%2Fi
>Sj1IFmWpfJDMwNvQk6PfbuEM2yfackVlE%3D=0
>[3] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2F1drv.ms%2
>Fu%2Fs!ApVpLyjpHDC2zTehS-kv_1g0cgSY=02%7C01%7C%7C92f8ef48e030413571a7
>08d490902c50%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6362923962952412
>98=wnCIo8EFiKQLZFZVLRMcj%2Fnqg1G1Kwb%2BMJPhN6x1ltE%3D=0
>
>Piotr
>
> 
>
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-MDL-Null-Pointer-Exception-in
>-HorizontalFlexLayout-tp61437.html=02%7C01%7C%7C92f8ef48e030413571a70
>8d490902c50%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63629239629524129
>8=FMk2TnkFIbtdFUEg0ifVD3X%2FmDZq%2BmMoQe2o4RyIi1Y%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0

2017-05-01 Thread Christofer Dutz

Well you could try deleting “{maven-local-repo-dir}/.cache” directory as this 
is where the maven-download-plugin downloads and caches downloads.

Chris

Am 01.05.17, 07:19 schrieb "Justin Mclean" :

Hi,

> What commands did you try?

 mvn clean install 

I also tried:
rm ./js/target/downloads/svg.js

And then clean install no luck.

I also tried downloading the file and manually applying the git patch but 
that also failed.

Hereteh has of the download - perhaps check if it matches yours?
MD5 (./js/target/downloads/svg.js) = 127dd144c7954427dd3d4186b3f8dc2c

Thanks,
Justin

[FlexJS, MDL] Null Pointer Exception in HorizontalFlexLayout

Hi Peter,

During creation of DropDownList component in MDL I have experienced Null
Pointer Exception in HorizontalFlexLayout. [1]

Issue:
My DropDownList contains 3 elements: Div with selected text, Material icon
(i) and Menu.

Case 1: If I create DropDownList in MXML - MDL library handle properly
upgrading.

Menu is a simple ul, but once upgrade is done MDL library surround it by
additional div [2] "mdl-menu__container".

HorizontalFlexLayout is going through the children of View in function
"layout". Array contains 3 elements from my DropDownList - the last one is
menu - in moment of layout perform it contains "ul" not
"mdl-menu__container".

This "ul" has been created by FlexJS and has element.flexjs_wrapper. and
function getElementAt returns child one by one.

Case 2 - ISSUE:

I would like to create DropDownList dynamically:

var dropDown:DropDownList = new DropDownList();
addElement(dropDown);

In order to do this Menu inside DropDownList need to be "upgraded" manually
- I need to tell MDL library that I've created Menu component - I have bead
for that purpose which doing his job: UpgradeElement.

Upgrade is completed successfully and MDL is surrounding "ul" by
"mdl-menu__container".

Now HorizontalFlexLayout is doing "layout" and trying to go through the
children. In array for some reason there is no "ul" MDL Menu, but this
"mdl-menu__container" which wasn't created by FlexJS. In that case it
doesn't have element.flexjs_wrapper, so getElementAt returns null. And we
are getting NPE.

It look like everything what HorizontalFlexLayout is doing in Case 1
happened before upgrading - in case 2 I'm doing upgrade during whole life
cycle performance.

I hope this long explanation help you understand issue and provide some
feedback. I'm attaching simple project where you can reproduce this issue
[3]

[1] https://paste.apache.org/9oRP
[2] https://paste.apache.org/iN4K
[3] https://1drv.ms/u/s!ApVpLyjpHDC2zTehS-kv_1g0cgSY

Piotr

-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Null-Pointer-Exception-in-HorizontalFlexLayout-tp61437.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

[FlexJS, MDL] DropDownList component

Hi,

I just added to MDL library DropDownList component. It utilize existing Menu
and use material icon MaterialIconType.ARROW_DROP_DOWN as drop down arrow.

MDLExample project has been updated with usage of this component [1] and you
can check it live [2] it's last tab: Drop Down List. 

During implementation I have found one issue with layout and css - I will
try to report it in separate thread.

[1]
https://github.com/apache/flex-asjs/blob/develop/examples/flexjs/MDLExample/src/main/flex/DropDownList.mxml
[2] https://goo.gl/EXXNKi

Piotr





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

Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0