Re: ant all failing (was Compiling Royale Libraries with Flash Builder (SWF))

[Alex Harui]

Please try to provide relevant information so we don't have trade more
emails getting it.  The test failure details should be in
compiler\target\junit-results in an xml file that has ASExpressionTests in
the name.

And we don't know what your environment variables are set to.

Also, we don't know if you are starting from a fresh clone or this is a
re-build.

Thanks,
-Alex

On 1/8/18, 11:13 PM, "Yishay Weiss"  wrote:

>Getting this console output.
>
>>tests:
>>
>>[mkdir] Created dir:
>>C:\dev\flexjs\royale-compiler\compiler\target\junit-reports
>>
>>[mkdir] Created dir:
>>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp
>>
>>[junit] Running as.ASExpressionTests
>>
>>[junit] looking for C:\dev\flexjs\royale-compiler\env.properties
>>
>>[junit] environment property - FLEX_HOME = C:\dev\flexjs\flex-sdk
>>
>>[junit] environment property - PLAYERGLOBAL_HOME = C:\dev\flashplayer
>>
>>[junit] environment property - PLAYERGLOBAL_VERSION = 11.1
>>
>>[junit] environment property - TLF_HOME = null
>>
>>[junit] environment property - AIR_HOME = C:\dev\flexjsbuilds\nightly
>>
>>[junit] environment property - FLASHPLAYER_DEBUGGER = null
>>
>>[junit] environment property - ASJS_HOME = C:\dev\flexjs\royale-asjs
>>
>>[junit] environment property - GOOG_HOME =
>>C:\dev\flexjsbuilds\nightly/js/lib/google/closure-library
>>
>>[junit] Generating test:
>>
>>[junit] Compiling test:
>>
>>[junit]
>>-external-library-path=C:\dev\flashplayer\11.1\playerglobal.swc
>>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTest
>>s
>>8263907973881887007.as
>>
>>[junit]
>>
>>[junit] 783 bytes written to
>>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTest
>>s
>>8263907973881887007.swf in 1.182 seconds
>>
>>[junit] After compile:
>>
>>[junit] Unexpected compilation problems:
>>
>>[junit]
>>
>>[junit] Generating test:
>>
>>[junit] Compiling test:
>>
>>[junit]
>>-external-library-path=C:\dev\flashplayer\11.1\playerglobal.swc
>>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTest
>>s
>>5673153471287683621.as
>>
>>[junit]
>>
>>[junit] 767 bytes written to
>>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTest
>>s
>>5673153471287683621.swf in 0.578 seconds
>>
>>[junit] After compile:
>>
>>[junit] Unexpected compilation problems:
>>
>>[junit]
>>
>>[junit] Generating test:
>>
>>[junit] Compiling test:
>>
>>[junit]
>>-external-library-path=C:\dev\flashplayer\11.1\playerglobal.swc
>>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTest
>>s
>>6206048447772149132.as
>>
>>[junit]
>>
>>[junit] 857 bytes written to
>>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTest
>>s
>>6206048447772149132.swf in 0.582 seconds
>>
>>[junit] After compile:
>>
>>[junit] Unexpected compilation problems:
>>
>>[junit]
>>
>>[junit] Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time
>>elapsed: 2.922 sec
>>
>>[junit] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
>>
>>
>>
>>BUILD FAILED
>>
>>C:\dev\flexjs\royale-asjs\build.xml:1752: The following error occurred
>>while executing this line:
>>
>>C:\dev\flexjs\royale-asjs\build.xml:1823: The following error occurred
>>while executing this line:
>>
>>C:\dev\flexjs\royale-compiler\build.xml:80: The following error occurred
>>while executing this line:
>>
>>C:\dev\flexjs\royale-compiler\compiler\build.xml:711: The following error
>>occurred while executing this line:
>>
>>C:\dev\flexjs\royale-compiler\compiler\src\test\build.xml:307: Tests
>>failed
>>
>>
>>
>>Total time: 8 minutes 20 seconds
>>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Alex Harui]

On 1/8/18, 11:23 PM, "Piotr Zarzycki"  wrote:

>Alex,
>
>Agree with you for the tests with Maven Artifacts, but definitely I'm with
>Om in case of failing tests. Unless there is some lot's of fixes there.

A failing test may not be a major problem if it is only failing for a
minority of people and there is some workaround.  It is important to
understand how many people are affected by any particular problem.  I
believe tests are passing on builds.a.o.  They just passed for me on OS X.
 I will try myself on Windows tonight or tomorrow.  Did those tests pass
for you?

-Alex

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Justin Mclean]

Hi,

> See https://github.com/google/material-design-lite/blob/mdl-1.x/README.md
> 
> Google has relicensed as AL 2. See the bottom.

At https://github.com/google/material-design-lite/blob/mdl-1.x/LICENSE at the 
bottom it states:

 All code in any directories or sub-directories that end with *.html or
   *.css is licensed under the Creative Commons Attribution International
   4.0 License, which full text can be found here:
   https://creativecommons.org/licenses/by/4.0/legalcode.

That doesn't explicitly help with the images and icons in question but does 
show that it has mixed licensing.

When they did change the license in order to change those images license they 
would of needed permission of the original copyright holders to do so. I guess 
that may of happened.  Do you know if it documented anywhere?

Looking through the issue on their github I found this open issue [1] and this 
[2] (mentioned before). In closed issues they state their code is ALv2 licensed 
[3], this [4] confirms it ALv2 and CC for the icons, but I couldn't find 
anything more re the images.

Thanks,
Justin

1. https://github.com/google/material-design-lite/issues/5017
2. https://github.com/google/material-design-lite/issues/4857
3. https://github.com/google/material-design-lite/issues/4796
4. https://github.com/google/material-design-lite/issues/4132

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Alex Harui]

Might be better to just discuss problems in this thread before voting -1
so we can understand the severity of the problem.  I want us to have a
philosophy that problems have to be pretty severe or a bad break of
something that worked before in order to hold up a release.  We want an
efficient release process and anything that can wait for the next release
should.

Your console output is rather strange, and I believe this test has passed
on Windows on build.a.o, so it may not be a major problem in the source
package itself.

The interesting part of your console output is this:

Running aa.AAAMavenTestExternc
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.881 sec
- in aa.AAAMavenTestExternc
Running aa.AAMavenTestSWCs
...
C:\temp\royale-rc1\apache-royale-0.9.0-src\royale-compiler\compiler\target\
compile-as-config.xml(30): col: 0 Error: unable to open
'C:\temp\royale-rc1\apache-royale-0.9.0-src\royale-compiler\compiler-extern
c\target\js.swc'.
...
290655 bytes written to
C:\temp\royale-rc1\apache-royale-0.9.0-src\royale-compiler\compiler-externc
\target\js.swc in 7.039 seconds
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.73 sec
<<< FAILURE! - in aa.AAMavenTestSWCs


What is interesting is that aa.AAAMavenTestExternc generates a js.swc file
that aa.AAMavenTestSWCs doesn't find so it fails.  But somehow
aa.AAMavenTestSWCs is being run before the console output shows that
290655 bytes were written out as js.swc!

I don't think we've configured the tests to run in parallel.  Can you
investigate to see if we are running tests in parallel or if there is
something else delaying the output of the js.swc?  I believe I have seen
Windows anti-virus programs screw up the timing of when things get written
out.

Thanks,
-Alex

On 1/8/18, 10:24 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
 wrote:

>As mentioned in the VOTE thread, I had unit tests failing while building
>the compiler with Maven.  The full console log is available here [1]
>
>Thanks,
>Om
>
>[1] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.gith
>ub.com%2Fanonymous%2F146e95749626a54dd2a6a2937c9591c0&data=02%7C01%7Caharu
>i%40adobe.com%7Cceb80d997c9e471a09f608d55729c251%7Cfa7b1b5a7b34438794aed2c
>178decee1%7C0%7C0%7C636510759229586647&sdata=siX7PVVjIeADiZBU1ijtSyY03tJtQ
>AyC4L92XzGSQ%2Fk%3D&reserved=0
>
>On Mon, Jan 8, 2018 at 10:14 PM, Olaf Krueger 
>wrote:
>
>> I'll try to do test it tonight but I am not sure if I had already use
>>maven
>> with my current machine... I will check it out.
>>
>> >3) Place following file template to the folder with your pom.xml [1]
>>
>> I guess this should be namend as settings-template.xml?
>>
>> Thanks,
>> Olaf
>>
>>
>>
>>
>>
>> --
>> Sent from: 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-ro
>>yale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com
>>%7Cceb80d997c9e471a09f608d55729c251%7Cfa7b1b5a7b34438794aed2c178decee1%7C
>>0%7C0%7C636510759229586647&sdata=QiF5DrFuBJ8shGp0mEJhqic%2BHIqx4lSHx91Ekh
>>WQMGY%3D&reserved=0
>>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Piotr Zarzycki]

Alex,

Agree with you for the tests with Maven Artifacts, but definitely I'm with
Om in case of failing tests. Unless there is some lot's of fixes there.

I hope Olaf won't have any problems. :)

Thanks, Piotr

2018-01-09 8:03 GMT+01:00 Alex Harui :

> That's fine for Olaf to try, but again, we don't want to nitpick the
> release process and slow things up.  If it worked for you, that should be
> good enough for this first release, and if Olaf has trouble, we fix it for
> the next release.
>
> Thanks,
> -Alex
>
> On 1/8/18, 10:36 PM, "Piotr Zarzycki"  wrote:
>
> >Olaf,
> >
> >I'm glad that you haven't use it - This is the test which I would like to
> >see. How does that work on the clean machine. Of course you will need to
> >download and install Maven first. :)
> >As for the name of template it doesn't matter, you can specify it in your
> >command if you name it differently: "mvn clean install -s
> >settings-template.xml"
> >
> >Thanks, Piotr
> >
> >
> >2018-01-09 7:14 GMT+01:00 Olaf Krueger :
> >
> >> I'll try to do test it tonight but I am not sure if I had already use
> >>maven
> >> with my current machine... I will check it out.
> >>
> >> >3) Place following file template to the folder with your pom.xml [1]
> >>
> >> I guess this should be namend as settings-template.xml?
> >>
> >> Thanks,
> >> Olaf
> >>
> >>
> >>
> >>
> >>
> >> --
> >> Sent from:
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fapache-ro
> >>yale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%
> 40adobe.com
> >>%7C1573ec6823fb43883b6108d5572b6638%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C
> >>0%7C0%7C636510766287922994&sdata=O0m0Xc0zsv%
> 2FrCsTUkgX6xGyO6rEy0cof7UYZ0M
> >>AyTd8%3D&reserved=0
> >>
> >
> >
> >
> >--
> >
> >Piotr Zarzycki
> >
> >Patreon:
> >*https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.patr
> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> 7C1573ec6823fb43
> >883b6108d5572b6638%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6365107662
> >87922994&sdata=iu6j0QNQ7yvgHmodOQrD4zZM7%2BNhHP59gWuKL5wD63A%3D&
> reserved=0
> > https%3A%2F%2Fwww.patr
> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> 7C1573ec6823fb43
> >883b6108d5572b6638%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6365107662
> >87922994&sdata=iu6j0QNQ7yvgHmodOQrD4zZM7%2BNhHP59gWuKL5wD63A%3D&
> reserved=0
> >>*
>
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Dave Fisher]

Hi Justin,

I was doing my research.

See https://github.com/google/material-design-lite/blob/mdl-1.x/README.md

Google has relicensed as AL 2. See the bottom.

Regards,
Dave

Sent from my iPhone

> On Jan 8, 2018, at 11:10 PM, Justin Mclean  wrote:
> 
> Hi,
> 
>> Those files come from here [1]
>> 
>> [1] https://getmdl.io/templates/index.html
> 
> Thanks, do you know how they are licensed?
> 
> I can see there’s an open issue reguarding licensing of these files. [1] The 
> original check in doesn’t help much [2] other than the icons seem to be under 
> an CCSA 4.0 international license. Have we altered the icons in any way?
> 
> Doing a reverse google image search on the road image [5] (which looks like a 
> professional stock photo to me) turns up a number if hits, but I would guess 
> it may of come from here [4] as that is one of the hits that predates the 
> original checkin. There it’s stated that the image is CC0 but it doesn’t give 
> the author and it’s unknown who uploaded it. (The free photos account seems 
> to be a catch all). So best case it seems it may be CC0 but it probably is of 
> unknown IP provenance. Note that it appears in several paid commercial 
> themes, I’ve not checked them all but the few I did see to come after that 
> checkin so they may of copied it from there. Can anyone find out anything 
> else about any of that (or others) images origins?
> 
> I’ve not investigated the other images.
> 
> To resolve we could:
> a) Found out where each image come form and what license it’s under.
> b) We may need to ask Alexander Surma (su...@surmair.de) who checked in the 
> images where they where obtained from and what license they were under. (And 
> if it was [4] ask pixabay where they got it from.)
> c) Ask for that issue [1] to be resolved (and give provenance for each image).
> d) Replace the images and icons with something of known IP provenance.
> 
> What do you think? To me d) seems the simplest and quickest option and would 
> require no changes to the existing LICENSE.
> 
> Thanks.
> Justin
> 
> 1. https://github.com/google/material-design-lite/issues/4857
> 2. 
> https://github.com/google/material-design-lite/commit/2cab1e730699b1a650c4f74300939f9d66b16128#diff-f8c098de9d518711322490fec27fcd27
> 3. 
> https://github.com/google/material-design-lite/blob/2cab1e730699b1a650c4f74300939f9d66b16128/templates/fonts/LICENSE.txt
> 4. https://pixabay.com/en/person-male-man-looking-sitting-60/
> 5. 
> https://github.com/apache/royale-asjs/blob/develop/examples/royale/MDLBlogExample/src/main/resources/images/road_big.jpg

ant all failing (was Compiling Royale Libraries with Flash Builder (SWF))

[Yishay Weiss]

Getting this console output.

>tests:
>
>[mkdir] Created dir:
>C:\dev\flexjs\royale-compiler\compiler\target\junit-reports
>
>[mkdir] Created dir:
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp
>
>[junit] Running as.ASExpressionTests
>
>[junit] looking for C:\dev\flexjs\royale-compiler\env.properties
>
>[junit] environment property - FLEX_HOME = C:\dev\flexjs\flex-sdk
>
>[junit] environment property - PLAYERGLOBAL_HOME = C:\dev\flashplayer
>
>[junit] environment property - PLAYERGLOBAL_VERSION = 11.1
>
>[junit] environment property - TLF_HOME = null
>
>[junit] environment property - AIR_HOME = C:\dev\flexjsbuilds\nightly
>
>[junit] environment property - FLASHPLAYER_DEBUGGER = null
>
>[junit] environment property - ASJS_HOME = C:\dev\flexjs\royale-asjs
>
>[junit] environment property - GOOG_HOME =
>C:\dev\flexjsbuilds\nightly/js/lib/google/closure-library
>
>[junit] Generating test:
>
>[junit] Compiling test:
>
>[junit]
>-external-library-path=C:\dev\flashplayer\11.1\playerglobal.swc
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests
>8263907973881887007.as
>
>[junit]
>
>[junit] 783 bytes written to
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests
>8263907973881887007.swf in 1.182 seconds
>
>[junit] After compile:
>
>[junit] Unexpected compilation problems:
>
>[junit]
>
>[junit] Generating test:
>
>[junit] Compiling test:
>
>[junit]
>-external-library-path=C:\dev\flashplayer\11.1\playerglobal.swc
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests
>5673153471287683621.as
>
>[junit]
>
>[junit] 767 bytes written to
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests
>5673153471287683621.swf in 0.578 seconds
>
>[junit] After compile:
>
>[junit] Unexpected compilation problems:
>
>[junit]
>
>[junit] Generating test:
>
>[junit] Compiling test:
>
>[junit]
>-external-library-path=C:\dev\flashplayer\11.1\playerglobal.swc
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests
>6206048447772149132.as
>
>[junit]
>
>[junit] 857 bytes written to
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests
>6206048447772149132.swf in 0.582 seconds
>
>[junit] After compile:
>
>[junit] Unexpected compilation problems:
>
>[junit]
>
>[junit] Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time
>elapsed: 2.922 sec
>
>[junit] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
>
>
>
>BUILD FAILED
>
>C:\dev\flexjs\royale-asjs\build.xml:1752: The following error occurred
>while executing this line:
>
>C:\dev\flexjs\royale-asjs\build.xml:1823: The following error occurred
>while executing this line:
>
>C:\dev\flexjs\royale-compiler\build.xml:80: The following error occurred
>while executing this line:
>
>C:\dev\flexjs\royale-compiler\compiler\build.xml:711: The following error
>occurred while executing this line:
>
>C:\dev\flexjs\royale-compiler\compiler\src\test\build.xml:307: Tests
>failed
>
>
>
>Total time: 8 minutes 20 seconds
>

RE: Compiling Royale Libraries with Flash Builder (SWF)

[Yishay Weiss]

Opened a new thread, the current topic is misleading. Thanks.




From: Alex Harui 
Sent: Monday, January 8, 2018 7:18:33 PM
To: dev@royale.apache.org
Subject: Re: Compiling Royale Libraries with Flash Builder (SWF)

Yishay,

I'm not clear what you are trying to do.  How did you get compiler JUNIT
tests to run from Flash Builder?

-Alex

On 1/8/18, 1:18 AM, "Yishay Weiss"  wrote:

>It wasn’t set. Now that I’ve set it I’m getting this:
>
>
>
>tests:
>
>[mkdir] Created dir:
>C:\dev\flexjs\royale-compiler\compiler\target\junit-reports
>
>[mkdir] Created dir:
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp
>
>[junit] Running as.ASExpressionTests
>
>[junit] looking for C:\dev\flexjs\royale-compiler\env.properties
>
>[junit] environment property - FLEX_HOME = C:\dev\flexjs\flex-sdk
>
>[junit] environment property - PLAYERGLOBAL_HOME = C:\dev\flashplayer
>
>[junit] environment property - PLAYERGLOBAL_VERSION = 11.1
>
>[junit] environment property - TLF_HOME = null
>
>[junit] environment property - AIR_HOME = C:\dev\flexjsbuilds\nightly
>
>[junit] environment property - FLASHPLAYER_DEBUGGER = null
>
>[junit] environment property - ASJS_HOME = C:\dev\flexjs\royale-asjs
>
>[junit] environment property - GOOG_HOME =
>C:\dev\flexjsbuilds\nightly/js/lib/google/closure-library
>
>[junit] Generating test:
>
>[junit] Compiling test:
>
>[junit]
>-external-library-path=C:\dev\flashplayer\11.1\playerglobal.swc
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests
>8263907973881887007.as
>
>[junit]
>
>[junit] 783 bytes written to
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests
>8263907973881887007.swf in 1.182 seconds
>
>[junit] After compile:
>
>[junit] Unexpected compilation problems:
>
>[junit]
>
>[junit] Generating test:
>
>[junit] Compiling test:
>
>[junit]
>-external-library-path=C:\dev\flashplayer\11.1\playerglobal.swc
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests
>5673153471287683621.as
>
>[junit]
>
>[junit] 767 bytes written to
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests
>5673153471287683621.swf in 0.578 seconds
>
>[junit] After compile:
>
>[junit] Unexpected compilation problems:
>
>[junit]
>
>[junit] Generating test:
>
>[junit] Compiling test:
>
>[junit]
>-external-library-path=C:\dev\flashplayer\11.1\playerglobal.swc
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests
>6206048447772149132.as
>
>[junit]
>
>[junit] 857 bytes written to
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests
>6206048447772149132.swf in 0.582 seconds
>
>[junit] After compile:
>
>[junit] Unexpected compilation problems:
>
>[junit]
>
>[junit] Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time
>elapsed: 2.922 sec
>
>[junit] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
>
>
>
>BUILD FAILED
>
>C:\dev\flexjs\royale-asjs\build.xml:1752: The following error occurred
>while executing this line:
>
>C:\dev\flexjs\royale-asjs\build.xml:1823: The following error occurred
>while executing this line:
>
>C:\dev\flexjs\royale-compiler\build.xml:80: The following error occurred
>while executing this line:
>
>C:\dev\flexjs\royale-compiler\compiler\build.xml:711: The following error
>occurred while executing this line:
>
>C:\dev\flexjs\royale-compiler\compiler\src\test\build.xml:307: Tests
>failed
>
>
>
>Total time: 8 minutes 20 seconds
>
>
>
>
>
>
>
>
>From: Alex Harui 
>Sent: Monday, January 8, 2018 7:39:15 AM
>To: dev@royale.apache.org
>Subject: Re: Compiling Royale Libraries with Flash Builder (SWF)
>
>What is PLAYERGLOBAL_HOME set to?
>
>-Alex
>
>On 1/7/18, 7:03 AM, "Yishay Weiss"  wrote:
>
>>I think that might have been it but I’m now struggling to get a Royale
>>build working.
>>
>>
>>
>>When trying to build Basic I’m getting
>>
>>
>>
>>C:\dev\flexjs\royale-asjs\frameworks\royale-config.xml(74): col: 0 unable
>>to open 'C:\dev\flexjs\royale-asjs\frameworks\\11.1\playerglobal.swc'.
>>
>>
>>
>>Any pointers would be appreciated…
>>
>>
>>
>>
>>From: Alex Harui 
>>Sent: Tuesday, January 2, 2018 7:05:48 PM
>>To: dev@royale.apache.org
>>Subject: Re: Compiling Royale Libraries with Flash Builder (SWF)
>>
>>In Project/Properties/Flex Build Path dialog, see which SWCs are being
>>used.  If your Royale SDK is/was a JS-Only one, you may be using the JS
>>SWCs during SWF compilation.
>>
>>HTH,
>>-Alex
>>
>>On 1/2/18, 12:42 AM, "Yishay Weiss"  wrote:
>>
>>>I’m getting messages such as
>>>1044: interface method applyImageData in interface IImage not
>>>implemented
>>>by class BinaryImage
>>>
>>>When I look at IImage I see
>>>  COMPILE::JS
>>>  function applyImageData(binaryDataAsString:String):void;
>>>So it looks like the 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Justin Mclean]

Hi,

> Those files come from here [1]
> 
> [1] https://getmdl.io/templates/index.html

Thanks, do you know how they are licensed?

I can see there’s an open issue reguarding licensing of these files. [1] The 
original check in doesn’t help much [2] other than the icons seem to be under 
an CCSA 4.0 international license. Have we altered the icons in any way?

Doing a reverse google image search on the road image [5] (which looks like a 
professional stock photo to me) turns up a number if hits, but I would guess it 
may of come from here [4] as that is one of the hits that predates the original 
checkin. There it’s stated that the image is CC0 but it doesn’t give the author 
and it’s unknown who uploaded it. (The free photos account seems to be a catch 
all). So best case it seems it may be CC0 but it probably is of unknown IP 
provenance. Note that it appears in several paid commercial themes, I’ve not 
checked them all but the few I did see to come after that checkin so they may 
of copied it from there. Can anyone find out anything else about any of that 
(or others) images origins?

I’ve not investigated the other images.

To resolve we could:
a) Found out where each image come form and what license it’s under.
b) We may need to ask Alexander Surma (su...@surmair.de) who checked in the 
images where they where obtained from and what license they were under. (And if 
it was [4] ask pixabay where they got it from.)
c) Ask for that issue [1] to be resolved (and give provenance for each image).
d) Replace the images and icons with something of known IP provenance.

What do you think? To me d) seems the simplest and quickest option and would 
require no changes to the existing LICENSE.

Thanks.
Justin

1. https://github.com/google/material-design-lite/issues/4857
2. 
https://github.com/google/material-design-lite/commit/2cab1e730699b1a650c4f74300939f9d66b16128#diff-f8c098de9d518711322490fec27fcd27
3. 
https://github.com/google/material-design-lite/blob/2cab1e730699b1a650c4f74300939f9d66b16128/templates/fonts/LICENSE.txt
4. https://pixabay.com/en/person-male-man-looking-sitting-60/
5. 
https://github.com/apache/royale-asjs/blob/develop/examples/royale/MDLBlogExample/src/main/resources/images/road_big.jpg

Jenkins build is back to normal : royale-asjs #121

[apacheroyaleci]

See 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Alex Harui]

That's fine for Olaf to try, but again, we don't want to nitpick the
release process and slow things up.  If it worked for you, that should be
good enough for this first release, and if Olaf has trouble, we fix it for
the next release.

Thanks,
-Alex

On 1/8/18, 10:36 PM, "Piotr Zarzycki"  wrote:

>Olaf,
>
>I'm glad that you haven't use it - This is the test which I would like to
>see. How does that work on the clean machine. Of course you will need to
>download and install Maven first. :)
>As for the name of template it doesn't matter, you can specify it in your
>command if you name it differently: "mvn clean install -s
>settings-template.xml"
>
>Thanks, Piotr
>
>
>2018-01-09 7:14 GMT+01:00 Olaf Krueger :
>
>> I'll try to do test it tonight but I am not sure if I had already use
>>maven
>> with my current machine... I will check it out.
>>
>> >3) Place following file template to the folder with your pom.xml [1]
>>
>> I guess this should be namend as settings-template.xml?
>>
>> Thanks,
>> Olaf
>>
>>
>>
>>
>>
>> --
>> Sent from: 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-ro
>>yale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com
>>%7C1573ec6823fb43883b6108d5572b6638%7Cfa7b1b5a7b34438794aed2c178decee1%7C
>>0%7C0%7C636510766287922994&sdata=O0m0Xc0zsv%2FrCsTUkgX6xGyO6rEy0cof7UYZ0M
>>AyTd8%3D&reserved=0
>>
>
>
>
>-- 
>
>Piotr Zarzycki
>
>Patreon: 
>*https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patr
>eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C1573ec6823fb43
>883b6108d5572b6638%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365107662
>87922994&sdata=iu6j0QNQ7yvgHmodOQrD4zZM7%2BNhHP59gWuKL5wD63A%3D&reserved=0
>eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C1573ec6823fb43
>883b6108d5572b6638%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365107662
>87922994&sdata=iu6j0QNQ7yvgHmodOQrD4zZM7%2BNhHP59gWuKL5wD63A%3D&reserved=0
>>*

Re: [Understanding PAYG] Button: Why is there no "text" or "icon" bead in order to compose a TextButton or IconButton?

[Olaf Krueger]

Thanks Alex!



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: [Understanding PAYG] Button: Why is there no "text" or "icon" bead in order to compose a TextButton or IconButton?

[Alex Harui]

Here's one article that is relevant [1]

[1] https://cwiki.apache.org/confluence/display/FLEX/Creating+Components

On 1/8/18, 11:48 AM, "Olaf Krueger"  wrote:

>>We've tried to write up things like this in the FlexJS wiki...
>
>Maybe I've overlooked some articles.
>I just started to move articles to the "FlexJS" category to make sure that
>we don't miss something when we'll move it to Royale...
>
>Thanks,
>Olaf
>
>
>
>--
>Sent from: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy
>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7
>C742c3cbcae74434d4f6308d556d0cc7d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7
>C0%7C636510377141330188&sdata=YlZYxB9WoczVS23472xeFAnGeqXSD3i6wKbwoP33KDQ%
>3D&reserved=0

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Piotr Zarzycki]

Olaf,

I'm glad that you haven't use it - This is the test which I would like to
see. How does that work on the clean machine. Of course you will need to
download and install Maven first. :)
As for the name of template it doesn't matter, you can specify it in your
command if you name it differently: "mvn clean install -s
settings-template.xml"

Thanks, Piotr


2018-01-09 7:14 GMT+01:00 Olaf Krueger :

> I'll try to do test it tonight but I am not sure if I had already use maven
> with my current machine... I will check it out.
>
> >3) Place following file template to the folder with your pom.xml [1]
>
> I guess this should be namend as settings-template.xml?
>
> Thanks,
> Olaf
>
>
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>



-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Piotr Zarzycki]

Justin,

Those files come from here [1]

[1] https://getmdl.io/templates/index.html

Thanks, Piotr

2018-01-09 2:02 GMT+01:00 Justin Mclean :

> Hi,
>
> Does any one know where these files come from and how they are licensed?
> [1]
>
> I quick reverse image search shows several of them to be part of
> commercial web templates, but those templates could of got them from else
> where.
>
> Thanks,
> Justin
>
>
> 1, https://github.com/apache/royale-asjs/tree/develop/examples/royale/
> MDLBlogExample/src/main/resources/images




-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: How to overwrite/change a components' default styles the royale way?

[Alex Harui]

I think I mostly agree with your point.  We want to make styling easy as
possible.  My point was that we have lots of work to do, and sometimes we
have to "settle" for providing the same way of doing things as folks would
do if they didn't use Royale.  So, if you didn't use Royale, chose some
CSS theme like Bootstrap or MaterialDesignLite and wanted to change
something, what would you have to do?   I'm not quite sure what that is,
but I think you may need to know that CSS rules the theme designers used
in order to override them.  I'm not sure you can "un-set" a style defined
in a CSS theme or not.

Now if you have a better idea and can implement it or get a volunteer to
implement it, great.  But for now, I'm going to be happy if the CSS our
users can define can override styles in the SWCs.

My 2 cents,
-Alex

On 1/8/18, 11:19 AM, "Olaf Krueger"  wrote:

>Hmm, I am not sure if we're misunderstood...
>
>I don't want to say that we should go the Flex way or that we need
>something
>like skinning.
>I just would like to say that from my point of view it is important to
>provide a possibility to overwrite CSS  styles in that way, that no
>default
>styles remain in the HTML.
>
>As long as we target HTML I think the easiest way is to just apply
>HTML/CSS3
>styles to change the look and feel of components/elements.
>
>However, maybe I get something wrong... I'll continue for now with
>exploring
>those things... 
>
>Thanks,
>Olaf
>
>
>
>
>
>--
>Sent from: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy
>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7
>Cb7df7d8be61147e0303908d556ccb423%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7
>C0%7C636510359552480505&sdata=15HOLwMdIXqtQDzOyzRNf6fZCbiTTx%2BcgX3NRY%2Bz
>Xtc%3D&reserved=0

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[OmPrakash Muppirala]

As mentioned in the VOTE thread, I had unit tests failing while building
the compiler with Maven.  The full console log is available here [1]

Thanks,
Om

[1] https://gist.github.com/anonymous/146e95749626a54dd2a6a2937c9591c0

On Mon, Jan 8, 2018 at 10:14 PM, Olaf Krueger  wrote:

> I'll try to do test it tonight but I am not sure if I had already use maven
> with my current machine... I will check it out.
>
> >3) Place following file template to the folder with your pom.xml [1]
>
> I guess this should be namend as settings-template.xml?
>
> Thanks,
> Olaf
>
>
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Olaf Krueger]

I'll try to do test it tonight but I am not sure if I had already use maven
with my current machine... I will check it out.

>3) Place following file template to the folder with your pom.xml [1] 

I guess this should be namend as settings-template.xml?

Thanks,
Olaf





--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: [VOTE] Release Apache Royale 0.9.0 RC1

[OmPrakash Muppirala]

-1 Binding

* MD5 matches
* Signature valid
* README, RELEASE_NOTES, NOTICE and LICENSE look good
* Installation via NPM successful
* Able to cross-compile apps successfully with mxml from npm
* royale-compiler>mvn clean install -P -main,utils works fine

royale-compiler>mvn clean install
Unit test failure.

Let's try to fix this unit test before releasing.  More details in the
DISCUSS thread.

Thanks,
Om


On Mon, Jan 8, 2018 at 8:47 PM, OmPrakash Muppirala 
wrote:

> One small correction.  These are the correct npm install commands:
>
> npm install https://dist.apache.org/repos/dist/dev/royale/0.9.0/rc1/
> binaries/apache-royale-jsonly-0.9.0-bin.tar.gz -g
>
> npm install https://dist.apache.org/repos/dist/dev/royale/0.9.0/rc1/
> binaries/apache-royale-0.9.0-bin.tar.gz -g
>
> Thanks,
> Om
>
> On Mon, Jan 8, 2018 at 12:10 AM, Alex Harui 
> wrote:
>
>> Hi,
>>
>> This is vote for the 0.9.0 release of Apache Royale.
>>
>> The release candidate can be found here;
>> https://dist.apache.org/repos/dist/dev/royale/0.9.0/rc1/
>>
>> Before voting please review the section,'What are the ASF requirements on
>> approving a release?', at:
>> http://www.apache.org/dev/release.html#approving-a-release
>>
>> At a minimum you would be expected to check that:
>> - MD5 and signed packages are correct
>> - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
>> - That the build script completes successfully
>> - That you can compile and cross-compile a simple example using the SDK.
>>
>> The source package is a combination of the 3 main Royale repos
>>
>> To use the binary package, unzip it into a folder.  The -js package is
>> ready-to-use in an IDE or command-line.  If you need SWF output, use the
>> -royale package and use Apache Ant to run the InstallAdobeSDKs script via:
>>   ant -f InstallAdobeSDKs.xml
>>
>> You may also get the binary packages via NPM.  The -js package can be
>> installed via:
>>
>> npm install
>> https://dist.apache.org/repos/dist/dev/royale/${release.vers
>> ion}/rc${rc}/bi
>> naries/apache-royale-jsonly-${release.version}-bin.tar.gz
>> 
>> -g
>>
>> The full package with SWF support can be installed via:
>>
>> npm install
>> https://dist.apache.org/repos/dist/dev/royale/${release.vers
>> ion}/rc{rc}/bin
>> aries/apache-royale-${release.version}-bin.tar.gz
>> 
>> -g
>>
>>
>> Please vote to approve this release:
>> +1 Approve the release
>> -1 Disapprove the release (please provide specific comments to why)
>>
>> This vote will be open for 72 hours or until a result can be called.
>>
>> The vote passes if there is:
>> - At least 3 +1 votes from the PMC
>> - More positive votes than negative votes
>>
>> Remember that this is a 'beta-quality' release so I expect there
>> will be many bugs found.  IMO the goal is not to try to find and fix bugs
>> in the RC, but to make sure we have the packaging right, and enough
>> functionality that folks will have some success trying to use it.
>>
>> People who are not in PMC are also encouraged to test out the release and
>> vote, although their votes will not be binding, they can influence how the
>> PMC votes.
>>
>> When voting please indicate what OS, IDE, Flash Player version and AIR
>> version you tested with.
>>
>> For your convenience, there is an ant script that automates the common
>> steps to validate a release.  Instead of individually downloading the
>> package and signature files, unzipping, etc, you can instead:
>> 1) create an empty folder,
>> 2) download into that folder this file:
>> https://dist.apache.org/repos/dist/dev/royale/0.9.0/rc1/ApproveRoyale.xml
>> 3) run the script:
>>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.0 -Drc=1
>>
>> You are not required to use this script, and more testing of the packages
>> and build results are always encouraged.
>>
>>
>> Please put all discussion about this release in the DISCUSSION thread not
>> this VOTE thread.
>>
>> Thanks,
>> Alex Harui
>>
>>
>

Re: [VOTE] Release Apache Royale 0.9.0 RC1

[OmPrakash Muppirala]

One small correction.  These are the correct npm install commands:

npm install
https://dist.apache.org/repos/dist/dev/royale/0.9.0/rc1/binaries/apache-royale-jsonly-0.9.0-bin.tar.gz
-g

npm install
https://dist.apache.org/repos/dist/dev/royale/0.9.0/rc1/binaries/apache-royale-0.9.0-bin.tar.gz
-g

Thanks,
Om

On Mon, Jan 8, 2018 at 12:10 AM, Alex Harui 
wrote:

> Hi,
>
> This is vote for the 0.9.0 release of Apache Royale.
>
> The release candidate can be found here;
> https://dist.apache.org/repos/dist/dev/royale/0.9.0/rc1/
>
> Before voting please review the section,'What are the ASF requirements on
> approving a release?', at:
> http://www.apache.org/dev/release.html#approving-a-release
>
> At a minimum you would be expected to check that:
> - MD5 and signed packages are correct
> - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
> - That the build script completes successfully
> - That you can compile and cross-compile a simple example using the SDK.
>
> The source package is a combination of the 3 main Royale repos
>
> To use the binary package, unzip it into a folder.  The -js package is
> ready-to-use in an IDE or command-line.  If you need SWF output, use the
> -royale package and use Apache Ant to run the InstallAdobeSDKs script via:
>   ant -f InstallAdobeSDKs.xml
>
> You may also get the binary packages via NPM.  The -js package can be
> installed via:
>
> npm install
> https://dist.apache.org/repos/dist/dev/royale/${release.
> version}/rc${rc}/bi
> naries/apache-royale-jsonly-${release.version}-bin.tar.gz -g
>
> The full package with SWF support can be installed via:
>
> npm install
> https://dist.apache.org/repos/dist/dev/royale/${release.
> version}/rc{rc}/bin
> aries/apache-royale-${release.version}-bin.tar.gz -g
>
>
> Please vote to approve this release:
> +1 Approve the release
> -1 Disapprove the release (please provide specific comments to why)
>
> This vote will be open for 72 hours or until a result can be called.
>
> The vote passes if there is:
> - At least 3 +1 votes from the PMC
> - More positive votes than negative votes
>
> Remember that this is a 'beta-quality' release so I expect there
> will be many bugs found.  IMO the goal is not to try to find and fix bugs
> in the RC, but to make sure we have the packaging right, and enough
> functionality that folks will have some success trying to use it.
>
> People who are not in PMC are also encouraged to test out the release and
> vote, although their votes will not be binding, they can influence how the
> PMC votes.
>
> When voting please indicate what OS, IDE, Flash Player version and AIR
> version you tested with.
>
> For your convenience, there is an ant script that automates the common
> steps to validate a release.  Instead of individually downloading the
> package and signature files, unzipping, etc, you can instead:
> 1) create an empty folder,
> 2) download into that folder this file:
> https://dist.apache.org/repos/dist/dev/royale/0.9.0/rc1/ApproveRoyale.xml
> 3) run the script:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.0 -Drc=1
>
> You are not required to use this script, and more testing of the packages
> and build results are always encouraged.
>
>
> Please put all discussion about this release in the DISCUSSION thread not
> this VOTE thread.
>
> Thanks,
> Alex Harui
>
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[OmPrakash Muppirala]

In the VOTE thread, I see these urls for the npm installation:


npm install
https://dist.apache.org/repos/dist/dev/royale/${release.version}/rc${rc}/bi
naries/apache-royale-jsonly-${release.version}-bin.tar.gz -g

The full package with SWF support can be installed via:

npm install
https://dist.apache.org/repos/dist/dev/royale/${release.version}/rc{rc}/bin
aries/apache-royale-${release.version}-bin.tar.gz -g

It should be the actual release.version values filled in, right?

Thanks,
Om

On Mon, Jan 8, 2018 at 8:02 PM, Justin Mclean 
wrote:

> Hi,
>
> Does any one know where these files come from and how they are licensed?
> [1]
>
> I quick reverse image search shows several of them to be part of
> commercial web templates, but those templates could of got them from else
> where.
>
> Thanks,
> Justin
>
>
> 1, https://github.com/apache/royale-asjs/tree/develop/examples/royale/
> MDLBlogExample/src/main/resources/images

Build failed in Jenkins: royale-asjs #120

[apacheroyaleci]

See 


--
[...truncated 927.89 KB...]
 [java] var net = require('net');
 [java]   ^^^
 [java] 
 [java] Jan 09, 2018 4:26:50 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [http]:25: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var stream = require('stream');
 [java]  ^^^
 [java] 
 [java] Jan 09, 2018 4:26:50 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [http]:252: WARNING - name module is not defined in the 
externs.
 [java] module.exports = http;
 [java] ^^
 [java] 
 [java] Jan 09, 2018 4:26:50 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [https]:23: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var http = require('http');
 [java]^^^
 [java] 
 [java] Jan 09, 2018 4:26:50 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [https]:24: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var tls = require('tls');
 [java]   ^^^
 [java] 
 [java] Jan 09, 2018 4:26:50 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [https]:84: WARNING - name module is not defined in the 
externs.
 [java] module.exports = https;
 [java] ^^
 [java] 
 [java] Jan 09, 2018 4:26:50 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [net]:23: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Jan 09, 2018 4:26:50 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [net]:219: WARNING - name module is not defined in the 
externs.
 [java] module.exports = net;
 [java] ^^
 [java] 
 [java] Jan 09, 2018 4:26:50 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [os]:112: WARNING - name module is not defined in the 
externs.
 [java] module.exports = os;
 [java] ^^
 [java] 
 [java] Jan 09, 2018 4:26:50 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [path]:97: WARNING - name module is not defined in the 
externs.
 [java] module.exports = path;
 [java] ^^
 [java] 
 [java] Jan 09, 2018 4:26:50 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [punycode]:74: WARNING - name module is not defined in the 
externs.
 [java] module.exports = punycode;
 [java] ^^
 [java] 
 [java] Jan 09, 2018 4:26:50 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [querystring]:66: WARNING - name module is not defined in 
the externs.
 [java] module.exports = querystring;
 [java] ^^
 [java] 
 [java] Jan 09, 2018 4:26:50 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [readline]:22: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Jan 09, 2018 4:26:50 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [readline]:23: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var stream = require('stream');
 [java]  ^^^
 [java] 
 [java] Jan 09, 2018 4:26:50 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [readline]:84: WARNING - name module is not defined in the 
externs.
 [java] module.exports = readline;
 [java] ^^
 [java] 
 [java] Jan 09, 2018 4:26:50 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [repl]:23: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Jan 09, 2018 4:26:50 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [repl]:24: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var stream = require('stream');
 [java]  ^^^
 [java] 
 [java] Jan 09, 2018 4:26:50 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [repl]:48: WARNING - name module is not defined in the 
externs.
 [java] module.exports = repl;
 [java] ^^^

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Justin Mclean]

Hi,

Does any one know where these files come from and how they are licensed? [1]

I quick reverse image search shows several of them to be part of commercial web 
templates, but those templates could of got them from else where.

Thanks,
Justin


1, 
https://github.com/apache/royale-asjs/tree/develop/examples/royale/MDLBlogExample/src/main/resources/images

Re: [Royale] ICollectionView

[Piotr Zarzycki]

Hi Peter,

Thank you very much. It will definitely help me finish another Big example!
I will check it tomorrow :)

Piotr


2018-01-08 20:29 GMT+01:00 Peter Ent :

> I just pushed some changes that give you a more dynamic DataGrid.
>
> The DataGrid should continue to work normally. But if you want to have it
> respond to items being inserted and removed, then you can use the new
> collection view beads.
>
> I updated DataGridExample to illustrate how to do it PAYG. You change the
> DataGrid's model to the new DataGridCollectionViewModel and then give each
> column the DataItemRendererFactoryForCollectionView via CSS. This way the
> majority of DataGrid uses that just display information will not have the
> extra code required to respond to changes in the dataProvider. But if you
> do use these new beads you can just insert or remove an item and the
> columns in the DataGrid will reflect the changes. The DataGrid should also
> remain selected unless you are removing the selected row.
>
> —peter
>
> On 1/7/18, 7:17 PM, "Peter Ent"  wrote:
>
> >The DataGrid’s model’s dataProvider would be an ICollectionView which
> >gets shared with each column list’s model’s dataProvider.  Changing the
> >data should trigger events to have each list’s
> >DataItemRendereFactoryForCollectionView update the itemRenderers.
> >
> >It should just work but I will be verifying that.
> >
> >Peter
> >
> >
> >> On Jan 7, 2018, at 11:38 AM, Piotr Zarzycki 
> >>wrote:
> >>
> >> Peter,
> >>
> >> When you were saying that :"I had a reasonably working version of
> >>DataGrid
> >> for this..." - Do you mean usage of all that new stuff which helps
> >>sorting
> >> etc ? I'm working on the next example where DataGrid is being used. I
> >>would
> >> like to have also ability to update like we are doing that in list by
> >> "DynamicUpdateItemRendererForArrayListData", but Grid is not a IList,
> >>which
> >> we are expecting in those Beads. What do you think what we should do in
> >> order to achieve that ?
> >>
> >> Thanks, Piotr
> >>
> >>
> >> 2018-01-07 14:35 GMT+01:00 Piotr Zarzycki :
> >>
> >>> Many Thanks!
> >>>
> >>> I just noticed that Grid doesn't have selectedItem property. Not sure
> >>>if
> >>> it was for purpose.
> >>>
> >>> Piotr
> >>>
> >>> 2018-01-07 14:21 GMT+01:00 Peter Ent :
> >>>
>  I did notice that something was happening with the scrollbars. I will
> look
>  into it.
>  ‹peter
> 
> > On 1/6/18, 8:52 AM, "piotrz"  wrote:
> >
> > Hi Peter,
> >
> > Just wanted to let you know that I have started use more extensively
> > DataGrid and I have found that using FlexLayout gives a way better
>  results
> > for DataGrid than VerticalFlexLayout/HorizotnalFlexLayout beads.
> >
> > Ma last commit fixes issue with synchronizing width of column with
> >width
> > of
> > header buttons in DataGrid.
> >
> > However there is one problem with that - Scrollbar. Take a look into
> >the
> > DataGridExample where scrollbar appear. Last column is a bit shifted.
> > Without scrollbar width is perfectly synced.
> >
> >   3A%2F%2Fapache-ro
> > yale-development.20373.n8.nabble.com%2Ffile%2Ft1%2Fscroll_
>  bar_problem.png&
> > data=02%7C01%7Cpent%40adobe.com%7C8c21b8b4e77145f0ef1f08d55
>  50cc1c8%7Cfa7b1
> > b5a7b34438794aed2c178decee1%7C0%7C0%7C636508435642510130&sd
>  ata=lqFyo5AO7td
> > RcHECAn1KbiDZJOFiMi9bpfNLnFvDYgQ%3D&reserved=0>
> >
> > If you have an idea how to fix that problem it would be great if you
>  could
> > do it during your work on DataGrid.
> >
> > Maybe we shouldn't actually fix that ?
> >
> > Thanks, Piotr
> >
> >
> >
> >
> > --
> > Sent from:
> > https://na01.safelinks.protection.outlook.com/?url=http%3A%
>  2F%2Fapache-roy
> >
> >ale-development.20373.n8.nabble.com%2F&data=02%7C01%7Cpent%
> 40adobe.com
>  %7C8
> > c21b8b4e77145f0ef1f08d5550cc1c8%7Cfa7b1b5a7b34438794aed2c17
>  8decee1%7C0%7C0
> > %7C636508435642510130&sdata=%2Fd%2FchSnNgv9qO7qhIF%2B5e7uN0
>  U1nCJpZMjRGBwEQ
> > cqs%3D&reserved=0
> 
> 
> >>>
> >>>
> >>> --
> >>>
> >>> Piotr Zarzycki
> >>>
> >>> Patreon:
> >>>*https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.pa
> >>>treon.com%2Fpiotrzarzycki&data=02%7C01%7Cpent%40adobe.com
> %7Cec2acb7cf9ea
> >>>4bf1d63308d555ed0cf6%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636509
> >>>398965142180&sdata=VB6%2FJI38K02X3lWGGDwoH%
> 2FiB4LpPerWLwZFGyukRT0w%3D&re
> >>>served=0
> >>>
> >>> https%3A%2F%2Fwww.pa
> >>>treon.com%2Fpiotrzarzycki&data=02%7C01%7Cpent%40adobe.com
> %7Cec2acb7cf9ea
> >>>4bf1d63308d555ed0cf6%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636509
> >>>398965142180&sdata=VB6%2FJI38K02X3lWGGDwoH%
> 2FiB4LpPerWLwZFGyukRT0w%3D&re
> >>>served=0>*
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Piotr Zarzycki]

It would be really great if someone from PMCs who never touch Maven tried
test some application. That would be really helpful.

Thanks, Piotr

2018-01-08 23:00 GMT+01:00 Piotr Zarzycki :

> Today I had time to test only Maven artifacts. Tomorrow hopefully will try
> ANT and building stuff. Just wanted to share with you guys instruction how
> to test Maven artifacts. My tests went well. I have build three
> applications 2 MDL and one with Basic components - Each run without the
> problem. :)
>
> Instruction:
>
> 1) Pickup some example or whatever application you have which have pom.xml
> - It can be something from our Examples
> 2) Remove -SNAPSHOT from pom. Place everywhere 0.9.0 version.
> 3) Place following file template to the folder with your pom.xml [1]
> 4) Type in console mvn clean install -s settings-template.xml
> 5) Run your application from location target/javascript/bin/js-debug
>
> All dependencies should be downloaded. If you will be able to run
> application one part of the testing is done. :)
>
> [1] https://paste.apache.org/phar
>
> Thanks, Piotr
>
>
> 2018-01-08 18:16 GMT+01:00 Alex Harui :
>
>>
>>
>> On 1/8/18, 12:52 AM, "Piotr Zarzycki"  wrote:
>>
>> >Placing discussion here.
>> >
>> >Understand, so the problem actually now is in Develop, but in 0.9.0
>> >doesn't
>> >exists, cause script simply invoke creation exact what we have in
>> >"develop"
>> >branch. Once we finish release, merge released branched to develop, we
>> can
>> >simply make correction manually for the future release.
>>
>> Maven "automatically" does lots of things (makes lots of assumptions).  It
>> assumes that when you create a release branch that it should automatically
>> update the develop branch to the next release version (you can set what
>> that version is, but it defaults to updating the z in x.y.z version
>> formats).  Then at that point, the release branch still has the older
>> snapshot versions.  Another Maven release step removes the "-SNAPSHOT"
>> from the versions and does a quick check to see that there are no
>> remaining -SNAPSHOT dependencies.  However, Maven doesn't seem to
>> understand string substitution variables so we have to fix those up in the
>> Ant script that is calling all of these Maven steps.  Then Maven creates
>> and stages the artifacts and then updates the release branch to the next
>> version as well in order to make the merge work cleanly.
>>
>> It might be that we can use the distribution profile when creating the
>> branches and then Maven should find and update the version in that pom.
>> Maybe I will try that in a future release.
>>
>> The key is with this Ant script, we can hopefully automatically do
>> whatever manual steps are required to make everything work so releases
>> don't require as much human intervention.
>>
>> Thanks,
>> -Alex
>> >
>> >
>> >2018-01-08 9:28 GMT+01:00 Piotr Zarzycki :
>> >
>> >> Hi Alex,
>> >>
>> >> My concerns about that is actually been in thread "Royale Release
>> >>Process
>> >> Philosophy". Feel free to respond here. :)
>> >>
>> >> Thanks, Piotr
>> >>
>> >>
>> >> 2018-01-08 9:14 GMT+01:00 Alex Harui :
>> >>
>> >>> This is the discussion thread.
>> >>>
>> >>> The Maven artifacts are staged here:
>> >>>
>> >>>https://na01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Freposit
>> >>>ory.apache.org%2Fcontent%2Frepositories%2Forgapacheroyale
>> -1009&data=02%7
>> >>>C01%7Caharui%40adobe.com%7Ca178dcb9a51f45c6250008d556770f
>> f3%7Cfa7b1b5a7b
>> >>>34438794aed2c178decee1%7C0%7C0%7C636509991723063403&sdata
>> =7B5hROFXM6a%2B
>> >>>vwhhrdw8uselbRlRXvjhK%2BKomVjRlNY%3D&reserved=0
>> >>>
>> >>>
>> >>> Thanks,
>> >>> Alex Harui
>> >>>
>> >>>
>> >>
>> >>
>> >> --
>> >>
>> >> Piotr Zarzycki
>> >>
>> >> Patreon:
>> >>*https://na01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Fwww.pat
>> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
>> %7Ca178dcb9a51f
>> >>45c6250008d556770ff3%7Cfa7b1b5a7b34438794aed2c178decee1%
>> 7C0%7C0%7C6365099
>> >>91723063403&sdata=jTXIh3gSni4jErwmg4jYz7PsfVlA3S5z8%
>> 2Febivq8qKE%3D&reserv
>> >>ed=0
>> >>
>> >>> 3A%2F%2Fwww.pat
>> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
>> %7Ca178dcb9a51f
>> >>45c6250008d556770ff3%7Cfa7b1b5a7b34438794aed2c178decee1%
>> 7C0%7C0%7C6365099
>> >>91723063403&sdata=jTXIh3gSni4jErwmg4jYz7PsfVlA3S5z8%
>> 2Febivq8qKE%3D&reserv
>> >>ed=0>*
>> >>
>> >
>> >
>> >
>> >--
>> >
>> >Piotr Zarzycki
>> >
>> >Patreon:
>> >*https://na01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Fwww.patr
>> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7
>> Ca178dcb9a51f45
>> >c6250008d556770ff3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%
>> 7C0%7C6365099917
>> >23063403&sdata=jTXIh3gSni4jErwmg4jYz7PsfVlA3S5z8%
>> 2Febivq8qKE%3D&reserved=0
>> >> 3A%2F%2Fwww.patr
>> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7
>> Ca178dcb9a51f4

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Piotr Zarzycki]

Today I had time to test only Maven artifacts. Tomorrow hopefully will try
ANT and building stuff. Just wanted to share with you guys instruction how
to test Maven artifacts. My tests went well. I have build three
applications 2 MDL and one with Basic components - Each run without the
problem. :)

Instruction:

1) Pickup some example or whatever application you have which have pom.xml
- It can be something from our Examples
2) Remove -SNAPSHOT from pom. Place everywhere 0.9.0 version.
3) Place following file template to the folder with your pom.xml [1]
4) Type in console mvn clean install -s settings-template.xml
5) Run your application from location target/javascript/bin/js-debug

All dependencies should be downloaded. If you will be able to run
application one part of the testing is done. :)

[1] https://paste.apache.org/phar

Thanks, Piotr


2018-01-08 18:16 GMT+01:00 Alex Harui :

>
>
> On 1/8/18, 12:52 AM, "Piotr Zarzycki"  wrote:
>
> >Placing discussion here.
> >
> >Understand, so the problem actually now is in Develop, but in 0.9.0
> >doesn't
> >exists, cause script simply invoke creation exact what we have in
> >"develop"
> >branch. Once we finish release, merge released branched to develop, we can
> >simply make correction manually for the future release.
>
> Maven "automatically" does lots of things (makes lots of assumptions).  It
> assumes that when you create a release branch that it should automatically
> update the develop branch to the next release version (you can set what
> that version is, but it defaults to updating the z in x.y.z version
> formats).  Then at that point, the release branch still has the older
> snapshot versions.  Another Maven release step removes the "-SNAPSHOT"
> from the versions and does a quick check to see that there are no
> remaining -SNAPSHOT dependencies.  However, Maven doesn't seem to
> understand string substitution variables so we have to fix those up in the
> Ant script that is calling all of these Maven steps.  Then Maven creates
> and stages the artifacts and then updates the release branch to the next
> version as well in order to make the merge work cleanly.
>
> It might be that we can use the distribution profile when creating the
> branches and then Maven should find and update the version in that pom.
> Maybe I will try that in a future release.
>
> The key is with this Ant script, we can hopefully automatically do
> whatever manual steps are required to make everything work so releases
> don't require as much human intervention.
>
> Thanks,
> -Alex
> >
> >
> >2018-01-08 9:28 GMT+01:00 Piotr Zarzycki :
> >
> >> Hi Alex,
> >>
> >> My concerns about that is actually been in thread "Royale Release
> >>Process
> >> Philosophy". Feel free to respond here. :)
> >>
> >> Thanks, Piotr
> >>
> >>
> >> 2018-01-08 9:14 GMT+01:00 Alex Harui :
> >>
> >>> This is the discussion thread.
> >>>
> >>> The Maven artifacts are staged here:
> >>>
> >>>https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Freposit
> >>>ory.apache.org%2Fcontent%2Frepositories%2Forgapacheroyale-1009&data=
> 02%7
> >>>C01%7Caharui%40adobe.com%7Ca178dcb9a51f45c6250008d55677
> 0ff3%7Cfa7b1b5a7b
> >>>34438794aed2c178decee1%7C0%7C0%7C636509991723063403&
> sdata=7B5hROFXM6a%2B
> >>>vwhhrdw8uselbRlRXvjhK%2BKomVjRlNY%3D&reserved=0
> >>>
> >>>
> >>> Thanks,
> >>> Alex Harui
> >>>
> >>>
> >>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon:
> >>*https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.pat
> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
> %7Ca178dcb9a51f
> >>45c6250008d556770ff3%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6365099
> >>91723063403&sdata=jTXIh3gSni4jErwmg4jYz7PsfVlA3S
> 5z8%2Febivq8qKE%3D&reserv
> >>ed=0
> >>
> >> https%3A%2F%2Fwww.pat
> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
> %7Ca178dcb9a51f
> >>45c6250008d556770ff3%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6365099
> >>91723063403&sdata=jTXIh3gSni4jErwmg4jYz7PsfVlA3S
> 5z8%2Febivq8qKE%3D&reserv
> >>ed=0>*
> >>
> >
> >
> >
> >--
> >
> >Piotr Zarzycki
> >
> >Patreon:
> >*https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.patr
> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> 7Ca178dcb9a51f45
> >c6250008d556770ff3%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6365099917
> >23063403&sdata=jTXIh3gSni4jErwmg4jYz7PsfVlA3S
> 5z8%2Febivq8qKE%3D&reserved=0
> > https%3A%2F%2Fwww.patr
> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> 7Ca178dcb9a51f45
> >c6250008d556770ff3%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6365099917
> >23063403&sdata=jTXIh3gSni4jErwmg4jYz7PsfVlA3S
> 5z8%2Febivq8qKE%3D&reserved=0
> >>*
>
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: [Understanding PAYG] Button: Why is there no "text" or "icon" bead in order to compose a TextButton or IconButton?

[Olaf Krueger]

>We've tried to write up things like this in the FlexJS wiki...

Maybe I've overlooked some articles.
I just started to move articles to the "FlexJS" category to make sure that
we don't miss something when we'll move it to Royale...

Thanks,
Olaf



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: [Royale] ICollectionView

[Peter Ent]

I just pushed some changes that give you a more dynamic DataGrid.

The DataGrid should continue to work normally. But if you want to have it
respond to items being inserted and removed, then you can use the new
collection view beads.

I updated DataGridExample to illustrate how to do it PAYG. You change the
DataGrid's model to the new DataGridCollectionViewModel and then give each
column the DataItemRendererFactoryForCollectionView via CSS. This way the
majority of DataGrid uses that just display information will not have the
extra code required to respond to changes in the dataProvider. But if you
do use these new beads you can just insert or remove an item and the
columns in the DataGrid will reflect the changes. The DataGrid should also
remain selected unless you are removing the selected row.

—peter

On 1/7/18, 7:17 PM, "Peter Ent"  wrote:

>The DataGrid’s model’s dataProvider would be an ICollectionView which
>gets shared with each column list’s model’s dataProvider.  Changing the
>data should trigger events to have each list’s
>DataItemRendereFactoryForCollectionView update the itemRenderers.
>
>It should just work but I will be verifying that.
>
>Peter 
>
>
>> On Jan 7, 2018, at 11:38 AM, Piotr Zarzycki 
>>wrote:
>> 
>> Peter,
>> 
>> When you were saying that :"I had a reasonably working version of
>>DataGrid
>> for this..." - Do you mean usage of all that new stuff which helps
>>sorting
>> etc ? I'm working on the next example where DataGrid is being used. I
>>would
>> like to have also ability to update like we are doing that in list by
>> "DynamicUpdateItemRendererForArrayListData", but Grid is not a IList,
>>which
>> we are expecting in those Beads. What do you think what we should do in
>> order to achieve that ?
>> 
>> Thanks, Piotr
>> 
>> 
>> 2018-01-07 14:35 GMT+01:00 Piotr Zarzycki :
>> 
>>> Many Thanks!
>>> 
>>> I just noticed that Grid doesn't have selectedItem property. Not sure
>>>if
>>> it was for purpose.
>>> 
>>> Piotr
>>> 
>>> 2018-01-07 14:21 GMT+01:00 Peter Ent :
>>> 
 I did notice that something was happening with the scrollbars. I will
look
 into it.
 ‹peter
 
> On 1/6/18, 8:52 AM, "piotrz"  wrote:
> 
> Hi Peter,
> 
> Just wanted to let you know that I have started use more extensively
> DataGrid and I have found that using FlexLayout gives a way better
 results
> for DataGrid than VerticalFlexLayout/HorizotnalFlexLayout beads.
> 
> Ma last commit fixes issue with synchronizing width of column with
>width
> of
> header buttons in DataGrid.
> 
> However there is one problem with that - Scrollbar. Take a look into
>the
> DataGridExample where scrollbar appear. Last column is a bit shifted.
> Without scrollbar width is perfectly synced.
> 
>  yale-development.20373.n8.nabble.com%2Ffile%2Ft1%2Fscroll_
 bar_problem.png&
> data=02%7C01%7Cpent%40adobe.com%7C8c21b8b4e77145f0ef1f08d55
 50cc1c8%7Cfa7b1
> b5a7b34438794aed2c178decee1%7C0%7C0%7C636508435642510130&sd
 ata=lqFyo5AO7td
> RcHECAn1KbiDZJOFiMi9bpfNLnFvDYgQ%3D&reserved=0>
> 
> If you have an idea how to fix that problem it would be great if you
 could
> do it during your work on DataGrid.
> 
> Maybe we shouldn't actually fix that ?
> 
> Thanks, Piotr
> 
> 
> 
> 
> --
> Sent from:
> https://na01.safelinks.protection.outlook.com/?url=http%3A%
 2F%2Fapache-roy
> 
>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7Cpent%40adobe.com
 %7C8
> c21b8b4e77145f0ef1f08d5550cc1c8%7Cfa7b1b5a7b34438794aed2c17
 8decee1%7C0%7C0
> %7C636508435642510130&sdata=%2Fd%2FchSnNgv9qO7qhIF%2B5e7uN0
 U1nCJpZMjRGBwEQ
> cqs%3D&reserved=0
 
 
>>> 
>>> 
>>> --
>>> 
>>> Piotr Zarzycki
>>> 
>>> Patreon: 
>>>*https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.pa
>>>treon.com%2Fpiotrzarzycki&data=02%7C01%7Cpent%40adobe.com%7Cec2acb7cf9ea
>>>4bf1d63308d555ed0cf6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636509
>>>398965142180&sdata=VB6%2FJI38K02X3lWGGDwoH%2FiB4LpPerWLwZFGyukRT0w%3D&re
>>>served=0
>>> 
>>>>>treon.com%2Fpiotrzarzycki&data=02%7C01%7Cpent%40adobe.com%7Cec2acb7cf9ea
>>>4bf1d63308d555ed0cf6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636509
>>>398965142180&sdata=VB6%2FJI38K02X3lWGGDwoH%2FiB4LpPerWLwZFGyukRT0w%3D&re
>>>served=0>*
>>> 
>> 
>> 
>> 
>> -- 
>> 
>> Piotr Zarzycki
>> 
>> Patreon: 
>>*https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.pat
>>reon.com%2Fpiotrzarzycki&data=02%7C01%7Cpent%40adobe.com%7Cec2acb7cf9ea4b
>>f1d63308d555ed0cf6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636509398
>>965142180&sdata=VB6%2FJI38K02X3lWGGDwoH%2FiB4LpPerWLwZFGyukRT0w%3D&reserv
>>ed=0
>> 
>>

Re: How to overwrite/change a components' default styles the royale way?

[Olaf Krueger]

Hmm, I am not sure if we're misunderstood...

I don't want to say that we should go the Flex way or that we need something
like skinning.
I just would like to say that from my point of view it is important to
provide a possibility to overwrite CSS  styles in that way, that no default
styles remain in the HTML.

As long as we target HTML I think the easiest way is to just apply HTML/CSS3
styles to change the look and feel of components/elements.

However, maybe I get something wrong... I'll continue for now with exploring
those things... 

Thanks,
Olaf





--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: [Understanding PAYG] Button: Why is there no "text" or "icon" bead in order to compose a TextButton or IconButton?

[Alex Harui]

On 1/8/18, 12:50 AM, "Olaf Krueger"  wrote:

>>Because the components have a model, the model needs to be PAYG...
>
>I guess I have to start exploring the asjs source code a bit more soon...
>Is there any kind of documentation how those strands and beads are
>internally works and how they are implemented or which patterns are used?

We've tried to write up things like this in the FlexJS wiki.  We are still
in the process of moving this information to Royale repos and updating it.
 Volunteers are more than welcome to help.

Thanks,
-Alex
>
>
>--
>Sent from: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy
>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7
>Cf9d19318ac754055ef1208d55674e03b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7
>C0%7C636509982339157503&sdata=1GkL2b5LB7luKj6sfudjkeK0APLLJnfkf4arakHhP0o%
>3D&reserved=0

Re: How to overwrite/change a components' default styles the royale way?

[Alex Harui]

From what I see in the browser, the browser is used to having a ton of CSS
to process.  While we are trying to replicate as much of Flex as we can,
we also don't want to blindly replicate all of Flex.  That's why the UI
set isn't 100% backward compatible, and in this case, why we are going to
rely on browser CSS instead of trying to make the browser implement Flex
CSS.  We will likely have a skin-able component set some day, but the
realization is that if you don't use Royale, you are probably going to
have to learn more about CSS that you did when you used Flex.  So, as long
as the CSS you would normally have to apply if you weren't using Royale
works when you do use Royale, that is the minimum.  If we can do better
than that, great, but not currently a huge priority for me.

So, if I'm not using Royale and just using HTML/CSS/JS and overriding the
default in some CSS theme, my choices are, IIRC, to set styles on a
component, or add a class selector, or override an existing class selector
from the theme. We are pretty much offering the same, I think.

My 2 cents,
-Alex

On 1/8/18, 12:31 AM, "Olaf Krueger"  wrote:

>Hi Alex,
>
>>We can look into it more.
>I'd highly appreciate it ;-)
>
>From my point of view the styling of (custom) components is crucial for
>Royal.
>For a Flex developer who will use Royale I guess CSS3 styling replaces
>Flex
>skinning and I guess anybody out there wants to give his compoenents a
>custom look and feel.
>Am I wrong? What do others think?
>
>So, even if the compiler maybe doesn't combine selectors properly for now
>I
>am still interested if there's a recommend way to style custom components.
>E.g. the way of 'overwriting' the default styles for a js:TextButton by
>applying styles to the 'Button' element feels not like the Royale way for
>me
>and on the other side am not sure if all default styles could be set
>successfully by applying styles by using the class selector (.myButton).
>
>If there's a recommend way I would like to write some docs in the near
>future...
>
>Thanks for help,
>Olaf
>
>
>
>
>
>
>
>--
>Sent from: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy
>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7
>C35786786a6fc40c6be2208d556737d6e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7
>C0%7C636509976388358349&sdata=aDGmTNKjZ4V95qEoWVaG%2BJdUcCkZwDuYU119XX9F0a
>A%3D&reserved=0

Re: Compiling Royale Libraries with Flash Builder (SWF)

[Alex Harui]

Yishay, 

I'm not clear what you are trying to do.  How did you get compiler JUNIT
tests to run from Flash Builder?

-Alex

On 1/8/18, 1:18 AM, "Yishay Weiss"  wrote:

>It wasn’t set. Now that I’ve set it I’m getting this:
>
>
>
>tests:
>
>[mkdir] Created dir:
>C:\dev\flexjs\royale-compiler\compiler\target\junit-reports
>
>[mkdir] Created dir:
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp
>
>[junit] Running as.ASExpressionTests
>
>[junit] looking for C:\dev\flexjs\royale-compiler\env.properties
>
>[junit] environment property - FLEX_HOME = C:\dev\flexjs\flex-sdk
>
>[junit] environment property - PLAYERGLOBAL_HOME = C:\dev\flashplayer
>
>[junit] environment property - PLAYERGLOBAL_VERSION = 11.1
>
>[junit] environment property - TLF_HOME = null
>
>[junit] environment property - AIR_HOME = C:\dev\flexjsbuilds\nightly
>
>[junit] environment property - FLASHPLAYER_DEBUGGER = null
>
>[junit] environment property - ASJS_HOME = C:\dev\flexjs\royale-asjs
>
>[junit] environment property - GOOG_HOME =
>C:\dev\flexjsbuilds\nightly/js/lib/google/closure-library
>
>[junit] Generating test:
>
>[junit] Compiling test:
>
>[junit] 
>-external-library-path=C:\dev\flashplayer\11.1\playerglobal.swc
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests
>8263907973881887007.as
>
>[junit]
>
>[junit] 783 bytes written to
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests
>8263907973881887007.swf in 1.182 seconds
>
>[junit] After compile:
>
>[junit] Unexpected compilation problems:
>
>[junit]
>
>[junit] Generating test:
>
>[junit] Compiling test:
>
>[junit] 
>-external-library-path=C:\dev\flashplayer\11.1\playerglobal.swc
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests
>5673153471287683621.as
>
>[junit]
>
>[junit] 767 bytes written to
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests
>5673153471287683621.swf in 0.578 seconds
>
>[junit] After compile:
>
>[junit] Unexpected compilation problems:
>
>[junit]
>
>[junit] Generating test:
>
>[junit] Compiling test:
>
>[junit] 
>-external-library-path=C:\dev\flashplayer\11.1\playerglobal.swc
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests
>6206048447772149132.as
>
>[junit]
>
>[junit] 857 bytes written to
>C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests
>6206048447772149132.swf in 0.582 seconds
>
>[junit] After compile:
>
>[junit] Unexpected compilation problems:
>
>[junit]
>
>[junit] Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time
>elapsed: 2.922 sec
>
>[junit] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
>
>
>
>BUILD FAILED
>
>C:\dev\flexjs\royale-asjs\build.xml:1752: The following error occurred
>while executing this line:
>
>C:\dev\flexjs\royale-asjs\build.xml:1823: The following error occurred
>while executing this line:
>
>C:\dev\flexjs\royale-compiler\build.xml:80: The following error occurred
>while executing this line:
>
>C:\dev\flexjs\royale-compiler\compiler\build.xml:711: The following error
>occurred while executing this line:
>
>C:\dev\flexjs\royale-compiler\compiler\src\test\build.xml:307: Tests
>failed
>
>
>
>Total time: 8 minutes 20 seconds
>
>
>
>
>
>
>
>
>From: Alex Harui 
>Sent: Monday, January 8, 2018 7:39:15 AM
>To: dev@royale.apache.org
>Subject: Re: Compiling Royale Libraries with Flash Builder (SWF)
>
>What is PLAYERGLOBAL_HOME set to?
>
>-Alex
>
>On 1/7/18, 7:03 AM, "Yishay Weiss"  wrote:
>
>>I think that might have been it but I’m now struggling to get a Royale
>>build working.
>>
>>
>>
>>When trying to build Basic I’m getting
>>
>>
>>
>>C:\dev\flexjs\royale-asjs\frameworks\royale-config.xml(74): col: 0 unable
>>to open 'C:\dev\flexjs\royale-asjs\frameworks\\11.1\playerglobal.swc'.
>>
>>
>>
>>Any pointers would be appreciated…
>>
>>
>>
>>
>>From: Alex Harui 
>>Sent: Tuesday, January 2, 2018 7:05:48 PM
>>To: dev@royale.apache.org
>>Subject: Re: Compiling Royale Libraries with Flash Builder (SWF)
>>
>>In Project/Properties/Flex Build Path dialog, see which SWCs are being
>>used.  If your Royale SDK is/was a JS-Only one, you may be using the JS
>>SWCs during SWF compilation.
>>
>>HTH,
>>-Alex
>>
>>On 1/2/18, 12:42 AM, "Yishay Weiss"  wrote:
>>
>>>I’m getting messages such as
>>>1044: interface method applyImageData in interface IImage not
>>>implemented
>>>by class BinaryImage
>>>
>>>When I look at IImage I see
>>>  COMPILE::JS
>>>  function applyImageData(binaryDataAsString:String):void;
>>>So it looks like the FB compiler ignores the fact that It’s a JS only
>>>method and expected swf implementers to implement it as well.
>>>
>>>
>>
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Alex Harui]

On 1/8/18, 12:52 AM, "Piotr Zarzycki"  wrote:

>Placing discussion here.
>
>Understand, so the problem actually now is in Develop, but in 0.9.0
>doesn't
>exists, cause script simply invoke creation exact what we have in
>"develop"
>branch. Once we finish release, merge released branched to develop, we can
>simply make correction manually for the future release.

Maven "automatically" does lots of things (makes lots of assumptions).  It
assumes that when you create a release branch that it should automatically
update the develop branch to the next release version (you can set what
that version is, but it defaults to updating the z in x.y.z version
formats).  Then at that point, the release branch still has the older
snapshot versions.  Another Maven release step removes the "-SNAPSHOT"
from the versions and does a quick check to see that there are no
remaining -SNAPSHOT dependencies.  However, Maven doesn't seem to
understand string substitution variables so we have to fix those up in the
Ant script that is calling all of these Maven steps.  Then Maven creates
and stages the artifacts and then updates the release branch to the next
version as well in order to make the merge work cleanly.

It might be that we can use the distribution profile when creating the
branches and then Maven should find and update the version in that pom.
Maybe I will try that in a future release.

The key is with this Ant script, we can hopefully automatically do
whatever manual steps are required to make everything work so releases
don't require as much human intervention.

Thanks,
-Alex
>
>
>2018-01-08 9:28 GMT+01:00 Piotr Zarzycki :
>
>> Hi Alex,
>>
>> My concerns about that is actually been in thread "Royale Release
>>Process
>> Philosophy". Feel free to respond here. :)
>>
>> Thanks, Piotr
>>
>>
>> 2018-01-08 9:14 GMT+01:00 Alex Harui :
>>
>>> This is the discussion thread.
>>>
>>> The Maven artifacts are staged here:
>>> 
>>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freposit
>>>ory.apache.org%2Fcontent%2Frepositories%2Forgapacheroyale-1009&data=02%7
>>>C01%7Caharui%40adobe.com%7Ca178dcb9a51f45c6250008d556770ff3%7Cfa7b1b5a7b
>>>34438794aed2c178decee1%7C0%7C0%7C636509991723063403&sdata=7B5hROFXM6a%2B
>>>vwhhrdw8uselbRlRXvjhK%2BKomVjRlNY%3D&reserved=0
>>>
>>>
>>> Thanks,
>>> Alex Harui
>>>
>>>
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: 
>>*https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.pat
>>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ca178dcb9a51f
>>45c6250008d556770ff3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365099
>>91723063403&sdata=jTXIh3gSni4jErwmg4jYz7PsfVlA3S5z8%2Febivq8qKE%3D&reserv
>>ed=0
>> 
>>>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ca178dcb9a51f
>>45c6250008d556770ff3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365099
>>91723063403&sdata=jTXIh3gSni4jErwmg4jYz7PsfVlA3S5z8%2Febivq8qKE%3D&reserv
>>ed=0>*
>>
>
>
>
>-- 
>
>Piotr Zarzycki
>
>Patreon: 
>*https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patr
>eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ca178dcb9a51f45
>c6250008d556770ff3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365099917
>23063403&sdata=jTXIh3gSni4jErwmg4jYz7PsfVlA3S5z8%2Febivq8qKE%3D&reserved=0
>eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ca178dcb9a51f45
>c6250008d556770ff3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365099917
>23063403&sdata=jTXIh3gSni4jErwmg4jYz7PsfVlA3S5z8%2Febivq8qKE%3D&reserved=0
>>*

Re: Royale Release Process Philosophy

[Alex Harui]

On 1/8/18, 12:42 AM, "Olaf Krueger"  wrote:

>>...of the CatX
>
>What is CatX?

CatX is the short name for "Category X Dependencies" which are
dependencies that are not compatible with the Apache License.  IMO, some
ASF Policies are conventions for how to track information and make it
easier for users to find and understand, but some, like the CatX policies,
are important to the reputation and "brand quality" of the ASF.


My 2 cents,
-Alex
>
>--
>Sent from: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy
>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7
>C6b4c6e97ab42463a5ad408d55673e0cc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7
>C0%7C636509978054375115&sdata=gSEiH6H3P1E6HeWg1C2kwV%2Fd69ZVeUEuVMxFke56XB
>8%3D&reserved=0

Re: [Understanding PAYG] Button: Why is there no "text" or "icon" bead in order to compose a TextButton or IconButton?

[Peter Ent]

Keep in mind that a Royale Button's base UI element is platform dependent.
On the HTML side, the element is a  and there is no view bead to
construct it. TextButtonView is a Flash platform class that makes the
actual UI button with its up/down/over states represented as separate
basic elements.

Button is a tricky one because it is so basic to the platform. In other
components, the base UI element is a  (HTML) or a
DisplayObjectContainer (Flash) and then what you actually see and interact
with are its children which are created by view beads. Not really the case
for Button.

‹peter

On 1/7/18, 9:16 PM, "Alex Harui"  wrote:

>You would add TextButtonView or ImageButtonView.  Most Basic top-level
>components are an aggregation of a model and view and often a controller.
>Express aggregates "non-essential" and/or less type-safe beads as well to
>reduce the amount of bead-adding you have to do.
>
>Because the components have a model, the model needs to be PAYG and not
>have slots for data like labels and icons it doesn't need.  The most basic
>button on some platforms does not have text or an icon because the visuals
>can be specified in CSS via background-image.
>
>HTH,
>-Alex
>
>On 1/7/18, 1:33 PM, "Olaf Krueger"  wrote:
>
>>Hi,
>>just for my understanding:
>>
>>It seems to me that we can't compose a TextButton or an IconButton or a
>>TextIconButton by adding some beads to Button, something like this [1].
>>Instead, we have "TextButton" which feels for me a bit like an Express
>>component.
>>I just would like to know if I have a wrong understanding of PAYG [1] or
>>if
>>those suggested beads just not implemented because nobody did it so far.
>>
>>Thank you!
>>Olaf
>>
>>
>>[1]
>>
>>   
>>  
>>  
>>   
>>
>>
>>
>>
>>--
>>Sent from: 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-ro
>>y
>>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%
>>7
>>C6b87c66fff6b472d0c4b08d55616630d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%
>>7
>>C0%7C636509576506543643&sdata=DXTepjQ2JQlIO7IwMOtdfL2e30usYh3nMvgKSZ3mluE
>>%
>>3D&reserved=0
>

Jenkins build is back to normal : royale-typedefs #52

[apacheroyaleci]

See 

Build failed in Jenkins: royale-typedefs #51

[apacheroyaleci]

See 


--
Started by upstream project "royale-compiler" build number 42
originally caused by:
 Started by timer
Building in workspace 

 > git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git.exe config remote.origin.url 
 > https://github.com/apache/royale-typedefs.git # timeout=10
Fetching upstream changes from https://github.com/apache/royale-typedefs.git
 > git.exe --version # timeout=10
 > git.exe fetch --tags --progress 
 > https://github.com/apache/royale-typedefs.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git.exe rev-parse "refs/remotes/origin/develop^{commit}" # timeout=10
 > git.exe rev-parse "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 3b27aa06d350aa3c1e24b53ad368503e55e6d57f 
(refs/remotes/origin/develop)
 > git.exe config core.sparsecheckout # timeout=10
 > git.exe checkout -f 3b27aa06d350aa3c1e24b53ad368503e55e6d57f
Commit message: "[maven-release-plugin] prepare for next development iteration"
 > git.exe rev-list --no-walk 3b27aa06d350aa3c1e24b53ad368503e55e6d57f # 
 > timeout=10
[royale-typedefs] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat main && 
exit %%ERRORLEVEL%%"
Buildfile: 


main:

download:
 [echo] 

[unjar] Expanding: C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\lib\google\closure-compiler\compiler.jar
 into 

[unzip] Expanding: 

 into 

  [get] Getting: 
https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/closureidl/svg.js
  [get] To: 


double-check-file:
 [echo] ${env.ROYALE_DOWNLOAD_CACHE}
 [echo] Need file: ${still_no_file}

get-from-cache-if-needed:

fail-if-not-found:

preprocess:

externc:
 [java] Math parameters not found!  0
 [java] Reflect parameters not found!  0
 [java] chrome parameters not found!  0
 [java] app parameters not found!  0
 [java] webstore parameters not found!  0
 [java] runtime parameters not found!  0
 [java] Intl parameters not found!  0
 [java] Exception in thread "main" java.lang.NoClassDefFoundError: 
org/apache/royale/compiler/clients/problems/ProblemFormatter
 [java] at 
org.apache.royale.compiler.clients.EXTERNC.mainNoExit(EXTERNC.java:174)
 [java] at 
org.apache.royale.compiler.clients.EXTERNC.staticMainNoExit(EXTERNC.java:152)
 [java] at 
org.apache.royale.compiler.clients.EXTERNC.main(EXTERNC.java:137)
 [java] Caused by: java.lang.ClassNotFoundException: 
org.apache.royale.compiler.clients.problems.ProblemFormatter
 [java] at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
 [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
 [java] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:338)
 [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
 [java] ... 3 more
 [java] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8

BUILD FAILED
:52:
 The following error occurred while executing this line:
:159:
 Java returned: 1

Total time: 20 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
Build step 'Invoke Ant' marked build as failure

[VOTE] Release Apache Royale 0.9.0 RC1

[Alex Harui]

Hi,

This is vote for the 0.9.0 release of Apache Royale.

The release candidate can be found here;
https://dist.apache.org/repos/dist/dev/royale/0.9.0/rc1/

Before voting please review the section,'What are the ASF requirements on
approving a release?', at:
http://www.apache.org/dev/release.html#approving-a-release

At a minimum you would be expected to check that:
- MD5 and signed packages are correct
- README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
- That the build script completes successfully
- That you can compile and cross-compile a simple example using the SDK.

The source package is a combination of the 3 main Royale repos

To use the binary package, unzip it into a folder.  The -js package is
ready-to-use in an IDE or command-line.  If you need SWF output, use the
-royale package and use Apache Ant to run the InstallAdobeSDKs script via:
  ant -f InstallAdobeSDKs.xml

You may also get the binary packages via NPM.  The -js package can be
installed via:

npm install 
https://dist.apache.org/repos/dist/dev/royale/${release.version}/rc${rc}/bi
naries/apache-royale-jsonly-${release.version}-bin.tar.gz -g

The full package with SWF support can be installed via:

npm install 
https://dist.apache.org/repos/dist/dev/royale/${release.version}/rc{rc}/bin
aries/apache-royale-${release.version}-bin.tar.gz -g


Please vote to approve this release:
+1 Approve the release
-1 Disapprove the release (please provide specific comments to why)

This vote will be open for 72 hours or until a result can be called.

The vote passes if there is:
- At least 3 +1 votes from the PMC
- More positive votes than negative votes

Remember that this is a 'beta-quality' release so I expect there
will be many bugs found.  IMO the goal is not to try to find and fix bugs
in the RC, but to make sure we have the packaging right, and enough
functionality that folks will have some success trying to use it.

People who are not in PMC are also encouraged to test out the release and
vote, although their votes will not be binding, they can influence how the
PMC votes.

When voting please indicate what OS, IDE, Flash Player version and AIR
version you tested with.

For your convenience, there is an ant script that automates the common
steps to validate a release.  Instead of individually downloading the
package and signature files, unzipping, etc, you can instead:
1) create an empty folder,
2) download into that folder this file:
https://dist.apache.org/repos/dist/dev/royale/0.9.0/rc1/ApproveRoyale.xml
3) run the script:
   ant -e -f ApproveRoyale.xml -Drelease.version=0.9.0 -Drc=1

You are not required to use this script, and more testing of the packages
and build results are always encouraged.


Please put all discussion about this release in the DISCUSSION thread not
this VOTE thread.

Thanks,
Alex Harui

RE: Compiling Royale Libraries with Flash Builder (SWF)

[Yishay Weiss]

It wasn’t set. Now that I’ve set it I’m getting this:



tests:

[mkdir] Created dir: 
C:\dev\flexjs\royale-compiler\compiler\target\junit-reports

[mkdir] Created dir: 
C:\dev\flexjs\royale-compiler\compiler\target\junit-temp

[junit] Running as.ASExpressionTests

[junit] looking for C:\dev\flexjs\royale-compiler\env.properties

[junit] environment property - FLEX_HOME = C:\dev\flexjs\flex-sdk

[junit] environment property - PLAYERGLOBAL_HOME = C:\dev\flashplayer

[junit] environment property - PLAYERGLOBAL_VERSION = 11.1

[junit] environment property - TLF_HOME = null

[junit] environment property - AIR_HOME = C:\dev\flexjsbuilds\nightly

[junit] environment property - FLASHPLAYER_DEBUGGER = null

[junit] environment property - ASJS_HOME = C:\dev\flexjs\royale-asjs

[junit] environment property - GOOG_HOME = 
C:\dev\flexjsbuilds\nightly/js/lib/google/closure-library

[junit] Generating test:

[junit] Compiling test:

[junit] -external-library-path=C:\dev\flashplayer\11.1\playerglobal.swc 
C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests8263907973881887007.as

[junit]

[junit] 783 bytes written to 
C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests8263907973881887007.swf
 in 1.182 seconds

[junit] After compile:

[junit] Unexpected compilation problems:

[junit]

[junit] Generating test:

[junit] Compiling test:

[junit] -external-library-path=C:\dev\flashplayer\11.1\playerglobal.swc 
C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests5673153471287683621.as

[junit]

[junit] 767 bytes written to 
C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests5673153471287683621.swf
 in 0.578 seconds

[junit] After compile:

[junit] Unexpected compilation problems:

[junit]

[junit] Generating test:

[junit] Compiling test:

[junit] -external-library-path=C:\dev\flashplayer\11.1\playerglobal.swc 
C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests6206048447772149132.as

[junit]

[junit] 857 bytes written to 
C:\dev\flexjs\royale-compiler\compiler\target\junit-temp\ASExpressionTests6206048447772149132.swf
 in 0.582 seconds

[junit] After compile:

[junit] Unexpected compilation problems:

[junit]

[junit] Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 
2.922 sec

[junit] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8



BUILD FAILED

C:\dev\flexjs\royale-asjs\build.xml:1752: The following error occurred while 
executing this line:

C:\dev\flexjs\royale-asjs\build.xml:1823: The following error occurred while 
executing this line:

C:\dev\flexjs\royale-compiler\build.xml:80: The following error occurred while 
executing this line:

C:\dev\flexjs\royale-compiler\compiler\build.xml:711: The following error 
occurred while executing this line:

C:\dev\flexjs\royale-compiler\compiler\src\test\build.xml:307: Tests failed



Total time: 8 minutes 20 seconds








From: Alex Harui 
Sent: Monday, January 8, 2018 7:39:15 AM
To: dev@royale.apache.org
Subject: Re: Compiling Royale Libraries with Flash Builder (SWF)

What is PLAYERGLOBAL_HOME set to?

-Alex

On 1/7/18, 7:03 AM, "Yishay Weiss"  wrote:

>I think that might have been it but I’m now struggling to get a Royale
>build working.
>
>
>
>When trying to build Basic I’m getting
>
>
>
>C:\dev\flexjs\royale-asjs\frameworks\royale-config.xml(74): col: 0 unable
>to open 'C:\dev\flexjs\royale-asjs\frameworks\\11.1\playerglobal.swc'.
>
>
>
>Any pointers would be appreciated…
>
>
>
>
>From: Alex Harui 
>Sent: Tuesday, January 2, 2018 7:05:48 PM
>To: dev@royale.apache.org
>Subject: Re: Compiling Royale Libraries with Flash Builder (SWF)
>
>In Project/Properties/Flex Build Path dialog, see which SWCs are being
>used.  If your Royale SDK is/was a JS-Only one, you may be using the JS
>SWCs during SWF compilation.
>
>HTH,
>-Alex
>
>On 1/2/18, 12:42 AM, "Yishay Weiss"  wrote:
>
>>I’m getting messages such as
>>1044: interface method applyImageData in interface IImage not implemented
>>by class BinaryImage
>>
>>When I look at IImage I see
>>  COMPILE::JS
>>  function applyImageData(binaryDataAsString:String):void;
>>So it looks like the FB compiler ignores the fact that It’s a JS only
>>method and expected swf implementers to implement it as well.
>>
>>
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Piotr Zarzycki]

Placing discussion here.

Understand, so the problem actually now is in Develop, but in 0.9.0 doesn't
exists, cause script simply invoke creation exact what we have in "develop"
branch. Once we finish release, merge released branched to develop, we can
simply make correction manually for the future release.


2018-01-08 9:28 GMT+01:00 Piotr Zarzycki :

> Hi Alex,
>
> My concerns about that is actually been in thread "Royale Release Process
> Philosophy". Feel free to respond here. :)
>
> Thanks, Piotr
>
>
> 2018-01-08 9:14 GMT+01:00 Alex Harui :
>
>> This is the discussion thread.
>>
>> The Maven artifacts are staged here:
>> https://repository.apache.org/content/repositories/orgapacheroyale-1009
>>
>>
>> Thanks,
>> Alex Harui
>>
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>



-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: [Understanding PAYG] Button: Why is there no "text" or "icon" bead in order to compose a TextButton or IconButton?

[Olaf Krueger]

>Because the components have a model, the model needs to be PAYG...

I guess I have to start exploring the asjs source code a bit more soon...
Is there any kind of documentation how those strands and beads are
internally works and how they are implemented or which patterns are used?

Thanks,
Olaf



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Royale Release Process Philosophy

[Olaf Krueger]

>I think we should try to cut a release during the first week of every 
>month, and potentially more often than that if a release goes out with 
>blocking problems. 

Hugh +1!


>...of the CatX

What is CatX?


Thanks for working on this,
Olaf



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: How to overwrite/change a components' default styles the royale way?

[Olaf Krueger]

Hi Alex,

>We can look into it more.
I'd highly appreciate it ;-)

>From my point of view the styling of (custom) components is crucial for
Royal.
For a Flex developer who will use Royale I guess CSS3 styling replaces Flex
skinning and I guess anybody out there wants to give his compoenents a
custom look and feel.
Am I wrong? What do others think?

So, even if the compiler maybe doesn't combine selectors properly for now I
am still interested if there's a recommend way to style custom components.
E.g. the way of 'overwriting' the default styles for a js:TextButton by
applying styles to the 'Button' element feels not like the Royale way for me
and on the other side am not sure if all default styles could be set
successfully by applying styles by using the class selector (.myButton).

If there's a recommend way I would like to write some docs in the near
future...

Thanks for help,
Olaf







--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Royale Release Process Philosophy

[Alex Harui]

The ant script tries to update the poms that Maven doesn't see.

When Maven cuts a release branch, it tries to update the poms to the next
version in the develop branch (in this case to 0.9.1-SNAPSHOT) and makes a
release branch with the current version (in this case 0.9.0).  The release
script ignores the develop branch for now, but if there is something in
there we need to fix, we can add it to the script.  But the current idea
is that we'll all be focused on the release branch for 72 hours, and once
the release is approved, there is a target in the ant script that updates
the places where Ant and Maven pick up versions and merge the release
branch to develop and that should get the develop branch set up with the
right versions.

We'll see how it goes.  I expect there are things we need to improve in
the script.  The goal is to get it all to automated so we don't forget
important steps or make silly errors.

-Alex 

On 1/8/18, 12:10 AM, "Piotr Zarzycki"  wrote:

>Hi Alex,
>
>I was waiting for your summarize in case of the preparation for release. I
>like your idea, cause we are exercising similar approach with Moonshine
>team. We are trying to have monthly release, next release just have to be
>better and hopefully bringing some new useful features. After 3 last month
>I can say that is succeeded.
>+1 - For the idea, let's get try to see how it's working in Royale.
>
>As for the script and build. If your script use Maven as an creator of
>branches (because we know that Maven has a way to automate the process) -
>it may not be enough. One of the steps in case of Maven is to change
>current poms-version - I saw in the repo right now 0.9.1. Unfortunately it
>is not enough, cause many poms has not the right version, cause they are
>simply not in the chain.
>
>One of the example is "distribution" folder. How can we handle this in
>that
>process?
>
>You are starting script - it's doing branch and changing poms and that
>version is suppose to be something for the VOTE, but hey - it's not cause
>we have still something to correct manually. - Are we doing it on that
>branch ? Can we ?
>
>Many Tanks for that idea!
>Piotr
>
>
>
>2018-01-08 8:57 GMT+01:00 Alex Harui :
>
>> Hi,
>>
>> I think I have a script that builds all of the Maven, Ant and I think
>>even
>> NPM artifacts for a Royale release.
>>
>> Instead of the Flex "Last Call" process, I would like to try a different
>> process and philosophy for Royale.  The script takes a while to run, but
>> is relatively straightforward so I think we should try releasing
>>whatever
>> happens to be in the develop branches more often, maybe monthly or even
>> more frequently than that.  So there won't be any "Last Call" since that
>> slows down the release process while we wait for someone to finish some
>> code or fix small things.
>>
>> I think we should try to cut a release during the first week of every
>> month, and potentially more often than that if a release goes out with
>> blocking problems.
>>
>> As such, we want to adopt a different philosophy to voting.  As
>> recommended by Roy Fielding, we could take the approach of "better than
>> the last release and not illegal".  And "not illegal" means truly
>>breaking
>> a law, not some policy issue.  I would say we would not release
>>something
>> that is in violation of the CatX handling policy though.
>>
>> So the process will be something like:  in the first week of every month
>> (not necessarily on the 1st day of the month), someone will cut an RC
>>and
>> we'll vote on it, and if we didn't break something important and aren't
>> breaking any laws and are handling CatX properly, we vote +1 and out it
>> goes.  Most bugs should not hold up these releases.  If something is
>> broken we try to fix it in a few days and hopefully out it goes then,
>>but
>> most other fixes just go in the develop branch and goes in the next
>> release.  Then towards the end of the month, we try to find a volunteer
>>to
>> cut the next monthly release. If we can work together to get releases
>>out
>> quickly, I will be the RM for the first couple of releases to make sure
>> the script holds up.
>>
>>
>> If we ship a release and after it goes out, something is found and we
>>want
>> to release a fix right away, we will do that as well, even if that means
>> that the first week of the month release is only a week later.
>>
>> Any objections?  Either way, the script completed building an RC, so I
>>am
>> going to send out vote and discuss emails for it so people will review
>>it
>> in case the script needs fixing.
>>
>> Thoughts?
>> -Alex
>>
>>
>
>
>-- 
>
>Piotr Zarzycki
>
>Patreon: 
>*https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patr
>eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ce764362e500847
>8513cd08d5566f4161%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365099581
>97400960&sdata=1AsrVYUTzkHej7yIn0DeCVn0Z83o0mg6NZnSW76IiD0%3D&reserved=0
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Piotr Zarzycki]

Hi Alex,

My concerns about that is actually been in thread "Royale Release Process
Philosophy". Feel free to respond here. :)

Thanks, Piotr


2018-01-08 9:14 GMT+01:00 Alex Harui :

> This is the discussion thread.
>
> The Maven artifacts are staged here:
> https://repository.apache.org/content/repositories/orgapacheroyale-1009
>
>
> Thanks,
> Alex Harui
>
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

[DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Alex Harui]

This is the discussion thread.

The Maven artifacts are staged here:
https://repository.apache.org/content/repositories/orgapacheroyale-1009


Thanks,
Alex Harui

Re: Royale Release Process Philosophy

[Piotr Zarzycki]

Hi Alex,

I was waiting for your summarize in case of the preparation for release. I
like your idea, cause we are exercising similar approach with Moonshine
team. We are trying to have monthly release, next release just have to be
better and hopefully bringing some new useful features. After 3 last month
I can say that is succeeded.
+1 - For the idea, let's get try to see how it's working in Royale.

As for the script and build. If your script use Maven as an creator of
branches (because we know that Maven has a way to automate the process) -
it may not be enough. One of the steps in case of Maven is to change
current poms-version - I saw in the repo right now 0.9.1. Unfortunately it
is not enough, cause many poms has not the right version, cause they are
simply not in the chain.

One of the example is "distribution" folder. How can we handle this in that
process?

You are starting script - it's doing branch and changing poms and that
version is suppose to be something for the VOTE, but hey - it's not cause
we have still something to correct manually. - Are we doing it on that
branch ? Can we ?

Many Tanks for that idea!
Piotr



2018-01-08 8:57 GMT+01:00 Alex Harui :

> Hi,
>
> I think I have a script that builds all of the Maven, Ant and I think even
> NPM artifacts for a Royale release.
>
> Instead of the Flex "Last Call" process, I would like to try a different
> process and philosophy for Royale.  The script takes a while to run, but
> is relatively straightforward so I think we should try releasing whatever
> happens to be in the develop branches more often, maybe monthly or even
> more frequently than that.  So there won't be any "Last Call" since that
> slows down the release process while we wait for someone to finish some
> code or fix small things.
>
> I think we should try to cut a release during the first week of every
> month, and potentially more often than that if a release goes out with
> blocking problems.
>
> As such, we want to adopt a different philosophy to voting.  As
> recommended by Roy Fielding, we could take the approach of "better than
> the last release and not illegal".  And "not illegal" means truly breaking
> a law, not some policy issue.  I would say we would not release something
> that is in violation of the CatX handling policy though.
>
> So the process will be something like:  in the first week of every month
> (not necessarily on the 1st day of the month), someone will cut an RC and
> we'll vote on it, and if we didn't break something important and aren't
> breaking any laws and are handling CatX properly, we vote +1 and out it
> goes.  Most bugs should not hold up these releases.  If something is
> broken we try to fix it in a few days and hopefully out it goes then, but
> most other fixes just go in the develop branch and goes in the next
> release.  Then towards the end of the month, we try to find a volunteer to
> cut the next monthly release. If we can work together to get releases out
> quickly, I will be the RM for the first couple of releases to make sure
> the script holds up.
>
>
> If we ship a release and after it goes out, something is found and we want
> to release a fix right away, we will do that as well, even if that means
> that the first week of the month release is only a week later.
>
> Any objections?  Either way, the script completed building an RC, so I am
> going to send out vote and discuss emails for it so people will review it
> in case the script needs fixing.
>
> Thoughts?
> -Alex
>
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*