Re: [I] Binding with {} vs binding mxml (ConstantBinding) [royale-asjs]

[Gabe Harbs]

Try ContainerBinding. That should work with nested objects.

> On May 13, 2024, at 11:30 AM, mjesteve (via GitHub)  wrote:
> 
> 
> mjesteve commented on issue #1244:
> URL: https://github.com/apache/royale-asjs/issues/1244#issuecomment-2106961448
> 
>   The name "gives us a clue", that's what it is, but since it's the only bead 
> I've seen used in the examples, I thought I should use this one.
>   I identified 2 beads that I could use, according to basic-manifest.xml, 
> "ConstantBinding" and "SimpleBinding" but the latter didn't work for me 
> either.
>   I continue investigating.
> 
>   Thx.
> 
> 
> -- 
> This is an automated message from the Apache Git Service.
> To respond to the message, please log on to GitHub and use the
> URL above to go to the specific comment.
> 
> To unsubscribe, e-mail: issues-unsubscr...@royale.apache.org
> 
> For queries about this service, please contact Infrastructure at:
> us...@infra.apache.org
> 

Abstract getters and setters

[Gabe Harbs]

I just noticed that getters and setters cannot be abstract.

I don’t remember if this was discussed before. Is there an issue with adding 
that functionality?

Thanks,
Harbs

Re: HTMLX

[Gabe Harbs]

HTMX or HTMLX?

I assume you mean the former.

I wouldn’t really compare it to MXML and Royale. It really shines in multi-page 
applications which do rendering on the backend while not requiring full page 
refreshes.

My $0.02,
Harbs

> On Mar 20, 2024, at 12:05 PM, Hugo Ferreira  wrote:
> 
> Hi,
> 
> I came across to a video on YouTube about HTMLX
> Seems basically turn HTML (a markup language) e in a real programming
> language.
> Seems a very basic version of MXML/Flex.

Re: I can't compile the all framework

[Gabe Harbs]

FYI, this is what I use to do a complete rebuild of Royale:

(
  cd ~/Apache/royale-compiler
  ant wipe-all
  git pull
  cd ~/Apache/royale-typedefs
  ant wipe
  git pull
  cd ~/Apache/royale-asjs
  ant super-clean
  ant clean
  git pull
  ant all
  rsync -r -u ~/Apache/frameworks/libs/player 
~/Apache/royale-asjs/frameworks/libs
)


> On Mar 11, 2024, at 11:11 PM, Harbs  wrote:
> 
> Great!
> 
>> On Mar 11, 2024, at 12:05 PM, Hugo Ferreira  wrote:
>> 
>> Thank you problem solved.
>> 
>> Deleted all folders expect the source
>> ant clean
>> all all
>> 
>> Build successfull.
>> 
>> Harbs  escreveu (sábado, 9/03/2024 à(s) 21:30):
>> 
>>> (IntersectionObserver is a web api which needs the current typedefs to
>>> recognize)
>>> 
 On Mar 9, 2024, at 11:28 PM, Harbs  wrote:
 
 Make sure your royale-typedefs repo is up to date.
 
 Harbs
 
> On Mar 9, 2024, at 10:42 PM, Hugo Ferreira 
>>> wrote:
> 
> Hi,
> 
> For months that I can't build the all framework with ant -all
> I get the following error:
> 
> [java]
> 
>>> /Volumes/Data/SDK/apache-royale-src/apache-royale/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/InfiniteScroller.as(147):
> col: 20 Error: Call to a possibly undefined method IntersectionObserver.
> 
>  [java]
> 
>  [java] observer = new IntersectionObserver(handleItemIntersection, {
> 
>  [java]^
> 
>  [java]
> 
>  [java]
> 
>>> /Volumes/Data/SDK/apache-royale-src/apache-royale/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/InfiniteScroller.as(147):
> col: 20 Call to a possibly undefined method IntersectionObserver.
> 
>  [java]
> 
>  [java] observer = new IntersectionObserver(handleItemIntersection, {
> 
>  [java]^
> 
>  [java]
> 
>  [java] 4.010328448 seconds
> 
>  [java] Java Result: 2
> 
> 
> If I comment out the //observer = new
> IntersectionObserver(handleItemIntersection ... from the
>>> InfiniteScroller.as
> it compiles again.
> 
> There is no IntersectionObserver.as in the source and this is the reason
> ant fails.
 
>>> 
>>> 
> 

Re: TrustedHTML

[Gabe Harbs]

I guess I’ll try.

And IIRC, updating Closure Compiler was very complicated. Right?

> On Nov 28, 2023, at 6:46 PM, Josh Tynjala  wrote:
> 
> You can set the GOOG_HOME environment variable (or env.GOOG_HOME in
> env.properties) to use a custom Closure Library when building royale-asjs,
> instead of the version that we have pinned.
> 
> I seem to remember Alex mentioning that updating either Closure Compiler or
> Closure Library *sometimes* also requires updating the other. I don't see
> any mention of specific versions in either README file, though. So you
> might just need to try using an updated Closure Library and test if it
> works with the version of Closure Compiler that we're bundling.
> 
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
> 
> 
> On Tue, Nov 28, 2023 at 8:34 AM Gabe Harbs  wrote:
> 
>> It seems like our dependency of Closure Compiler is too old.
>> 
>> I have an app which runs inside Google Workspace and I’m having issues
>> running a debug version since Google enabled TrustedHTML restrictions.
>> https://developer.mozilla.org/en-US/docs/Web/API/TrustedHTML
>> 
>> The newer versions appear to support TrustedHTML.
>> 
>> 
>> https://github.com/google/closure-library/blob/7818ff7dc0b53555a7fb3c3427e6761e88bde3a2/closure/goog/base.js#L2996
>> 
>> Is there an issue with just swapping the closure-library version?
>> 
>> Harbs

TrustedHTML

[Gabe Harbs]

It seems like our dependency of Closure Compiler is too old.

I have an app which runs inside Google Workspace and I’m having issues running 
a debug version since Google enabled TrustedHTML 
restrictions.https://developer.mozilla.org/en-US/docs/Web/API/TrustedHTML

The newer versions appear to support TrustedHTML.

https://github.com/google/closure-library/blob/7818ff7dc0b53555a7fb3c3427e6761e88bde3a2/closure/goog/base.js#L2996

Is there an issue with just swapping the closure-library version?

Harbs

Re: Performance issue with Datagrid / last build download issue

[Gabe Harbs]

The job of InfiniteScroller is to tell you when the user scrolled down to the 
end of the list.

What to do when you get to the end of the list is up to you. `the most common 
use case is to load paged data. You would need to keep track of whether you 
have more paged data to get.

You’d probably have getMoreData() make an API call to get paged data if there’s 
more data pending.

SmoothDataLoader is complementary in that it’s useful for loading large amounts 
of data in a way that doesn’t freeze the UI.

HTH,
Harbs

> On May 6, 2023, at 11:27 AM, Hugo Ferreira  wrote:
> 
> I didn't quiet understand what this new head SmoothDataLoader does but I
> see that was created to work together with InfiniteScroller
> 
> Harbs  escreveu no dia quarta, 3/05/2023 à(s) 10:55:
> 
>> I added js:SmoothDataLoader as well.
>> 
>> The bead is expecting data as an array. It should be added using either
>> setData() (to replace the data) or appendData() to add more data to the
>> queue of data being added.
>> 
>> The strand does not need a dataProvider set, but it does need to be able
>> to handle collections and collection change events.
>> 
>> FYI, the SmoothDataLoader might trigger scrollEnd on the InfiniteScroller
>> while adding data, so if you use the two together, make sure you check
>> whether there’s pending data in the SmoothDataLoader before requesting more
>> data on the scrollEnd event.
>> 
>> The InfiniteScroller also does not handle adding a progress indicator to
>> the end of the list. If desired, that would need to be handled separately.
>> 
>> HTH,
>> Harbs
>> 
>>> On May 1, 2023, at 7:14 PM, Harbs  wrote:
>>> 
>>> I added InfiniteScroller.
>>> 
>>> You can use it like this:
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> If the scroll container is not the actual list, you should use it like
>> this:
>>> 
>>> 
>>> 
>>> > scrollContainer=“{scrollContainer}”/>
>>> 
>>> 
>>> 
>>> 
>>> I’ll try to add the other bead tomorrow…
>>> 
>>> Harbs
>>> 
 On Apr 26, 2023, at 12:46 PM, Hugo Ferreira 
>> wrote:
 
 I'm sold :)
 
 When you push that to github, please make a comment here.
 I will test it right a way ;)
 
 Harbs  escreveu no dia quarta, 26/04/2023 à(s)
>> 10:43:
 
> If you use IntersectionObservers, the callback is only invoked when the
> observed element comes into view. The beauty of the
>> IntersectionObservers
> is that it doesn’t matter how the element comes into view. It can be
>> by any
> kind of scrolling, window resize, or even by changing the visibility
>> of it.
> It’s very elegant and much more performant than listening to scroll
>> events.
> 
>> On Apr 26, 2023, at 12:32 PM, Hugo Ferreira 
> wrote:
>> 
>> But, don't forget that the user can grab the scroll bar and drop
> somewhere.
> 
> 
>>> 
>> 
>> 
>> 

Re: 0.9.10 Release

[Gabe Harbs]

I had some issues getting FunctionalTests to pass due to timing issues. It 
might not work reliably on all machines. You can probably [Ignore] the 
problematic one(s). Which ones fail?

> On May 4, 2023, at 11:24 PM, Yishay Weiss  wrote:
> 
> The encoding issues were fixed (had to set java_tool_options on CI server). 
> After running the approval script however I noticed I did not update 
> releasemgr/RELEASE_NOTES. Also, there is a unit test fail:
> 
> Suite: flexUnitTests.FunctionalTests
> 
> Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.492 sec
> 
> From: Yishay Weiss 
> Sent: Monday, May 1, 2023 10:28 AM
> To: dev@royale.apache.org 
> Subject: Re: 0.9.10 Release
> 
> Update on current status:
> 
> Thanks to Josh's fixes to compiler and typedefs we have reproducible binary 
> artifacts in maven build. The main release archives, however, still have some 
> issues:
> 
> a) Line ending inconsistency in source files. I think this is fixed by 
> changing git global settings on CI to core.autocrlf to 'input'.
> b) differences in PNG, gif, ico, mp3, mp4, ttf  for source files. I suspect 
> ant zip task is compressing these, so I'll have to change build script to 
> disable compression for those files.
> c) Encoding differences in txt, as, DEPENDENCIES source files. I will need to 
> figure out where this encoding happens, I suspect it's a zip task issue too.
> 
> From: Yishay Weiss 
> Sent: Thursday, April 27, 2023 3:25 PM
> To: dev@royale.apache.org 
> Subject: Re: 0.9.10 Release
> 
> Thanks, that worked.
> 
> From: Josh Tynjala 
> Sent: Tuesday, April 25, 2023 9:15 PM
> To: dev@royale.apache.org 
> Subject: Re: 0.9.10 Release
> 
> It looks like the jquery-1.9.js externs download was being cached by
> download-maven-plugin, and one machine had an older version than the other.
> We were skipping the cache for other .js externs downloads already, so I
> updated them all to skip the cache.
> 
> Hopefully, this will be the last difference. Give it another try!
> 
> --
> Josh Tynjala
> Bowler Hat LLC 
> 
> 
> On Thu, Apr 20, 2023 at 12:17 AM Yishay Weiss 
> wrote:
> 
>> I started another release candidate. Somehow, I'm getting a
>> reproducibility problem which did not exist before in type-defs.
>> 
>> If somebody wants to confirm  you can try to reproduce the problem with
>> the following step:
>> 
>> 
>> From the royale-typedefs repo:
>> 1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.10
>> -DskipTests=true
>> 
>> I had to  locally modify releasesteps.xml (line 122) to add CI
>> crendentials [1]. I still need to fix the permissions in CI.
>> 
>> What I'm seeing is that locally built
>> royale-typedefs-jquery-0.9.10-typedefs.swc does not match archived one.
>> 
>> [1] username="" password="***"
>> 
>> From: Josh Tynjala 
>> Sent: Monday, April 17, 2023 11:52 PM
>> To: dev@royale.apache.org 
>> Subject: Re: 0.9.10 Release
>> 
>> Alright, my commit today seems to do the trick. All SWC files in the
>> js/libs, frameworks/libs, and frameworks/js/libs directories are a binary
>> match when I compare the Maven distribution as built on macOS vs built on
>> Windows.
>> 
>> You need to make sure to pull the latest develop branch for both
>> royale-compiler and royale-asjs.
>> 
>> --
>> Josh Tynjala
>> Bowler Hat LLC 
>> 
>> 
>> On Sun, Apr 16, 2023 at 5:59 AM Yishay Weiss 
>> wrote:
>> 
 I still need to figure out the duplicate hoisted variables in MXRoyale.
>>> 
>>> I can confirm it's still happening. It does not happen on my machine with
>>> a simple "mvn clean install".
>>> 
>>> From: Josh Tynjala 
>>> Sent: Friday, April 7, 2023 2:01 AM
>>> To: dev@royale.apache.org 
>>> Subject: Re: 0.9.10 Release
>>> 
>>> My latest commits make the Jewel and JewelJS SWC files match between my
>>> macOS and Windows machines. I ended up having to switch to a different
>>> Maven Sass plugin because I realized the one we were using was no longer
>>> maintained, and it was misbehaving. This new plugin is based on the newer
>>> Sass that doesn't support CRLF output at all, so the changes I talked
>> about
>>> in my previous email ended up being a strict requirement.
>>> 
>>> I still need to figure out the duplicate hoisted variables in MXRoyale.
>>> I'll need to dive into that on another day.
>>> 
>>> --
>>> Josh Tynjala
>>> Bowler Hat LLC 
>>> 
>>> 
>>> On Thu, Apr 6, 2023 at 9:57 AM Josh Tynjala 
>>> wrote:
>>> 
 Some more findings:
 
 The difference in Jewel appears to be caused by defaults.css. The Maven
 build at some point was updated to force Sass to output CRLF on
>> Windows,
>>> to
 keep Git from saying that the file is modified after regenerating it.
 Unfortunately, this breaks the ability to do a cross-platform
>>> reproducible

Re: Player Global

[Gabe Harbs]

This went over my head a bit.

Currently, when I build Royale (withs wf support), I rsync a “player” folder 
which has playerglobal.swc into frameworks/libs to allow it to be used for 
compiling applications. I’m looking to get rid of that step and I’m not sure 
how we can facilitate that.

Harbs

> On May 4, 2023, at 8:53 PM, Josh Tynjala  wrote:
> 
> There's a swf.distribution Ant property that normally gets managed
> automatically. It get set to true when AIR_HOME is available, and false
> when AIR_HOME is not available. The availability of AIR_HOME (and
> PLAYERGLOBAL_HOME) is normally how the Ant build determines that it needs
> to build a SWF/JS distribution instead of a JS-only distribution.
> 
> As I recall, you can manually enable it with -Dswf.distribution=1 on the
> command line (or you can set it in env.properties, if you prefer), and this
> will force a SWF/JS distribution even when PLAYERGLOBAL_HOME and AIR_HOME
> are not set. When swf.distribution is set, but PLAYERGLOBAL_HOME and
> AIR_HOME are not set, it should look for the royale-typedefs versions of
> playerglobal.swc and airglobal.swc instead of the Adobe versions.
> 
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
> 
> 
> On Thu, May 4, 2023 at 12:20 AM Gabe Harbs  wrote:
> 
>> What’s the status to compiling player global? I remember Josh doing work
>> on creating our own version of player global so we wouldn’t have to rely on
>> the downloads from Adobe.
>> 
>> It does not seem to be added as part of the build process. Is there a
>> reason why not?
>> 
>> Thanks,
>> Harbs

Re: Mac M2 performance

[Gabe Harbs]

And the frameworks without tests (i.e. ant -Dskip-tests=true) took:

Total time: 3 minutes 1 second


> On May 4, 2023, at 10:53 AM, Gabe Harbs  wrote:
> 
> My Intel laptop fell and my screen broke. That was my impetus to buy a new 
> MacBook Pro. I just bought an M2 MacBook Pro and I figured I’d profile 
> compiling Royale. Here’s what I got:
> 
> A full compile of Royale including the compiler (i.e. ant all) took:
> 
> Total time: 6 minutes 52 seconds
> 
> 
> A compile of all the frameworks (i.e. ant) took:
> 
> Total time: 6 minutes 7 seconds
> 
> Harbs

Mac M2 performance

[Gabe Harbs]

My Intel laptop fell and my screen broke. That was my impetus to buy a new 
MacBook Pro. I just bought an M2 MacBook Pro and I figured I’d profile 
compiling Royale. Here’s what I got:

A full compile of Royale including the compiler (i.e. ant all) took:

Total time: 6 minutes 52 seconds


A compile of all the frameworks (i.e. ant) took:

Total time: 6 minutes 7 seconds

Harbs

Player Global

[Gabe Harbs]

What’s the status to compiling player global? I remember Josh doing work on 
creating our own version of player global so we wouldn’t have to rely on the 
downloads from Adobe.

It does not seem to be added as part of the build process. Is there a reason 
why not?

Thanks,
Harbs

Re: [royale-asjs] branch develop updated: Basic: Fix issue where in scenario of providing object in dataProvider contains fields either null or undefined causes display [object Object] instead of empt

[Gabe Harbs]

No. That’s probably not what you want. If there’s an empty string that should 
be used.

> On 12 Aug 2022, at 13:57, Piotr Zarzycki  wrote:
> 
> So maybe it's enough if I just made:
> 
> If (data[(obj as IHasLabelField).labelField]) ?
> 
> pt., 12 sie 2022 o 12:46 Gabe Harbs  napisał(a):
> 
>> FWIW: undefined == null is true. You don’t need to test for both null and
>> undefined.
>> 
>> 
>>>> On 12 Aug 2022, at 12:56, pio...@apache.org wrote:
>>> 
>>> This is an automated email from the ASF dual-hosted git repository.
>>> 
>>> piotrz pushed a commit to branch develop
>>> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
>>> 
>>> 
>>> The following commit(s) were added to refs/heads/develop by this push:
>>>new 9cf3840b26 Basic: Fix issue where in scenario of providing
>> object in dataProvider contains fields either null or undefined causes
>> display [object Object] instead of empty string
>>> 9cf3840b26 is described below
>>> 
>>> commit 9cf3840b2646f57a312a121db17a991766307fef
>>> Author: Piotr Zarzycki 
>>> AuthorDate: Fri Aug 12 11:54:54 2022 +0200
>>> 
>>>   Basic: Fix issue where in scenario of providing object in
>> dataProvider contains fields either null or undefined causes display
>> [object Object] instead of empty string
>>> 
>>>   Example of dp object: {firstName: "Piotr", lastName: null}
>>> ---
>>> .../royale/org/apache/royale/html/util/getLabelFromData.as | 10
>> +-
>>> 1 file changed, 9 insertions(+), 1 deletion(-)
>>> 
>>> diff --git
>> a/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/util/getLabelFromData.as
>> b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/util/getLabelFromData.as
>>> index 18aa873040..1581f0c21b 100644
>>> ---
>> a/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/util/getLabelFromData.as
>>> +++
>> b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/util/getLabelFromData.as
>>> @@ -65,9 +65,17 @@ package org.apache.royale.html.util
>>>}
>>> 
>>>var label:String = data["label"];
>>> -if(label != null){
>>> +if(label != null)
>>> +{
>>>return label;
>>>}
>>> +
>>> +if (obj is IHasLabelField && (obj as IHasLabelField).labelField
>> &&
>>> +(data[(obj as IHasLabelField).labelField] == null ||
>> data[(obj as IHasLabelField).labelField] == undefined))
>>> +{
>>> +return "";
>>> +}
>>> +
>>>return "" + data;
>>> 
>>>}
>>> 
>> 
> 
> 
> -- 
> 
> Piotr Zarzycki

Re: [royale-asjs] branch develop updated: Basic: Fix issue where in scenario of providing object in dataProvider contains fields either null or undefined causes display [object Object] instead of empt

[Gabe Harbs]

FWIW: undefined == null is true. You don’t need to test for both null and 
undefined.


> On 12 Aug 2022, at 12:56, pio...@apache.org wrote:
> 
> This is an automated email from the ASF dual-hosted git repository.
> 
> piotrz pushed a commit to branch develop
> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> 
> 
> The following commit(s) were added to refs/heads/develop by this push:
> new 9cf3840b26 Basic: Fix issue where in scenario of providing object in 
> dataProvider contains fields either null or undefined causes display [object 
> Object] instead of empty string
> 9cf3840b26 is described below
> 
> commit 9cf3840b2646f57a312a121db17a991766307fef
> Author: Piotr Zarzycki 
> AuthorDate: Fri Aug 12 11:54:54 2022 +0200
> 
>Basic: Fix issue where in scenario of providing object in dataProvider 
> contains fields either null or undefined causes display [object Object] 
> instead of empty string
> 
>Example of dp object: {firstName: "Piotr", lastName: null}
> ---
> .../royale/org/apache/royale/html/util/getLabelFromData.as | 10 +-
> 1 file changed, 9 insertions(+), 1 deletion(-)
> 
> diff --git 
> a/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/util/getLabelFromData.as
>  
> b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/util/getLabelFromData.as
> index 18aa873040..1581f0c21b 100644
> --- 
> a/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/util/getLabelFromData.as
> +++ 
> b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/util/getLabelFromData.as
> @@ -65,9 +65,17 @@ package org.apache.royale.html.util
> }
> 
> var label:String = data["label"];
> -if(label != null){
> +if(label != null)
> +{
> return label;
> }
> +
> +if (obj is IHasLabelField && (obj as IHasLabelField).labelField &&
> +(data[(obj as IHasLabelField).labelField] == null || 
> data[(obj as IHasLabelField).labelField] == undefined))
> +{
> +return "";
> +}
> +
> return "" + data;
> 
> }
> 

Re: Support for SVG in older browsers and Operating Systems.

[Gabe Harbs]

There is a ObjectMap class which uses WeakMap or Map and falls back to regular 
objects on platforms whether that is not supported.
http://royale.apache.org/asdoc/#!org.apache.royale.utils/ObjectMap 


It should be a decent replacement for Dictionary (including weak references). 
The only caveat is you need to use get() and set() instead of bracket access.

I just added documentation and cleaned it up a bit.

What’s interesting about that class is I needed to do some weird things with 
the methods to reassign them. They are not showing up in the ASDoc very well…

There might be a better way to declare the method (variable) proxies. Not sure…

HTH,
Harbs

> On Feb 24, 2018, at 9:10 PM, Greg Dove  wrote:
> 
> That might make porting some legacy Flex code a
> lot easier, for example because (iiuc) I think that means Dictionary with
> weak keys could be supported. [3] (and I know Harbs did something related
> to this in the past, maybe some sort of polyfill, can't recall exactly)

Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc libraries

[Gabe Harbs]

Copying is generally not done by the compiler itself. It’s usually handled by a 
compiler script or tooling.

> On Feb 24, 2018, at 8:53 PM, Carlos Rovira  wrote:
> 
> Hi Alex,
> 
> now the SWCs has all files needed, but when compile VividExample, the
> assets are not copied to VividExample target folder.
> How this is done?
> 
> Thanks
> 
> Carlos
> 
> 
> 
> 2018-02-24 19:48 GMT+01:00 Carlos Rovira  >:
> 
>> I get it with:
>> 
>> 
>> assets/*
>> ../src/main/resources/assets/*
>> 
>> 
>> Thanks!
>> 
>> Carlos
>> 
>> 
>> 
>> 2018-02-24 19:28 GMT+01:00 Alex Harui :
>> 
>>> I think any assets need to be listed in the  in the pom.xml
>>> (and for Ant, the src/main/config/compile*.xml files).
>>> AFAIK, there is no automatic including.  I believe you can use wildcards
>>> in the .
>>> 
>>> -Alex
>>> 
>>> On 2/24/18, 9:35 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>>>  wrote:
>>> 
 Hi,
 
 the final "environment" problem I've is that SVGs that I put in
 src/main/resources/assets are not in
 final VividBlueTheme-0.9.2-SNAPSHOT-js.swc
 
 I see it copied to target/classes as usual in maven build, but are not
 part
 of the theme swc file.
 
 it's something missing in the theme implementation? or maybe something I
 need to setup in pom.xml?
 
 
 thanks
 
 --
 Carlos Rovira
 https://na01.safelinks.protection.outlook.com/?url=http%3A%
>>> 2F%2Fabout.me%2
 Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7C973b4725a
>>> eaf4542d16308d5
 7bacfdd8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63655
>>> 0905283794125
 data=GeImt6g%2FONQJO8aKdkb%2BR8LgspIJ4jimlwrweM%2BCV8M%3D=0
>>> 
>>> 
>> 
>> 
>> --
>> 
>> 
>> 
>> Carlos Rovira
>> 
>> Director General
>> 
>> M: +34 607 22 60 05 <607%2022%2060%2005>
>> 
>> http://www.codeoscopic.com
>> 
>> 
>> Conócenos en 1 minuto! 
>> 
>> 
>> Este mensaje se dirige exclusivamente a su destinatario y puede contener
>> información privilegiada o confidencial. Si ha recibido este mensaje por
>> error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
>> proceda a su destrucción.
>> 
>> De la vigente Ley Orgánica de Protección de Datos (15/1999), le
>> comunicamos que sus datos forman parte de un fichero cuyo responsable es
>> CODEOSCOPIC S.A. La finalidad de dicho tratamiento es facilitar la
>> prestación del servicio o información solicitados, teniendo usted derecho
>> de acceso, rectificación, cancelación y oposición de sus datos dirigiéndose
>> a nuestras oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la
>> documentación necesaria.
>> 
>> 
> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira 

Re: TypeNames vs ClassName

[Gabe Harbs]

There’s some edge cases which seem problematic. One example:
ComboBoxBiew has the following:
input = new TextInput();
input.className = "ComboBoxTextInput";  

button = new TextButton();
button.className = "opt_org-apache.royale-html-ComboBox_Button";

Input and button are both external to the view class, but are managed by the 
view class. On the other hand, there is a chance that the user might wan to 
style them. I’m not sure whether className or typeNames is more appropriate 
here…

Harbs

> On Feb 23, 2018, at 11:03 AM, Gabe Harbs <harbs.li...@gmail.com> wrote:
> 
> I’ll help.
> 
>> On Feb 23, 2018, at 10:50 AM, Alex Harui <aha...@adobe.com.INVALID> wrote:
>> 
>> Quick note before I shut down for the night.
>> 
>> UIBase has both a typeNames and className property.  TypeNames is used to
>> emulate Flex-like type selectors in the CSS lookup.  It should be set in
>> the constructor and never set from outside the class.  There are a few
>> classes in Basic and lots of classes in MDL that should be upgraded to set
>> typeNames in the constructor.  Subclasses can append to the base class's
>> typeNames
>> 
>> className is the opposite.  It should never be set inside the component's
>> class.  It is for users of that component to set styles on the component.
>> 
>> Can we get a volunteer to clean this up?
>> 
>> Thanks,
>> -Alex
>> 
> 

Re: TypeNames vs ClassName

[Gabe Harbs]

I’ll help.

> On Feb 23, 2018, at 10:50 AM, Alex Harui  wrote:
> 
> Quick note before I shut down for the night.
> 
> UIBase has both a typeNames and className property.  TypeNames is used to
> emulate Flex-like type selectors in the CSS lookup.  It should be set in
> the constructor and never set from outside the class.  There are a few
> classes in Basic and lots of classes in MDL that should be upgraded to set
> typeNames in the constructor.  Subclasses can append to the base class's
> typeNames
> 
> className is the opposite.  It should never be set inside the component's
> class.  It is for users of that component to set styles on the component.
> 
> Can we get a volunteer to clean this up?
> 
> Thanks,
> -Alex
> 

Re: Removing the * selector

[Gabe Harbs]

Here’s a first stab at that:
https://github.com/apache/royale-compiler/wiki/Eclipse-Setup 


> On Feb 23, 2018, at 10:11 AM, Piotr Zarzycki  
> wrote:
> 
> Can you please describe how to setup debugger for Royale compiler on the
> Wiki?

Re: Removing the * selector

[Gabe Harbs]

I think Alex was suggesting to run it on the Moonshine *codebase*.

> On Feb 22, 2018, at 7:39 PM, Piotr Zarzycki  wrote:
> 
> Yep. That's what I suggested to Alina, because she was started to use
> Moonshine. I think it's doable also through the VSCode. In the end it is
> all about passing that argument as additional compiler options.
> 
> 
> 
> 2018-02-22 18:36 GMT+01:00 Alex Harui :
> 
>> Isn't Moonshine also a SWF-based app?  Could try it there too.
>> 
>> -Alex
>> 
>> On 2/22/18, 9:31 AM, "Piotr Zarzycki"  wrote:
>> 
>>> Carlos,
>>> 
>>> It would be great to get that report from your application!
>>> 
>>> Thanks, Piotr
>>> 
>>> 2018-02-22 18:17 GMT+01:00 Alex Harui :
>>> 
 Your point of view is valid, but it might depend on the kind of
 application.  Some might have 100's of views to port, others might only
 have 2 or 3 views and a million lines of business logic.
 
 In another thread I mentioned the -api-report option I added.  It would
 be
 interesting for folks to try getting API reports on their Flex apps so
 we
 can see what folks are using so we can use that in making decisions.
 
 My 2 cents,
 -Alex
 
 On 2/22/18, 8:39 AM, "carlos.rov...@gmail.com on behalf of Carlos
 Rovira"
  wrote:
 
> Without know nothing about the solution I want to share a though: I
 think
> the implementation of all the things related to visuals (and css is
 one of
> them) is completely different in Royale to what it was in flex, so
 maybe
> we
> should not be worried that CSS is not following main flex rules.
> For me UX in royale must be done from scratch, if someone is
 migrating, we
> can only provide some basic *structure* similar to what Flex was. But
> that's only some kind of guide and could mean around 5-10% of what they
> must to migrate. So this is the opposite to things more related to
> "business" (like the ArrayCollection disscussion we made some days
 ago),
> in
> this case, there's very few to save from a flex codebase point of view,
> and
> CSS is one of the things I don't expect to reuse if I come from flex
> codebase.
> 
> 
> 
> 2018-02-22 17:27 GMT+01:00 Alex Harui :
> 
>> Well, it might be a migration issue in the sense that you could use a
>> selector called "global" in Flex and it would become the default
 value
>> for
>> styles.
>> 
>> Flex and Royale CSS has non-compliant CSS in it like "cffHinting" or
>> "focusSkin" in Flex or "IStatesImpl" in Royale.  Non-compliant styles
>> are
>> not emitted to the final .css file since the browser has no use for
>> them,
>> but are kept in a data structure used by ValuesManager.  If you use
>> "global" for non-compliant style properties, it will work in Royale
 like
>> it did in Flex, but if you use "global" to try to set the fontFamily
 to
>> Gothic everywhere in your app it will not work in Royale as it did in
>> Flex.
>> 
>> Until this change we renamed "global" in the final CSS to "*" so it
>> would
>> have a more global effect, but I took that out because I'm not sure
 that
>> "*" is the equivalent since "*" actually has precedence over Type
>> Selectors.  I'm not quite sure how to create the true equivalent of
 Flex
>> global styles.
>> 
>> We could rename what I'm currently calling "global" in Royale to
>> something
>> else like "royale" and go back to renaming "global" to "*", but I
 think
>> that will end up with complaints.  I think it might be right for the
>> migration docs to mention this and offer alternatives like moving
 some
>> styles from global to "*" if they understand the impact of doing so.
>> Also, everything is currently a child of the Application so setting
>> Application styles should have a global effect, but I think both will
>> still override type selectors.
>> 
>> My 2 cents,
>> -Alex
>> 
>> On 2/22/18, 7:44 AM, "carlos.rov...@gmail.com on behalf of Carlos
>> Rovira"
>> 
>> wrote:
>> 
>>> Hi Andrew, this is new for Apache Royale since is how to deal with
 CSS
>> and
>>> how browsers manage it.
>>> So maybe not much relation with Flex in this case
>>> 
>>> Best
>>> 
>>> Carlos
>>> 
>>> 
>>> 
>>> 2018-02-22 13:27 GMT+01:00 Andrew Wetmore :
>>> 
 Is this a migration issue for Flex apps, or is this specific to
>> Royale?
 
 On Thu, Feb 22, 2018 at 5:29 AM, Alex Harui
>> 
 wrote:
 

Re: About Royale MDL Examples

[Gabe Harbs]

What do you think about putting the example in Royale-extras? 
https://github.com/royale-extras 

> On Feb 20, 2018, at 11:49 PM, Piotr Zarzycki  
> wrote:
> 
> MDLExample landed in my repository [1] and live [2]. It will be improved in
> the next weeks. :)
> 
> [1]
> https://github.com/piotrzarzycki21/TranspiledActionScript/tree/examples/Examples/MDLExample
> [2] https://transpiledactionscript.com/examples/MDLExample/
> 
> Thanks, Piotr
> 
> 
> 2018-02-19 23:07 GMT+01:00 Carlos Rovira :
> 
>> that would be great! ;)
>> 
>> 2018-02-19 20:26 GMT+01:00 Piotr Zarzycki :
>> 
>>> Ok let's leave it as is. I will take MDL to my repository. I don't want
>> to
>>> fight with Legal about that.
>>> 
>>> Carlos I will look into the Vivid soon. :)
>>> 
>>> Thanks, Piotr
>>> 
>>> 2018-02-19 20:23 GMT+01:00 Carlos Rovira :
>>> 
 Hi,
 
 as Alex said, Dave and Piotr understand my word incorrectly. Maybe I
 express incorrectly. So bad for myself.
 
 but anyway, I'm with Alex that we as "Apache Royale" should take
>> priority
 for our own UI set, and I prefer all the time that we could spend in
>> MDL
 examples will go to make our own set looks beautiful.
 
 In the end, whatever we interpret, is that Piotr can upload MDLExample
>> to
 their GitHub so make it accesible to anyone.
 
 That's my opinion on this, although I invest lot of time in MDLExample
>> a
 long with Piotr, my intention was to catch eyes and people for the
>>> project,
 but in the end I see clearly that any *imported* UI set (MDL,
>> Bootstrap,
 etc...) are not the way we should take. Our future depends in making
>> our
 own UI set.
 
 @Piotr, after testing with Vivid, I see clearly that we can mimic the
>>> same
 MDL looks, maybe not 100%, but very closely...and seems a doable task
>> if
 anyone is interesed as a theme, and with only one compilation
>> parameter,
>>> we
 can make the entire app looks completly different...I think that should
>>> be
 our goal! :)
 
 thanks
 
 
 
 2018-02-19 17:33 GMT+01:00 Alex Harui :
 
> @Dave,
> 
> I agree that you could interpret Carlos's words the way you did, but
>> I
> also think it is possible that Carlos was referring that the two MDL
> examples we are discussing aren't as important as some other things
>> on
>>> VP
> Legal's to-do list, which is fair and probably true and why I haven't
> pinged VP Legal.
> 
> @Piotr,
> 
> As Dave says, the way to escalate is to add a comment to the JIRA
>> issue
 or
> ask politely on legal-discuss.  Again, how important is it?
> 
> My 2 cents,
> -Alex
> 
> On 2/19/18, 8:23 AM, "Dave Fisher"  wrote:
> 
>> Carlos,
>> 
>> Please stop with the meme that the ASF doesn’t care about projects.
>> It
 is
>> not helpful and it is not true.
>> 
>> There are hundreds of projects. I suggested that you politely query
>> on
>> legal-discuss@.
>> 
>> Regards,
>> Dave
>> 
>> Sent from my iPhone
>> 
>>> On Feb 19, 2018, at 6:52 AM, Carlos Rovira <
>> carlosrov...@apache.org
 
>>> wrote:
>>> 
>>> Hi Piotr
>>> 
>>> my bet is that, as that projects are of no interest for ASF, you
>> can
>>> upload
>>> to your GitHub account directly without any word about it.
>>> 
>>> my 2cnt
>>> 
>>> 2018-02-19 11:48 GMT+01:00 Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com
> :
>>> 
 It's been several weeks since w have asked about advice. There is
>>> no
 response. How can we escalate this question higher ?
 
 Thanks, Piotr
 
 2018-01-30 19:58 GMT+01:00 Alex Harui >> :
 
> I created
> https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fissues
> .apache.org%2Fjira%2Fbrowse%2FLEGAL-363=02%
> 7C01%7Caharui%40adobe.c
> om%7C38e5360cf20847b34cd508d577b572dd%
>>> 7Cfa7b1b5a7b34438794aed2c178de
> cee
> 1%7C0%7C0%7C636546543554938163=
>>> cDHQDyV2kJw53r7ZQKODy3Itqx2bjl
> leb6
> f28MJeDgE%3D=0
> 
> -Alex
> 
>> On 1/30/18, 8:48 AM, "Piotr Zarzycki" <
>> piotrzarzyck...@gmail.com
 
>> wrote:
>> 
>> I think since release has been done we could raise a JIRA. I
>> will
>> try to
>> follow it and see how can I help. Will you raise jira since you
 have
>> started legal discussion ?
>> 
>> Thanks, Piotr
>> 
>> 2018-01-29 7:59 GMT+01:00 Alex Harui >> :
>> 
>>> Yes, filing a JIRA is probably the next step.  When do we want
>>> 

Re: Maven Builds

[Gabe Harbs]

OK. I asked there.

Thanks,
Harbs

> On Feb 21, 2018, at 6:42 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
> 
> The builds should not be taking 3 hours.  They never did before.  There
> could be something wrong with the build machine, the network, or the
> snapshot repo.  Feel free to ask builds.a.o.  I'm not going to spend any
> time looking at it.  You are also welcome to setup Maven builds without
> snapshot deployment on the apacheroyale CI server.
> 
> -Alex
> 
> On 2/21/18, 4:09 AM, "Gabe Harbs" <harbs.li...@gmail.com 
> <mailto:harbs.li...@gmail.com>> wrote:
> 
>> Just wondering:
>> 
>> If what’s taking the time is the transfer to Maven Central, I wonder if
>> there’s some way to do something like this:
>> 1. Initiate the upload
>> 2. Continue building the rest of the frameworks, uploading the artifacts
>> as it goes.
>> 3. When *everything* finishes building, check that all the artifacts were
>> successfully uploaded.
>> 
>> I know nothing about how these builds work, so I don’t even know if what
>> I’m writing makes any sense…
>> 
>> Harbs
>> 
>>> On Feb 21, 2018, at 1:57 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com>
>>> wrote:
>>> 
>>> It looks like it also upload Artifacts and failing on something. Try to
>>> setup Maven build on your local Machine to check something faster.
>>> 
>>> 2018-02-21 12:53 GMT+01:00 Piotr Zarzycki <piotrzarzyck...@gmail.com>:
>>> 
>>>> Hi Harbs,
>>>> 
>>>> Because each swc is being uploaded to Apache Maven central.
>>>> Unfortunately
>>>> it takes some time. If you would like to check something faster you
>>>> can use
>>>> pipeline which is not uploading as I remember artifacts [1]. Pipeline
>>>> should also run automatically but It's not and I don't know why.
>>>> 
>>>> [1] 
>>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuilds 
>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuilds>.
>>>> apache.org 
>>>> <http://apache.org/>%2Fjob%2FRoyale%2520Pipeline%2F=02%7C01%7Caharui%40adobe.
>>>> com%7C507e0a5a08ce48bd751008d5792406eb%7Cfa7b1b5a7b34438794aed2c178decee
>>>> 1%7C0%7C0%7C636548118007590652=C3I0Q%2F6OKAoOk9Mw8CKGCBbQIDJk0w8jR
>>>> R%2FToSBDtL0%3D=0
>>>> 
>>>> Thanks, Piotr
>>>> 
>>>> 
>>>> 2018-02-21 12:49 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com 
>>>> <mailto:harbs.li...@gmail.com>>:
>>>> 
>>>>> Why do the maven builds of royale-asjs take so long?
>>>>> 
>>>>> They are taking close to 3 hours per build. It seems to take a very
>>>>> long
>>>>> time “Downloading from apache-snapshots”. i.e. Downloaded from
>>>>> apache-snapshots:
>>>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Freposit 
>>>>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Freposit>
>>>>> ory.apache.org 
>>>>> <http://ory.apache.org/>%2Fs=02%7C01%7Caharui%40adobe.com 
>>>>> <http://40adobe.com/>%7C507e0a5a08ce48bd
>>>>> 751008d5792406eb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636548118
>>>>> 007590652=nm8wGkPjamOA%2BUTlJwhiOpGq4fwBK%2F2TwAab2fQ6m9I%3D
>>>>> rved=0
>>>>> napshots/org/apache/royale/framework/DragDrop/0.9.2-SNAPSHOT
>>>>> /maven-metadata.xml
>>>>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Freposi 
>>>>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Freposi>
>>>>> tory.apache.org 
>>>>> <http://tory.apache.org/>%2F=02%7C01%7Caharui%40adobe.com 
>>>>> <http://40adobe.com/>%7C507e0a5a08ce48bd
>>>>> 751008d5792406eb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636548118
>>>>> 007590652=fnl4UbdR15xXeNe5KehWq0XOF09utNs9%2Bx2PsFDcYks%3D
>>>>> ed=0
>>>>> snapshots/org/apache/royale/framework/DragDrop/0.9.2-SNAPSHO
>>>>> T/maven-metadata.xml> (1.2 kB at 3.1 kB/s)
>>>>> 
>>>>> That step can sit there for minutes at a time. Is there something
>>>>> which
>>>>> can be configured differently to make these builds go quicker?
>>>>> 
>>>>> Harbs
>>>> 
>>>> 
>>>> 
>>&g

Re: Maven Builds

[Gabe Harbs]

Just wondering:

If what’s taking the time is the transfer to Maven Central, I wonder if there’s 
some way to do something like this:
1. Initiate the upload
2. Continue building the rest of the frameworks, uploading the artifacts as it 
goes.
3. When *everything* finishes building, check that all the artifacts were 
successfully uploaded.

I know nothing about how these builds work, so I don’t even know if what I’m 
writing makes any sense…

Harbs

> On Feb 21, 2018, at 1:57 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com> wrote:
> 
> It looks like it also upload Artifacts and failing on something. Try to
> setup Maven build on your local Machine to check something faster.
> 
> 2018-02-21 12:53 GMT+01:00 Piotr Zarzycki <piotrzarzyck...@gmail.com>:
> 
>> Hi Harbs,
>> 
>> Because each swc is being uploaded to Apache Maven central. Unfortunately
>> it takes some time. If you would like to check something faster you can use
>> pipeline which is not uploading as I remember artifacts [1]. Pipeline
>> should also run automatically but It's not and I don't know why.
>> 
>> [1] https://builds.apache.org/job/Royale%20Pipeline/
>> 
>> Thanks, Piotr
>> 
>> 
>> 2018-02-21 12:49 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
>> 
>>> Why do the maven builds of royale-asjs take so long?
>>> 
>>> They are taking close to 3 hours per build. It seems to take a very long
>>> time “Downloading from apache-snapshots”. i.e. Downloaded from
>>> apache-snapshots: http://repository.apache.org/s
>>> napshots/org/apache/royale/framework/DragDrop/0.9.2-SNAPSHOT
>>> /maven-metadata.xml <http://repository.apache.org/
>>> snapshots/org/apache/royale/framework/DragDrop/0.9.2-SNAPSHO
>>> T/maven-metadata.xml> (1.2 kB at 3.1 kB/s)
>>> 
>>> That step can sit there for minutes at a time. Is there something which
>>> can be configured differently to make these builds go quicker?
>>> 
>>> Harbs
>> 
>> 
>> 
>> 
>> --
>> 
>> Piotr Zarzycki
>> 
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> <https://www.patreon.com/piotrzarzycki>*
>> 
> 
> 
> 
> -- 
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*

Re: Maven Builds

[Gabe Harbs]

I have never successfully managed to compile using Maven on my machine. I don’t 
know why.

For 99% of what I’ve done, Ant is just fine for me…

Harbs

> On Feb 21, 2018, at 1:57 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com> wrote:
> 
> It looks like it also upload Artifacts and failing on something. Try to
> setup Maven build on your local Machine to check something faster.
> 
> 2018-02-21 12:53 GMT+01:00 Piotr Zarzycki <piotrzarzyck...@gmail.com>:
> 
>> Hi Harbs,
>> 
>> Because each swc is being uploaded to Apache Maven central. Unfortunately
>> it takes some time. If you would like to check something faster you can use
>> pipeline which is not uploading as I remember artifacts [1]. Pipeline
>> should also run automatically but It's not and I don't know why.
>> 
>> [1] https://builds.apache.org/job/Royale%20Pipeline/
>> 
>> Thanks, Piotr
>> 
>> 
>> 2018-02-21 12:49 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
>> 
>>> Why do the maven builds of royale-asjs take so long?
>>> 
>>> They are taking close to 3 hours per build. It seems to take a very long
>>> time “Downloading from apache-snapshots”. i.e. Downloaded from
>>> apache-snapshots: http://repository.apache.org/s
>>> napshots/org/apache/royale/framework/DragDrop/0.9.2-SNAPSHOT
>>> /maven-metadata.xml <http://repository.apache.org/
>>> snapshots/org/apache/royale/framework/DragDrop/0.9.2-SNAPSHO
>>> T/maven-metadata.xml> (1.2 kB at 3.1 kB/s)
>>> 
>>> That step can sit there for minutes at a time. Is there something which
>>> can be configured differently to make these builds go quicker?
>>> 
>>> Harbs
>> 
>> 
>> 
>> 
>> --
>> 
>> Piotr Zarzycki
>> 
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> <https://www.patreon.com/piotrzarzycki>*
>> 
> 
> 
> 
> -- 
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*

Re: Maven Builds

[Gabe Harbs]

It looks like I don’t have permissions to see the pipeline configuration.

Even in pipeline, the asjs build seems to take about the same time.

> On Feb 21, 2018, at 1:53 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com> wrote:
> 
> Hi Harbs,
> 
> Because each swc is being uploaded to Apache Maven central. Unfortunately
> it takes some time. If you would like to check something faster you can use
> pipeline which is not uploading as I remember artifacts [1]. Pipeline
> should also run automatically but It's not and I don't know why.
> 
> [1] https://builds.apache.org/job/Royale%20Pipeline/
> 
> Thanks, Piotr
> 
> 
> 2018-02-21 12:49 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
> 
>> Why do the maven builds of royale-asjs take so long?
>> 
>> They are taking close to 3 hours per build. It seems to take a very long
>> time “Downloading from apache-snapshots”. i.e. Downloaded from
>> apache-snapshots: http://repository.apache.org/
>> snapshots/org/apache/royale/framework/DragDrop/0.9.2-
>> SNAPSHOT/maven-metadata.xml <http://repository.apache.org/
>> snapshots/org/apache/royale/framework/DragDrop/0.9.2-
>> SNAPSHOT/maven-metadata.xml> (1.2 kB at 3.1 kB/s)
>> 
>> That step can sit there for minutes at a time. Is there something which
>> can be configured differently to make these builds go quicker?
>> 
>> Harbs
> 
> 
> 
> 
> -- 
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*

Maven Builds

[Gabe Harbs]

Why do the maven builds of royale-asjs take so long?

They are taking close to 3 hours per build. It seems to take a very long time 
“Downloading from apache-snapshots”. i.e. Downloaded from apache-snapshots: 
http://repository.apache.org/snapshots/org/apache/royale/framework/DragDrop/0.9.2-SNAPSHOT/maven-metadata.xml
 

 (1.2 kB at 3.1 kB/s)

That step can sit there for minutes at a time. Is there something which can be 
configured differently to make these builds go quicker?

Harbs

Re: Maintain Release Notes List of changes(was: Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released)

[Gabe Harbs]

No I missed it. Pneumonia and all…

FWIW, it’s possible to add commit references to issues after a commit is made. 
You just include a hash in an issue comment.

> On Feb 20, 2018, at 7:13 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
> 
> I don't know if you saw my commit wizard idea.
> https://lists.apache.org/thread.html/5d94976d277729a8f34b77a0ec09e45678bbf5 
> <https://lists.apache.org/thread.html/5d94976d277729a8f34b77a0ec09e45678bbf5>
> d2d7111e411fb5fb14@%3Cdev.royale.apache.org 
> <http://3cdev.royale.apache.org/>%3E
> 
> I guess it won't help if you don't use command line for commits.  It
> should be possible to do any of the 3 you suggested.  The GitHub API seems
> to be relatively easy to use, and I tested the JSON2ASVO utility with some
> of the responses and it seems to work.  We just need to find the time to
> put something together.
> 
> -Alex
> 
> On 2/20/18, 8:28 AM, "Gabe Harbs" <harbs.li...@gmail.com 
> <mailto:harbs.li...@gmail.com>> wrote:
> 
>> +1
>> 
>> Some thoughts:
>> 1. We can have a utility which rewrites entries to a standard format
>> before release.
>> 2. We can have a form which takes the info and adds it to the release
>> notes.
>> 3. It might be interesting to have a Github integration which watches
>> Issues and when a commit closes a ticket, it creates an entry in the
>> release notes.
>> 
>> Harbs
>> 
>>> On Feb 20, 2018, at 6:05 PM, Alex Harui <aha...@adobe.com.INVALID>
>>> wrote:
>>> 
>>> If you want a particular format, help me write a wizard that will manage
>>> that.  I will not remember to get it right every time I commit.  I will
>>> not know what to use for a description unless we take the bug topic
>>> verbatim with any misspellings and other cruft.
>>> 
>>> My 2 cents,
>>> -Alex
>>> 
>>> On 2/20/18, 5:37 AM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com
>>> <mailto:piotrzarzyck...@gmail.com <mailto:piotrzarzyck...@gmail.com>>> 
>>> wrote:
>>> 
>>>> I see in release notes links to issues. I'm in favor of having
>>>> description
>>>> + eventually links.
>>>> 
>>>> - my description for a bug [Bug Number](link) - it will display nicely
>>>> on
>>>> GitHub.
>>>> 
>>>> I'm talking about this commit.
>>>> 
>>>> What do other thinks ?
>>>> 
>>>> Thanks, Piotr
>>>> 
>>>> 
>>>> 2018-02-14 23:13 GMT+01:00 Carlos Rovira <carlosrov...@apache.org 
>>>> <mailto:carlosrov...@apache.org>>:
>>>> 
>>>>> Ok Alex, that's great, so we'll be doing the work on RELEASE_NOTES
>>>>> file
>>>>> 
>>>>> thanks!
>>>>> 
>>>>> 2018-02-14 17:31 GMT+01:00 Alex Harui <aha...@adobe.com.invalid 
>>>>> <mailto:aha...@adobe.com.invalid>>:
>>>>> 
>>>>>> We already have this.  It is the RELEASE_NOTES file.  All ASF
>>>>>> releases
>>>>> are
>>>>>> supposed to have one so we should use it.  And as keepachangelog.com 
>>>>>> <http://keepachangelog.com/>
>>>>> says,
>>>>>> it is not the GitHub commit log.
>>>>>> 
>>>>>> IMO, it is not the Release Manager's job to fill this out.  It needs
>>>>> to
>>>>> be
>>>>>> maintained by every committer.  I know I'm really bad about filling
>>>>>> it
>>>>> out
>>>>>> which is why I proposed a Commit Wizard a few days ago.
>>>>>> 
>>>>>> IMO, there were some good feature enhancements in 0.9.1, like
>>>>>> NestedDataGridColumn, but nothing really notable.  The focus of 0.9.1
>>>>> was
>>>>>> to get the documentation published by making sure ASDoc and the
>>>>> examples
>>>>>> worked.  Also, there was only a few weeks between 0.9.0 and 0.9.1.
>>>>>> 
>>>>>> Also, I added links from the RELEASE_NOTES to our wiki.  That way we
>>>>> can
>>>>>> add late-breaking news after the release.  I think we should do the
>>>>> that
>>>>>> for every release.  But we should try to make the RELEASE_NOTES
>>>>> contain
>>>>>> most or all of the notable changes.
>>>>&g

Re: Public Vars

[Gabe Harbs]

For framework code which might be used in MXML, we’re probably going to have to 
stick to setters and getters.

For code which will not be used in MXML there’s no reason to not use public 
vars (unless it needs setter/getter logic). I’m suggesting that if Foo has some 
public var “baz”, and someone declares   
would generate a compiler error that bar is not set-able in MXML.

Does that make sense?

Harbs

> On Feb 20, 2018, at 8:43 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
> 
> I may not be understanding you, but the application developer likely
> didn't write the "public var" that is going to be a problem, some other
> component developer did.  The goal is to get the component developer to
> not use public vars.
> 
> Any application developer who uses MXMLComponents (an MXML file used as a
> component in another MXML file) is technically now a component developer
> and under the same restrictions.
> 
> And as folks develop Royale apps with modules, they will face similar
> restrictions I think.  I think we want to flag that.  I don't think the
> contexts are limited to MXML, Binding, and States, nor does the framework
> component developer know the context when they type "public var".
> 
> I did consider a flag that would have the JS output automatically generate
> a getter/setter for every public var.  But that would significantly fatten
> your app for 700 public vars.
> 
> Folks are welcome to try other options in the compiler.  I just did what
> was quick and I think will help us help folks migrating.
> 
> -Alex
> 
> On 2/20/18, 10:30 AM, "Gabe Harbs" <harbs.li...@gmail.com 
> <mailto:harbs.li...@gmail.com>> wrote:
> 
>> What about a different approach?
>> 
>> Maybe we can *disable* public vars in MXML, Binding and States?
>> 
>> If someone tries to use public vars in those contexts, they would get a
>> compiler error. Only setters would show up as sett-able attributes in
>> MXML.
>> 
>> If we can do that, we can probably get rid of @exports for pubic vars
>> which would probably make apps smaller.
>> 
>> Thoughts?
>> Harbs
>> 
>>> On Feb 20, 2018, at 8:23 PM, Alex Harui <aha...@adobe.com.INVALID>
>>> wrote:
>>> 
>>> As a said, it mainly matters for MXML, Binding, and States.
>>> 
>>> I believe it will matter in accessing modules and a module accessing the
>>> thing that loaded the module, and any other access by the original
>>> property name.
>>> 
>>> I think it will matter in accessing Value Objects that are instantiated
>>> in
>>> the code instead of externally if that Value Object is not [Bindable].
>>> IOW, if you take some JSON and convert it to a plain Objects and tell
>>> the
>>> compiler that it is one of your Value Objects, that should work, but if
>>> you then create a new instance of a Value Object and set its properties
>>> in
>>> the code, I think that won't always work.
>>> 
>>> Maybe we'll end up turning this flag off by default in MXMLC and on by
>>> default for COMPC or something like that.  The goal is to catch places
>>> in
>>> the framework where it could matter to increase the chances that the
>>> js-release will work on the first try.  The sweep definitely caught some
>>> things that needed to be changed.  I might have suppressed some warnings
>>> on things that will need to be changed, not sure.
>>> 
>>> Of course, I could be wrong...
>>> -Alex
>>> 
>>> On 2/20/18, 10:07 AM, "Gabe Harbs" <harbs.li...@gmail.com
>>> <mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>> wrote:
>>> 
>>>> I have over 700 public vars in my app and it handles minification just
>>>> fine.
>>>> 
>>>> AFAIK, public vars are only a problem for classes and properties used
>>>> in
>>>> MXML. Am I wrong?
>>>> 
>>>>> On Feb 20, 2018, at 7:26 PM, Alex Harui <aha...@adobe.com.INVALID 
>>>>> <mailto:aha...@adobe.com.INVALID>>
>>>>> wrote:
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> I just pushed compiler changes that will default to reporting a new
>>>>> warning if you have public var in your Royale code.  Public methods,
>>>>> getters and setters are fine, but public vars do not handle
>>>>> minification.
>>>>> 
>>>>> I also just pushed a sweep of the framework code to eliminate public
>>

Re: Public Vars

[Gabe Harbs]

What about a different approach?

Maybe we can *disable* public vars in MXML, Binding and States?

If someone tries to use public vars in those contexts, they would get a 
compiler error. Only setters would show up as sett-able attributes in MXML.

If we can do that, we can probably get rid of @exports for pubic vars which 
would probably make apps smaller.

Thoughts?
Harbs

> On Feb 20, 2018, at 8:23 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
> 
> As a said, it mainly matters for MXML, Binding, and States.
> 
> I believe it will matter in accessing modules and a module accessing the
> thing that loaded the module, and any other access by the original
> property name.
> 
> I think it will matter in accessing Value Objects that are instantiated in
> the code instead of externally if that Value Object is not [Bindable].
> IOW, if you take some JSON and convert it to a plain Objects and tell the
> compiler that it is one of your Value Objects, that should work, but if
> you then create a new instance of a Value Object and set its properties in
> the code, I think that won't always work.
> 
> Maybe we'll end up turning this flag off by default in MXMLC and on by
> default for COMPC or something like that.  The goal is to catch places in
> the framework where it could matter to increase the chances that the
> js-release will work on the first try.  The sweep definitely caught some
> things that needed to be changed.  I might have suppressed some warnings
> on things that will need to be changed, not sure.
> 
> Of course, I could be wrong...
> -Alex
> 
> On 2/20/18, 10:07 AM, "Gabe Harbs" <harbs.li...@gmail.com 
> <mailto:harbs.li...@gmail.com>> wrote:
> 
>> I have over 700 public vars in my app and it handles minification just
>> fine.
>> 
>> AFAIK, public vars are only a problem for classes and properties used in
>> MXML. Am I wrong?
>> 
>>> On Feb 20, 2018, at 7:26 PM, Alex Harui <aha...@adobe.com.INVALID>
>>> wrote:
>>> 
>>> Hi,
>>> 
>>> I just pushed compiler changes that will default to reporting a new
>>> warning if you have public var in your Royale code.  Public methods,
>>> getters and setters are fine, but public vars do not handle
>>> minification.
>>> 
>>> I also just pushed a sweep of the framework code to eliminate public var
>>> usage or add a directive to suppress the warning.  At some point in
>>> time I
>>> will probably sweep the examples, but I'm letting it spit a few warnings
>>> for now.  I hope to remove the * selector this week and that will
>>> require
>>> another sweep of the examples.
>>> 
>>> Not using public vars should increase the changes that your minified
>>> code
>>> will run.  I put some information about public var usage in the wiki.
>>> I'm
>>> not sure if or where it should go in the user doc.  Users may be able
>>> survive with more public vars since it mainly matters for vars used in
>>> MXML, Binding, and States.  But we want the framework to be clean, so if
>>> you see a warning from your framework code, please clean it up.
>>> 
>>> 
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c 
>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c>
>>> om%2Fapache%2Froyale-asjs%2Fwiki%2FPublic-Variables=02%7C01%7Caharui
>>> %40adobe.com 
>>> <http://40adobe.com/>%7C93e6c53f985c4a6ae7d408d5788cd84a%7Cfa7b1b5a7b34438794aed2c
>>> 178decee1%7C0%7C0%7C636547468674049910=Vxx36hMI3fS1q8PT34WnMWlniF3a
>>> LNONqTmEGghTUf0%3D=0
>>> 
>>> Thanks,
>>> -Alex

Re: Public Vars

[Gabe Harbs]

I have over 700 public vars in my app and it handles minification just fine.

AFAIK, public vars are only a problem for classes and properties used in MXML. 
Am I wrong?

> On Feb 20, 2018, at 7:26 PM, Alex Harui  wrote:
> 
> Hi,
> 
> I just pushed compiler changes that will default to reporting a new
> warning if you have public var in your Royale code.  Public methods,
> getters and setters are fine, but public vars do not handle minification.
> 
> I also just pushed a sweep of the framework code to eliminate public var
> usage or add a directive to suppress the warning.  At some point in time I
> will probably sweep the examples, but I'm letting it spit a few warnings
> for now.  I hope to remove the * selector this week and that will require
> another sweep of the examples.
> 
> Not using public vars should increase the changes that your minified code
> will run.  I put some information about public var usage in the wiki.  I'm
> not sure if or where it should go in the user doc.  Users may be able
> survive with more public vars since it mainly matters for vars used in
> MXML, Binding, and States.  But we want the framework to be clean, so if
> you see a warning from your framework code, please clean it up.
> 
> https://github.com/apache/royale-asjs/wiki/Public-Variables
> 
> Thanks,
> -Alex
> 

Re: Maintain Release Notes List of changes(was: Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released)

[Gabe Harbs]

+1

Some thoughts:
1. We can have a utility which rewrites entries to a standard format before 
release.
2. We can have a form which takes the info and adds it to the release notes.
3. It might be interesting to have a Github integration which watches Issues 
and when a commit closes a ticket, it creates an entry in the release notes.

Harbs

> On Feb 20, 2018, at 6:05 PM, Alex Harui  wrote:
> 
> If you want a particular format, help me write a wizard that will manage
> that.  I will not remember to get it right every time I commit.  I will
> not know what to use for a description unless we take the bug topic
> verbatim with any misspellings and other cruft.
> 
> My 2 cents,
> -Alex
> 
> On 2/20/18, 5:37 AM, "Piotr Zarzycki"  > wrote:
> 
>> I see in release notes links to issues. I'm in favor of having description
>> + eventually links.
>> 
>> - my description for a bug [Bug Number](link) - it will display nicely on
>> GitHub.
>> 
>> I'm talking about this commit.
>> 
>> What do other thinks ?
>> 
>> Thanks, Piotr
>> 
>> 
>> 2018-02-14 23:13 GMT+01:00 Carlos Rovira :
>> 
>>> Ok Alex, that's great, so we'll be doing the work on RELEASE_NOTES file
>>> 
>>> thanks!
>>> 
>>> 2018-02-14 17:31 GMT+01:00 Alex Harui :
>>> 
 We already have this.  It is the RELEASE_NOTES file.  All ASF releases
>>> are
 supposed to have one so we should use it.  And as keepachangelog.com
>>> says,
 it is not the GitHub commit log.
 
 IMO, it is not the Release Manager's job to fill this out.  It needs
>>> to
>>> be
 maintained by every committer.  I know I'm really bad about filling it
>>> out
 which is why I proposed a Commit Wizard a few days ago.
 
 IMO, there were some good feature enhancements in 0.9.1, like
 NestedDataGridColumn, but nothing really notable.  The focus of 0.9.1
>>> was
 to get the documentation published by making sure ASDoc and the
>>> examples
 worked.  Also, there was only a few weeks between 0.9.0 and 0.9.1.
 
 Also, I added links from the RELEASE_NOTES to our wiki.  That way we
>>> can
 add late-breaking news after the release.  I think we should do the
>>> that
 for every release.  But we should try to make the RELEASE_NOTES
>>> contain
 most or all of the notable changes.
 
 I think there will be major new features in 0.9.2 if it doesn't
>>> become a
 hot fix release.  I just pushed "fixed row height virtual lists" and
>>> will
 likely get variable row height working as well.  And of course, I did
>>> not
 update RELEASE_NOTES when I pushed those changes, so I will go and do
>>> that
 now ;-)
 
 My 2 cents,
 -Alex
 
 On 2/14/18, 5:15 AM, "Olaf Krueger"  wrote:
 
>> In Moonshine we are following this ->
>> https://na01.safelinks.protection.outlook.com/?url=
 http%3A%2F%2Fkeepachan
>> gelog.com%2Fen%2F1.0.0%2F=02%7C01%7Caharui%40adobe.com
 %7C4f310c6f286
>> 04f5391d708d573acfd7d%7Cfa7b1b5a7b34438794aed2c178de
 cee1%7C0%7C0%7C636542
>> 109181598814=Epgu%2BBIjQkIbbte9KXBIEFwg1YN2uZZ7a
 DEr%2BoGyvgU%3D
>> erved=0
> 
> +1, we also start using this format here ;-)
> 
> Olaf
> 
> 
> 
> --
> Sent from:
> https://na01.safelinks.protection.outlook.com/?url=
 http%3A%2F%2Fapache-roy
> ale-development.20373.n8.nabble.com%2F=02%7C01%7Caharui%
>>> 40adobe.com
 %7
> C4f310c6f28604f5391d708d573acfd7d%7Cfa7b1b5a7b34438794aed2c178de
 cee1%7C0%7
> C0%7C636542109181598814=n4CqdIGyGoEp2hanhb%
 2FtTrL8UvC8jWWmiEH%2FTWHb
> sIY%3D=0
 
 
>>> 
>>> 
>>> --
>>> Carlos Rovira
>>> 
>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me% 
>>> 
>>> 2Fcarlosrovira=02%7C01%7Caharui%40adobe.com 
>>> %7C74e5ff2b882c46c7cfdf08
>>> d578672402%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63654730674335656
>>> 9=cebcj%2BzMEiHGeB6K3kI%2Fi4rtDc4w%2BCjWPAf%2FnfjGSX4%3D=0
>>> 
>> 
>> 
>> 
>> -- 
>> 
>> Piotr Zarzycki
>> 
>> Patreon: 
>> *https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patr 
>> 
>> eon.com %2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com 
>> %7C74e5ff2b882c46
>> c7cfdf08d578672402%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365473067
>> 43356569=aM%2FQpF7A6bDHtDARJM4wUWaA9oE7OHMNbGaNEIe9wbA%3D=0
>> > 
>> eon.com %2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com 
>> %7C74e5ff2b882c46
>> 

Re: [royale-asjs] branch develop updated: Revert "Added .md extension to RELEASE_NOTES"

[Gabe Harbs]

We don’t *have to*, but it looks *WAY* nicer on Github.

From what I’ve seen other projects use wildly different practices when it comes 
to release notes, but it seems pretty common to have “nice” release notes. In 
fact most projects I’ve seen seem to have a styled web page which displays 
release notes.

From what I’ve seen, many projects don’t even seem to be keeping their release 
notes in their repos.

I’m not sure where to read the release notes for Flink.
https://github.com/apache/flink <https://github.com/apache/flink>

Cloudstack use CHANGES.md which then seems to populate a nicely designed web 
page
https://github.com/apache/cloudstack <https://github.com/apache/cloudstack>
https://github.com/apache/cloudstack/blob/master/CHANGES.md 
<https://github.com/apache/cloudstack/blob/master/CHANGES.md>
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.6.0/ 
<http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.6.0/>

Arrow uses a CHANGELOG.md file which then gets populated to a web page.
https://github.com/apache/arrow/blob/master/CHANGELOG.md 
<https://github.com/apache/arrow/blob/master/CHANGELOG.md>
http://arrow.apache.org/release/0.8.0.html 
<http://arrow.apache.org/release/0.8.0.html>

etc.

I think we can do whatever works nicely…

Thanks,
Harbs

> On Feb 20, 2018, at 6:03 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
> 
> Why do we have to use markdown in RELEASE_NOTES.  Are other ASF projects
> doing that?
> 
> -Alex
> 
> On 2/20/18, 5:43 AM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com 
> <mailto:piotrzarzyck...@gmail.com>> wrote:
> 
>> Maybe we can exclude from RAT check this file. It is failed because it
>> doesn't have Apache header license.
>> 
>> Let me look today evening into options of exclusion some files from RAT
>> check.
>> 
>> Thanks, Piotr
>> 
>> 2018-02-20 14:08 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
>> 
>>> Can someone more familiar with the maven build look into this?
>>> 
>>> Thanks,
>>> Harbs
>>> 
>>>> On Feb 20, 2018, at 3:06 PM, ha...@apache.org wrote:
>>>> 
>>>> This is an automated email from the ASF dual-hosted git repository.
>>>> 
>>>> harbs pushed a commit to branch develop
>>>> in repository 
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.a 
>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.a>
>>> pache.org 
>>> <http://pache.org/>%2Frepos%2Fasf%2Froyale-asjs.git=02%7C01%7Caharui%40adobe.c
>>> om%7C50a4e8f572da474086c808d57867f756%7Cfa7b1b5a7b34438794aed2c178decee1%
>>> 7C0%7C0%7C636547310280500614=H4lG3NGh3Q2B0wGVk25nqxHlZWc0bGd0TqrTUV
>>> 9fqd8%3D=0
>>>> 
>>>> 
>>>> The following commit(s) were added to refs/heads/develop by this push:
>>>>new aa03fac  Revert "Added .md extension to RELEASE_NOTES"
>>>> aa03fac is described below
>>>> 
>>>> commit aa03fac44b84f7f07a18682cb5bf456f24b7ef05
>>>> Author: Harbs <ha...@in-tools.com <mailto:ha...@in-tools.com>>
>>>> AuthorDate: Tue Feb 20 15:06:11 2018 +0200
>>>> 
>>>>   Revert "Added .md extension to RELEASE_NOTES"
>>>> 
>>>>   This reverts commit bb5499b394cf6c9f36515c3f6883202116d49e3f.
>>>> 
>>>>   It looks like the MAVEN build does not like this name change.
>>>>   I think the maven build should be fixed and we should use the .md
>>> extension.
>>>> ---
>>>> RELEASE_NOTES.md => RELEASE_NOTES | 0
>>>> 1 file changed, 0 insertions(+), 0 deletions(-)
>>>> 
>>>> diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES
>>>> similarity index 100%
>>>> rename from RELEASE_NOTES.md
>>>> rename to RELEASE_NOTES
>>>> 
>>>> --
>>>> To stop receiving notification emails like this one, please contact
>>>> ha...@apache.org <mailto:ha...@apache.org>.
>>> 
>>> 
>> 
>> 
>> -- 
>> 
>> Piotr Zarzycki
>> 
>> Patreon: 
>> *https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patr 
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patr>
>> eon.com <http://eon.com/>%2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com 
>> <http://40adobe.com/>%7C50a4e8f572da47
>> 4086c808d57867f756%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365473102
>> 80500614=0iB06Uoq8M3Nj%2BMViiIB9AZqxEdIVSKkSKBuDurNKt8%3D=0
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patr 
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patr>
>> eon.com <http://eon.com/>%2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com 
>> <http://40adobe.com/>%7C50a4e8f572da47
>> 4086c808d57867f756%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365473102
>> 80500614=0iB06Uoq8M3Nj%2BMViiIB9AZqxEdIVSKkSKBuDurNKt8%3D=0
>>> *

Re: [royale-asjs] branch develop updated: Revert "Added .md extension to RELEASE_NOTES"

[Gabe Harbs]

Can someone more familiar with the maven build look into this?

Thanks,
Harbs

> On Feb 20, 2018, at 3:06 PM, ha...@apache.org wrote:
> 
> This is an automated email from the ASF dual-hosted git repository.
> 
> harbs pushed a commit to branch develop
> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> 
> 
> The following commit(s) were added to refs/heads/develop by this push:
> new aa03fac  Revert "Added .md extension to RELEASE_NOTES"
> aa03fac is described below
> 
> commit aa03fac44b84f7f07a18682cb5bf456f24b7ef05
> Author: Harbs 
> AuthorDate: Tue Feb 20 15:06:11 2018 +0200
> 
>Revert "Added .md extension to RELEASE_NOTES"
> 
>This reverts commit bb5499b394cf6c9f36515c3f6883202116d49e3f.
> 
>It looks like the MAVEN build does not like this name change.
>I think the maven build should be fixed and we should use the .md 
> extension.
> ---
> RELEASE_NOTES.md => RELEASE_NOTES | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> 
> diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES
> similarity index 100%
> rename from RELEASE_NOTES.md
> rename to RELEASE_NOTES
> 
> -- 
> To stop receiving notification emails like this one, please contact
> ha...@apache.org.

Re: Page linked to from license page no longer exists

[Gabe Harbs]

Cool. Sorry for the noise.

> On Feb 17, 2018, at 8:33 PM, OmPrakash Muppirala <bigosma...@gmail.com> wrote:
> 
> I already pushed a fix for this.
> 
> Thanks,
> Om
> 
> On Feb 17, 2018 8:50 AM, "Gabe Harbs" <harbs.li...@gmail.com> wrote:
> 
>> This page has quite a few different variations:
>> https://commons.wikimedia.org/wiki/Category:SVG_maps_of_the_United_States
>> <https://commons.wikimedia.org/wiki/Category:SVG_maps_of_the_United_States
>>> 
>> 
>>> On Feb 17, 2018, at 6:46 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>>> 
>>> What about this one?
>>> https://commons.wikimedia.org/wiki/File:Blank_US_Map_(
>> states_only).svg#file <https://commons.wikimedia.
>> org/wiki/File:Blank_US_Map_(states_only).svg#file>
>>> 
>>>> On Feb 16, 2018, at 6:49 PM, OmPrakash Muppirala <bigosma...@gmail.com
>> <mailto:bigosma...@gmail.com>> wrote:
>>>> 
>>>> I'll look into it.
>>>> 
>>>> Thanks,
>>>> Om
>>>> 
>>>> On Feb 16, 2018 8:35 AM, "Alex Harui" <aha...@adobe.com.invalid
>> <mailto:aha...@adobe.com.invalid>> wrote:
>>>> 
>>>>> Bummer.  Looks like WikiPedia decided to remove it.  I think Om
>>>>> contributed that, so I guess we should let him decide whether to find
>>>>> another source for the data or remove the example.
>>>>> 
>>>>> My 2 cents,
>>>>> -Alex
>>>>> 
>>>>> On 2/16/18, 3:17 AM, "Andrew Wetmore" <cottag...@gmail.com > cottag...@gmail.com>> wrote:
>>>>> 
>>>>>> Hi:
>>>>>> 
>>>>>> on Welcome/licenses.md there is this passage:
>>>>>> 
>>>>>> The map coordinates in examples/native/USStatesMap/src/MapCoords.as
>> were
>>>>>> placed into the Public Domain by its author. See:
>>>>>> https://na01.safelinks.protection.outlook.com/?url= <
>> https://na01.safelinks.protection.outlook.com/?url=>
>>>>> https%3A%2F%2Fen.wikipe
>>>>>> dia.org <http://dia.org/>%2Fwiki%2FFile%3AUSA_CIA_Map.svg%
>> 23file=02%
>>>>> 7C01%7Caharui%40ado
>>>>>> be.com <http://be.com/>%7C8c30db66c9c448a2a77708d5752ed58e%
>> 7Cfa7b1b5a7b34438794aed2c178de
>>>>> ce
>>>>>> e1%7C0%7C0%7C636543766369921734=EVjU7uzApzAiAIf8CoayF6n7kP6LQs
>>>>> WtxHHZ
>>>>>> zqTNb5M%3D=0
>>>>>> 
>>>>>> When I click that link I get a message that the file has been deleted.
>>>>>> Since this is license-related, do we need to hunt out a replacement
>>>>>> source?
>>>>>> 
>>>>>> --
>>>>>> Andrew Wetmore
>>>>>> 
>>>>>> https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fcottage14 <https://na01.safelinks.
>> protection.outlook.com/?url=http%3A%2F%2Fcottage14>
>>>>> .
>>>>>> blogspot.com <http://blogspot.com/>%2F=02%7C01%7Caharui%40adobe.
>> com <http://40adobe.com/>%
>>>>> 7C8c30db66c9c448a2a77708
>>>>>> d5752ed58e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>>>>> 7C636543766369921734
>>>>>> =dwjkXL%2BDCfUpUYMLL9B4Mhpw%2BIjT%
>> 2FlNEeEkpDMgMX8M%3D=0
>>>>> 
>>>>> 
>>> 
>> 
>> 

Re: -remove-circulars

[Gabe Harbs]

FWIW, none of the apps I built to date compiled correctly without 
-remove-circulars.

I’m not sure I completely understand the issue. Will your proposed solution 
make minified apps fatter, or just the debug apps?

Can you point me to where in the ASDoc code the problem is so In can understand 
the problem better?

Harbs

> On Feb 17, 2018, at 7:40 AM, Alex Harui  wrote:
> 
> Hi Folks,
> 
> I've spent the last day or so trying to get ASDoc to run when minified.  I
> created a JSON to ValueObjects utility which helped a lot.  It still isn't
> completely running, but it appears that we need to stop pruning classes
> that are only used in type annotations.  This will make most apps a little
> fatter, but also require all apps to use remove-circulars.
> 
> What do folks think about that?  The compiler used to prune classes from a
> file's goog.requires list that were never instantiated or type-checked in
> that file.  So, for ASDoc, the ASDocClass ValueObject that represents the
> JSON data for the ASDoc is never instantiated by the class that consumes
> it.  The instances are created by JSON.  The ASDocClass is only mentioned
> in JSDoc to declare some variable as being of type ASDoc.  That enabled us
> to remove that class from the requires list since that ASDocClass is never
> referenced by operational code.  Removing that goog.require helped
> eliminate circular goog.require references that the closure compiler
> disallows.  That kicked HTMLElementWrapper out of the app for example.
> But it appears that by removing that goog.require, the compiler didn't
> know that the ASDocClass properties were exported and it renamed some of
> them resulting in problems in js-release.  So by leaving more
> goog.requires in the code we get better support against renaming, but we
> also bring back more circularities and now even HelloWorld would need
> -remove-circulars.
> 
> An alternative that would allow a few more apps to not need
> remove-circulars is to modify a few of our examples and classes to
> eliminate circularities.  HelloWorld only has 3.  But 2 of them are
> IParent/IChild and IStrand/IBead.  It seems "right" to have IParent
> reference IChild and vice versa.  Same for IStrand and IBead.  I'm not
> quite sure what the answer is.  Maybe IParent can reference IChild, but
> IChild does not reference its IParent.  I guess you could make an
> IParentedChild interface with the parent property and concrete children
> implement both IChild and IParentedChild.  That seems wrong and overly
> complicated.
> 
> Yet another option, which is recommended by some folks in the Closure
> Compiler community but doesn't fit well with the ActionScript language is
> to define both IChild and IParent in the same file.  I do not want to
> spend the time modifying the compiler for that.  It might be practical to
> merge the files as part of the Ant and Maven builds.  But again, that will
> take time as well.
> 
> That said, requiring remove-circulars always doesn't seem quite right
> either.
> 
> Thoughts?
> -Alex
> 
> 
> 

Re: Page linked to from license page no longer exists

[Gabe Harbs]

This page has quite a few different variations:
https://commons.wikimedia.org/wiki/Category:SVG_maps_of_the_United_States 
<https://commons.wikimedia.org/wiki/Category:SVG_maps_of_the_United_States>

> On Feb 17, 2018, at 6:46 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
> 
> What about this one?
> https://commons.wikimedia.org/wiki/File:Blank_US_Map_(states_only).svg#file 
> <https://commons.wikimedia.org/wiki/File:Blank_US_Map_(states_only).svg#file>
> 
>> On Feb 16, 2018, at 6:49 PM, OmPrakash Muppirala <bigosma...@gmail.com 
>> <mailto:bigosma...@gmail.com>> wrote:
>> 
>> I'll look into it.
>> 
>> Thanks,
>> Om
>> 
>> On Feb 16, 2018 8:35 AM, "Alex Harui" <aha...@adobe.com.invalid 
>> <mailto:aha...@adobe.com.invalid>> wrote:
>> 
>>> Bummer.  Looks like WikiPedia decided to remove it.  I think Om
>>> contributed that, so I guess we should let him decide whether to find
>>> another source for the data or remove the example.
>>> 
>>> My 2 cents,
>>> -Alex
>>> 
>>> On 2/16/18, 3:17 AM, "Andrew Wetmore" <cottag...@gmail.com 
>>> <mailto:cottag...@gmail.com>> wrote:
>>> 
>>>> Hi:
>>>> 
>>>> on Welcome/licenses.md there is this passage:
>>>> 
>>>> The map coordinates in examples/native/USStatesMap/src/MapCoords.as were
>>>> placed into the Public Domain by its author. See:
>>>> https://na01.safelinks.protection.outlook.com/?url= 
>>>> <https://na01.safelinks.protection.outlook.com/?url=>
>>> https%3A%2F%2Fen.wikipe
>>>> dia.org <http://dia.org/>%2Fwiki%2FFile%3AUSA_CIA_Map.svg%23file=02%
>>> 7C01%7Caharui%40ado
>>>> be.com 
>>>> <http://be.com/>%7C8c30db66c9c448a2a77708d5752ed58e%7Cfa7b1b5a7b34438794aed2c178de
>>> ce
>>>> e1%7C0%7C0%7C636543766369921734=EVjU7uzApzAiAIf8CoayF6n7kP6LQs
>>> WtxHHZ
>>>> zqTNb5M%3D=0
>>>> 
>>>> When I click that link I get a message that the file has been deleted.
>>>> Since this is license-related, do we need to hunt out a replacement
>>>> source?
>>>> 
>>>> --
>>>> Andrew Wetmore
>>>> 
>>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14 
>>>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14>
>>> .
>>>> blogspot.com <http://blogspot.com/>%2F=02%7C01%7Caharui%40adobe.com 
>>>> <http://40adobe.com/>%
>>> 7C8c30db66c9c448a2a77708
>>>> d5752ed58e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>>> 7C636543766369921734
>>>> =dwjkXL%2BDCfUpUYMLL9B4Mhpw%2BIjT%2FlNEeEkpDMgMX8M%3D=0
>>> 
>>> 
> 

Re: Page linked to from license page no longer exists

[Gabe Harbs]

What about this one?
https://commons.wikimedia.org/wiki/File:Blank_US_Map_(states_only).svg#file 


> On Feb 16, 2018, at 6:49 PM, OmPrakash Muppirala  wrote:
> 
> I'll look into it.
> 
> Thanks,
> Om
> 
> On Feb 16, 2018 8:35 AM, "Alex Harui"  wrote:
> 
>> Bummer.  Looks like WikiPedia decided to remove it.  I think Om
>> contributed that, so I guess we should let him decide whether to find
>> another source for the data or remove the example.
>> 
>> My 2 cents,
>> -Alex
>> 
>> On 2/16/18, 3:17 AM, "Andrew Wetmore"  wrote:
>> 
>>> Hi:
>>> 
>>> on Welcome/licenses.md there is this passage:
>>> 
>>> The map coordinates in examples/native/USStatesMap/src/MapCoords.as were
>>> placed into the Public Domain by its author. See:
>>> https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fen.wikipe
>>> dia.org%2Fwiki%2FFile%3AUSA_CIA_Map.svg%23file=02%
>> 7C01%7Caharui%40ado
>>> be.com%7C8c30db66c9c448a2a77708d5752ed58e%7Cfa7b1b5a7b34438794aed2c178de
>> ce
>>> e1%7C0%7C0%7C636543766369921734=EVjU7uzApzAiAIf8CoayF6n7kP6LQs
>> WtxHHZ
>>> zqTNb5M%3D=0
>>> 
>>> When I click that link I get a message that the file has been deleted.
>>> Since this is license-related, do we need to hunt out a replacement
>>> source?
>>> 
>>> --
>>> Andrew Wetmore
>>> 
>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14
>> .
>>> blogspot.com%2F=02%7C01%7Caharui%40adobe.com%
>> 7C8c30db66c9c448a2a77708
>>> d5752ed58e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> 7C636543766369921734
>>> =dwjkXL%2BDCfUpUYMLL9B4Mhpw%2BIjT%2FlNEeEkpDMgMX8M%3D=0
>> 
>> 

Re: How to install Nightly build through NPM

[Gabe Harbs]

Cool! I didn’t know you could do that.

Should we add this info to the “developer” documentation?

Harbs

> On Feb 16, 2018, at 6:48 PM, OmPrakash Muppirala  wrote:
> 
> You can just do npm install -g  
> That should install the nightly for you.
> 
> Thanks,
> Om
> 
> On Feb 16, 2018 5:49 AM, "Piotr Zarzycki"  wrote:
> 
>> Hi Guys,
>> 
>> Is it possible to install Nightly build of Royale through NPM ? I need to
>> check some scenario with Moonshine on Mac platform.
>> 
>> Thanks,
>> --
>> 
>> Piotr Zarzycki
>> 
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> *
>> 

Re: Introducing Royale CLI tool

[Gabe Harbs]

Very cool! Great initiative!

I’ll try to give it a spin later.

Is there a way of creating different templates for the “new” command?

BTW, it would be really great to try to stick to dog-fooding to have as many 
samples of Royale use as possible.

This tool can be written in ActionScript and compiled for node.js using Royale.

Harbs

> On Feb 15, 2018, at 10:16 AM, OmPrakash Muppirala  wrote:
> 
> As I was trying to write a `Setting up Royale with npm `blog post, I
> realized that things could be much easier for npm users.  So, I built the
> Royale CLI tool.  It takes inspiration from the create-react-app and the
> angular cli projects.
> 
> Here are the details:
> 
> *To Install: *
> npm install @apache-royale/royale-js -g
> npm install @apache-royale/cli -g
> 
> After installation:
> 
> *Help *
> royale help
> 
> *Setup *
> royale new  my-royale-app
> cd my-royale-app
> 
> This creates a simple app: my-royale-app/src/Main.mxml
> 
> 
> *Run in debug mode *
> royale serve:debug
> 
> Compiles the project in debug mode
> Compiles with source map option
> Starts a http server and serves the files from the bin/js-debug directory
> Opens the default browser and navigates to http://localhost:3000
> Listens to src folder
> When any file changes, it will recompile the app
> Automatically reloads the browser to show the updated application
> 
> *Run in release mode *
> royale serve:release
> 
> Compiles the project in release mode
> Starts a http server and serves the files from the bin/js-release
> directory
> Opens the default browser and navigates to http://localhost:3001
> 
> 
> Please test and provide feedback.  It would be greatly appreciated.
> 
> Thanks,
> Om

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released

[Gabe Harbs]

We probably should maintain a changelog which gets modified as things are 
developed.

> On Feb 14, 2018, at 2:39 PM, Carlos Rovira  wrote:
> 
> Hi just one more thing, for next release, since this is already done and
> announced.
> 
> People in twitter and facebook asked about "what's changed" when released
> 0.9.0 (in comparison with FlexJS latest release)
> 
> My response was that 0.9.0 was a first release here and there was no "list
> of changes". But I think people expect for next release see what is done
> and what to expect.
> 
> If we don't make some "Release Notes" with a list of changes, people out
> there will not know what's happening here. Only people working on the
> project will know what's change and maybe even only know about what changes
> he made, but not changes made by other contributors.
> 
> So I think that is very important to communicate in each release the "diff"
> between releases so people understand what's going on, and we need to
> communicate it through blog post, twitter, facebook, and whatever other
> via. If not we'll be working for us, and only us will know what's going on.
> 
> 
> 
> 
> 
> 2018-02-13 23:15 GMT+01:00 Jason Guild :
> 
>> Please pull the first sentence from the 0.9.0 blog announcement that
>> Carlos recently worked on.
>> It reads better and is grammatically correct.
>> 
>> 
>> On 2/13/2018 12:15 PM, Alex Harui wrote:
>> 
>>> We will wait a bit for other feedback and let the mirrors finish
>>> propagating.  I'll post it in about 8 hours if no other feedback.
>>> 
>>> -Alex
>>> 
>>> On 2/13/18, 1:00 PM, "Piotr Zarzycki"  wrote:
>>> 
>>> Go on and announce. I will fill GitHub release once it will be done! :)
 
 Thanks,
 Piotr
 
 2018-02-13 21:57 GMT+01:00 Andrew Wetmore :
 
 This announcement seems clear and inviting.
> 
> On Tue, Feb 13, 2018 at 3:06 PM, Alex Harui 
> wrote:
> 
> Please comment on the draft below.
>> 
>> Thoughts?
>> -Alex
>> 
>> 
>> 
> --
> Andrew Wetmore
> 
> 
> https://na01.safelinks.protection.outlook.com/?url=http%3A%
> 2F%2Fcottage14
> .blogspot.com%2F=02%7C01%7Caharui%40adobe.com%7Cd4c77f7
> efac24c43527b
> 08d57324d7ed%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636541524457865
> 491=i2PjCF4AaKmM70dq489Z60snqnKXjufTQU6iTKe34Jg%3D=0
> 
> 
 
 --
 
 Piotr Zarzycki
 
 Patreon:
 *https://na01.safelinks.protection.outlook.com/?url=https%
 3A%2F%2Fwww.patr
 eon.com%2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com%7C
 d4c77f7efac24c
 43527b08d57324d7ed%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%
 7C0%7C6365415244
 57865491=4K39eoxbjwFxRmtuduLgUulDCCVtPnrkQHxQ1UIIO%
 2F4%3D=0
  *
> 
 
>> --
>> Jason Guild
>> Analyst/Programmer V
>> State of Alaska - Department of Transportation & Public Facilities
>> Information Systems and Services Division
>> 820 E. 15th Ave.
>> Anchorage, Alaska 99501
>> 
>> 
> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: [MAVEN-BUILD] Royale-typedefs - Build # 40 - Still Failing

[Gabe Harbs]

It passed! :-)

> On Feb 14, 2018, at 2:24 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com> wrote:
> 
> I just cleaned up workspace on Maven and run build with your changes. Let's
> see!
> 
> 2018-02-14 13:18 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
> 
>> I just committed a change where I set overwrite to true.
>> 
>> Hopefully that will do it…
>> 
>>> On Feb 14, 2018, at 2:13 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>>> 
>>> Is there some way to make sure that all the old resources are cleared
>> out of the maven build?
>>> 
>>> ITemplateArray is not a file which should be generated at all.
>>> 
>>> It looks like the replacement of es6.js is not working correctly.
>>> 
>>> Can you take a look at what I did to the pom and see if you can tweak it
>> so it works correctly?
>>> 
>>>> On Feb 14, 2018, at 1:10 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com>
>> wrote:
>>>> 
>>>> I'm wondering why are you not seeing that. If you scroll up in this
>> console
>>>> output - >https://builds.apache.org/job/Royale-typedefs/41/console
>>>> 
>>>> Can you see the errors ?
>>>> 
>>>> 2018-02-14 10:05 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
>>>> 
>>>>> Weird.
>>>>> 
>>>>> In my build, I get that function commented out:
>>>>> 
>>>>>  /**
>>>>>   * @param template [ITemplateArray]
>>>>>   * @param var_args [*] Substitution values.
>>>>>   * @see https://developer.mozilla.org/en-US/docs/Web/JavaScript/
>>>>> Reference/Global_Objects/String/raw
>>>>>   * @see [es6]
>>>>>   * @returns {string}
>>>>>   */
>>>>> //public static function raw(template:ITemplateArray,
>>>>> ...var_args):String { return ''; }
>>>>> 
>>>>> I’m not sure, but I’m guessing that is caused by this in
>>>>> externc-config.xml:
>>>>> 
>>>>>  
>>>>>  controlRange
>>>>>  ITemplateArray
>>>>>  
>>>>> 
>>>>>> On Feb 14, 2018, at 10:56 AM, Piotr Zarzycki <
>> piotrzarzyck...@gmail.com>
>>>>> wrote:
>>>>>> 
>>>>>> Do you see now this errors?
>>>>>> 
>>>>>> F:\jenkins\jenkins-slave\workspace\Royale-typedefs\js\
>>>>> target\generated-sources\externc\classes\String.as(52):
>>>>>> col: 41 Error: Type was not found or was not a compile-time constant:
>>>>>> ITemplateArray.
>>>>>> 
>>>>>> public static function raw(template:ITemplateArray,
>> ...var_args):String {
>>>>>> return ''; }
>>>>>> 
>>>>>> Piotr
>>>>>> 
>>>>>> On Wed, Feb 14, 2018, 09:53 Piotr Zarzycki <piotrzarzyck...@gmail.com
>>> 
>>>>>> wrote:
>>>>>> 
>>>>>>> Let me try again. It doesn't look like our fail.
>>>>>>> 
>>>>>>> On Wed, Feb 14, 2018, 09:52 Harbs <ha...@in-tools.com> wrote:
>>>>>>> 
>>>>>>>> I don’t understand the console output.
>>>>>>>> 
>>>>>>>> Suggestions?
>>>>>>>> 
>>>>>>>>> On Feb 14, 2018, at 10:50 AM, Apache Jenkins Server <
>>>>>>>> jenk...@builds.apache.org> wrote:
>>>>>>>>> 
>>>>>>>>> The Apache Jenkins build system has built Royale-typedefs (build
>> #40)
>>>>>>>>> 
>>>>>>>>> Status: Still Failing
>>>>>>>>> 
>>>>>>>>> Check console output at
>>>>>>>> https://builds.apache.org/job/Royale-typedefs/40/ to view the
>> results.
>>>>>>>> 
>>>>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> --
>>>> 
>>>> Piotr Zarzycki
>>>> 
>>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>>> <https://www.patreon.com/piotrzarzycki>*
>>> 
>> 
>> 
> 
> 
> -- 
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*

Re: [royale-typedefs] branch develop updated: try setting overwrite to true

[Gabe Harbs]

Phew!

Looks like this did it… :-)

> On Feb 14, 2018, at 2:18 PM, ha...@apache.org wrote:
> 
> This is an automated email from the ASF dual-hosted git repository.
> 
> harbs pushed a commit to branch develop
> in repository https://gitbox.apache.org/repos/asf/royale-typedefs.git
> 
> 
> The following commit(s) were added to refs/heads/develop by this push:
> new b2339de  try setting overwrite to true
> b2339de is described below
> 
> commit b2339de1be43a4ac7a53ffe1f01b1412a583
> Author: Harbs 
> AuthorDate: Wed Feb 14 14:17:58 2018 +0200
> 
>try setting overwrite to true
> ---
> js/pom.xml | 5 +
> 1 file changed, 5 insertions(+)
> 
> diff --git a/js/pom.xml b/js/pom.xml
> index 17f0f39..896ae7f 100644
> --- a/js/pom.xml
> +++ b/js/pom.xml
> @@ -93,6 +93,7 @@
>   es3.js
>   
> ${project.build.directory}/downloads
>   true
> +  true
> 
>   
>   
> @@ -106,6 +107,7 @@
>   es6.js
>   
> ${project.build.directory}/downloads
>   true
> +  true
> 
>   
>   
> @@ -119,6 +121,7 @@
>   w3c_css.js
>   
> ${project.build.directory}/downloads/browser
>   true
> +  true
> 
>   
>   
> @@ -132,6 +135,7 @@
>   gecko_dom.js
>   
> ${project.build.directory}/downloads/browser
>   true
> +  true
> 
>   
>   
> @@ -145,6 +149,7 @@
>   w3c_dom2.js
>   
> ${project.build.directory}/downloads/browser
>   true
> +  true
> 
>   
> 
> 
> -- 
> To stop receiving notification emails like this one, please contact
> ha...@apache.org.

Re: [MAVEN-BUILD] Royale-typedefs - Build # 40 - Still Failing

[Gabe Harbs]

Is there some way to make sure that all the old resources are cleared out of 
the maven build?

ITemplateArray is not a file which should be generated at all.

It looks like the replacement of es6.js is not working correctly.

Can you take a look at what I did to the pom and see if you can tweak it so it 
works correctly?

> On Feb 14, 2018, at 1:10 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com> wrote:
> 
> I'm wondering why are you not seeing that. If you scroll up in this console
> output - >https://builds.apache.org/job/Royale-typedefs/41/console
> 
> Can you see the errors ?
> 
> 2018-02-14 10:05 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
> 
>> Weird.
>> 
>> In my build, I get that function commented out:
>> 
>>/**
>> * @param template [ITemplateArray]
>> * @param var_args [*] Substitution values.
>> * @see https://developer.mozilla.org/en-US/docs/Web/JavaScript/
>> Reference/Global_Objects/String/raw
>> * @see [es6]
>> * @returns {string}
>> */
>> //public static function raw(template:ITemplateArray,
>> ...var_args):String { return ''; }
>> 
>> I’m not sure, but I’m guessing that is caused by this in
>> externc-config.xml:
>> 
>>
>>controlRange
>>ITemplateArray
>>
>> 
>>> On Feb 14, 2018, at 10:56 AM, Piotr Zarzycki <piotrzarzyck...@gmail.com>
>> wrote:
>>> 
>>> Do you see now this errors?
>>> 
>>> F:\jenkins\jenkins-slave\workspace\Royale-typedefs\js\
>> target\generated-sources\externc\classes\String.as(52):
>>> col: 41 Error: Type was not found or was not a compile-time constant:
>>> ITemplateArray.
>>> 
>>> public static function raw(template:ITemplateArray, ...var_args):String {
>>> return ''; }
>>> 
>>> Piotr
>>> 
>>> On Wed, Feb 14, 2018, 09:53 Piotr Zarzycki <piotrzarzyck...@gmail.com>
>>> wrote:
>>> 
>>>> Let me try again. It doesn't look like our fail.
>>>> 
>>>> On Wed, Feb 14, 2018, 09:52 Harbs <ha...@in-tools.com> wrote:
>>>> 
>>>>> I don’t understand the console output.
>>>>> 
>>>>> Suggestions?
>>>>> 
>>>>>> On Feb 14, 2018, at 10:50 AM, Apache Jenkins Server <
>>>>> jenk...@builds.apache.org> wrote:
>>>>>> 
>>>>>> The Apache Jenkins build system has built Royale-typedefs (build #40)
>>>>>> 
>>>>>> Status: Still Failing
>>>>>> 
>>>>>> Check console output at
>>>>> https://builds.apache.org/job/Royale-typedefs/40/ to view the results.
>>>>> 
>>>>> 
>> 
>> 
> 
> 
> -- 
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*

Re: [MAVEN-BUILD] Royale-typedefs - Build # 40 - Still Failing

[Gabe Harbs]

Weird.

In my build, I get that function commented out:

/**
 * @param template [ITemplateArray] 
 * @param var_args [*] Substitution values.
 * @see 
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/raw
 
 * @see [es6]
 * @returns {string} 
 */
//public static function raw(template:ITemplateArray, ...var_args):String { 
return ''; }

I’m not sure, but I’m guessing that is caused by this in externc-config.xml:


controlRange
ITemplateArray


> On Feb 14, 2018, at 10:56 AM, Piotr Zarzycki  
> wrote:
> 
> Do you see now this errors?
> 
> F:\jenkins\jenkins-slave\workspace\Royale-typedefs\js\target\generated-sources\externc\classes\String.as(52):
> col: 41 Error: Type was not found or was not a compile-time constant:
> ITemplateArray.
> 
> public static function raw(template:ITemplateArray, ...var_args):String {
> return ''; }
> 
> Piotr
> 
> On Wed, Feb 14, 2018, 09:53 Piotr Zarzycki 
> wrote:
> 
>> Let me try again. It doesn't look like our fail.
>> 
>> On Wed, Feb 14, 2018, 09:52 Harbs  wrote:
>> 
>>> I don’t understand the console output.
>>> 
>>> Suggestions?
>>> 
 On Feb 14, 2018, at 10:50 AM, Apache Jenkins Server <
>>> jenk...@builds.apache.org> wrote:
 
 The Apache Jenkins build system has built Royale-typedefs (build #40)
 
 Status: Still Failing
 
 Check console output at
>>> https://builds.apache.org/job/Royale-typedefs/40/ to view the results.
>>> 
>>> 

Re: [MAVEN-BUILD] Royale-typedefs - Build # 40 - Still Failing

[Gabe Harbs]

Nope. :-(

What does this mean?

[INFO] Skipping Apache Royale: TypeDefs: Parent
[INFO] This project has been banned from the build due to previous failures.

Please check the pom where I added multiple executions. I’m not sure if what I 
did was legal…

Harbs

> On Feb 14, 2018, at 10:53 AM, Piotr Zarzycki  
> wrote:
> 
> Let me try again. It doesn't look like our fail.
> 
> On Wed, Feb 14, 2018, 09:52 Harbs  wrote:
> 
>> I don’t understand the console output.
>> 
>> Suggestions?
>> 
>>> On Feb 14, 2018, at 10:50 AM, Apache Jenkins Server <
>> jenk...@builds.apache.org> wrote:
>>> 
>>> The Apache Jenkins build system has built Royale-typedefs (build #40)
>>> 
>>> Status: Still Failing
>>> 
>>> Check console output at
>> https://builds.apache.org/job/Royale-typedefs/40/ to view the results.
>> 
>> 

Re: [MAVEN-BUILD] Royale-typedefs - Build # 39 - Still Failing

[Gabe Harbs]

I didn’t realize that. Thanks.

> On Feb 14, 2018, at 10:48 AM, Piotr Zarzycki  
> wrote:
> 
> Harbs,
> 
> You can do this also, by logging with your apache credentials there.
> 
> Ok let me do this.
> 
> 
> On Wed, Feb 14, 2018, 09:46 Harbs  wrote:
> 
>> Piotr,
>> 
>> Could you manually run the maven build. I’d like to see if I fixed it…
>> 
>>> On Feb 14, 2018, at 10:39 AM, Apache Jenkins Server <
>> jenk...@builds.apache.org> wrote:
>>> 
>>> The Apache Jenkins build system has built Royale-typedefs (build #39)
>>> 
>>> Status: Still Failing
>>> 
>>> Check console output at
>> https://builds.apache.org/job/Royale-typedefs/39/ to view the results.
>> 
>> 

Re: Royale Examples Blog proposal to all the team

[Gabe Harbs]

Looks great!

> On Feb 13, 2018, at 11:45 PM, Carlos Rovira  wrote:
> 
> Hi all,
> 
> just let you know that I updated the Hello World with :
> 
> * working example (loaded below in Iframe)
> * added more explanations
> * Updated styled in code to look better.
> 
> I think we have the final base for the rest of blog examples
> 
> https://royale.apache.org/creating-a-hello-world-in-apache-royale/
> 
> 
> hope you liked the final result :)
> 
> 
> 
> 2018-02-13 22:42 GMT+01:00 Carlos Rovira :
> 
>> Hi Alex,
>> 
>> I can make another blog post with Express, based on the first one. I look
>> at it tomorrow :)
>> 
>> 
>> 2018-02-13 18:36 GMT+01:00 Alex Harui :
>> 
>>> I just looked at the Hello World example.  IMO, these examples should use
>>> Express, not Basic, and then the code would be even shorter.
>>> 
>>> My 2 cents,
>>> -Alex
>>> 
>>> On 2/13/18, 9:21 AM, "Alex Harui"  wrote:
>>> 
 Having an Examples blog is a great thing.
 
 I saw the calendar invite.  I couldn't see the calendar I think because
 default to logging in under a different email and don't really want this
 stuff mixed into to my default calendar.
 
 My only concern is the scheduling.  IMO, scheduling is difficult with
 volunteers.  Folks get busy with their $dayjob and may run out of time.
 We should accept entries from anyone, even non-committers, at any time.
 So what if we get a burst here and it goes quiet for a while?  Carlos, if
 you want to volunteer to keep track of the last post date, then if a week
 goes by without a new post you could ask on the mailing list for a
 volunteer to write the next post.  And anyone reading this email is
 welcome to write a post or suggest a topic.  That will likely be the
 biggest question for me: what should I write about?
 
 Anyway, thanks for getting this started.
 
 My 2 cents,
 -Alex
 
 On 2/13/18, 3:09 AM, "carlos.rov...@gmail.com on behalf of Carlos
>>> Rovira"
  wrote:
 
> Hi Olaf
> 
> 2018-02-13 11:31 GMT+01:00 Olaf Krueger :
> 
>>> I'd like to read thoughts from others in the team.
>> 
>> This is a really good idea, Carlos!
>> If I understand you right you'd like to say that we want to publish a
>> post
>> every two weeks and because we're about 10 to 15 people who will
>> contribute
>> this means that anybody of us has to write an article approx every 6
>> months?!
>> And you want us to manage the scheduling of the blog posts by using
>>> the
>> google calendar?
>> 
> 
> That's right! I think if we all participate will 10-11, and about 6
> months
> between repeat author.
> Maybe, as examples are very easy to do we can talk more later if we do
> this
> each week...we'll see as we develop it right?
> 
> 
>> 
>>> Below the source code, we should have the result displayed in an
>> iframe.
>> +1
>> 
>> Another suggestion:
>> Peter de Haan posts always contain some simple explanations.
>> Regarding the "Hello world" post, I think it would be interesting for
>> people
>> to learn something about the code, e.g. for what is
>> "js:SimpleCSSValuesImpl", "js:initialView" and "js:View" needed.
>> Maybe it makes sense to link something to the docs or to add some
>> simple
>> explanation?
>> 
> 
> That's a very good idea. I'll try to update the hello world with this
> suggestions :)
> 
> 
>> 
>> I'll check out the google calendar...
>> 
>> Thanks,
>> Olaf
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> --
>> Sent from:
>> https://na01.safelinks.protection.outlook.com/?url=http%
>>> 3A%2F%2Fapache-r
>> o
>> yale-development.20373.n8.nabble.com%2F=02%7C01%7Caharui%
>>> 40adobe.co
>> m
>> %7Cd2453e80427a4a2db4a708d572d259e3%7Cfa7b1b5a7b34438794a
>>> ed2c178decee1%7
>> C
>> 0%7C0%7C636541170132357067=IW1I%2BZebS7gSyrBako0WCH
>>> BAG8eo1b3NPVnfC
>> %
>> 2BvUyTA%3D=0
>> 
> 
> 
> 
> --
> Carlos Rovira
> https://na01.safelinks.protection.outlook.com/?url=http%
>>> 3A%2F%2Fabout.me%
> 2
> Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7Cd2453e80
>>> 427a4a2db4a708d
> 5
> 72d259e3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365
>>> 41170132357067&
> s
> data=YBsn0zhxZd98toKr%2BrZP1GwprmRzcmM5NesejiabbJo%3D=0
 
>>> 
>>> 
>> 
>> 
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>> 
>> 
> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Gabe Harbs]

Question for (I think) Alex:

How does this target work?






What sets the ROYALE_DOWNLOAD_CACHE and what saves the files there?

> On Feb 13, 2018, at 11:41 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
> 
> I’m not sure I’m going to get to this tonight. If not, I’ll try to fix the 
> builds first thing in the morning.
> 
> I’m going to put back the unzipping of the externs and I’m replacing the 
> specific ones which need editing. I should be able to fix both the ant and 
> maven builds.
> 
> Harbs
> 
>> On Feb 13, 2018, at 10:49 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com> 
>> wrote:
>> 
>> Where is the conclusion, cause I lost a bit track with that. What are you
>> going to do next Harbs ? Should I still spent some time on Maven ?
>> 
>> 2018-02-13 19:45 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
>> 
>>> Ultimately, using those files is probably the way to go, but I’ll go back
>>> to overwriting individual files for now…
>>> 
>>> I’ll work on this a bit later.
>>> 
>>> Harbs
>>> 
>>>> On Feb 13, 2018, at 8:04 PM, Alex Harui <aha...@adobe.com.INVALID>
>>> wrote:
>>>> 
>>>> I think we are working against an older closure-compiler.  Volunteers are
>>>> welcome to move us to the latest.
>>>> 
>>>> I think we only patch a dozen files or so, so yes, even if you coned the
>>>> originals to royale-extras, I thought you would just cherry pick the few
>>>> files we need.  IMO, you can do that and get both Maven and Ant working
>>>> with less hassle.
>>>> 
>>>> My 2 cents,
>>>> -Alex
>>>> 
>>>> On 2/13/18, 9:45 AM, "Gabe Harbs" <harbs.li...@gmail.com> wrote:
>>>> 
>>>>> BTW, when I switched to the newer extern files that turned upon some
>>> more
>>>>> bugs with them.
>>>>> 
>>>>> I’m not ure at what point the newer externs are/will be included in the
>>>>> closure-compiler download, but more files will become an issue at
>>>>> whatever point they do.
>>>>> 
>>>>>> On Feb 13, 2018, at 7:40 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>>>>>> 
>>>>>> You mean just download the specific files we need?
>>>>>> 
>>>>>> I figured we might as well just get all the files from the same repo.
>>>>>> 
>>>>>>> On Feb 13, 2018, at 7:28 PM, Alex Harui <aha...@adobe.com.INVALID
>>>>>>> <mailto:aha...@adobe.com.INVALID>> wrote:
>>>>>>> 
>>>>>>> I don't understand what is wrong with the way it worked.  Isn't the
>>>>>>> idea
>>>>>>> that you are overlaying files from royale-extras?  Why can't the
>>>>>>> current
>>>>>>> build expand the externs from closure-compiler and then your stuff can
>>>>>>> overlay it?
>>>>>>> 
>>>>>>> Thoughts?
>>>>>> -Alex
>>>>>>> 
>>>>>>> On 2/13/18, 5:26 AM, "Gabe Harbs" <harbs.li...@gmail.com
>>>>>>> <mailto:harbs.li...@gmail.com>> wrote:
>>>>>>> 
>>>>>>>> Maybe. I didn’t realize changing the typedefs was going to end up
>>>>>>>> being
>>>>>>>> so complicated.
>>>>>>>> 
>>>>>>>> I just changed the ant build to use git instead of svn. It takes
>>>>>>>> about a
>>>>>>>> minute the first time the repo is needed to be ownloaded, but it’s
>>>>>>>> pretty quick afterwards.
>>>>>>>> 
>>>>>>>> I’m not sure which method is best for Maven.
>>>>>>>> 
>>>>>>>>> On Feb 13, 2018, at 2:17 PM, Piotr Zarzycki
>>>>>>>>> <piotrzarzyck...@gmail.com <mailto:piotrzarzyck...@gmail.com>>
>>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>> Btw. Maybe you should move your changes to separate branch. We will
>>>>>>>>> have
>>>>>>>>> emails with fails for a long time now. Unless someone else look into
>>>>>>>>> the
>>>>>>>>> Maven.
>>>>>>>

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Gabe Harbs]

I’m not sure I’m going to get to this tonight. If not, I’ll try to fix the 
builds first thing in the morning.

I’m going to put back the unzipping of the externs and I’m replacing the 
specific ones which need editing. I should be able to fix both the ant and 
maven builds.

Harbs

> On Feb 13, 2018, at 10:49 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com> 
> wrote:
> 
> Where is the conclusion, cause I lost a bit track with that. What are you
> going to do next Harbs ? Should I still spent some time on Maven ?
> 
> 2018-02-13 19:45 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
> 
>> Ultimately, using those files is probably the way to go, but I’ll go back
>> to overwriting individual files for now…
>> 
>> I’ll work on this a bit later.
>> 
>> Harbs
>> 
>>> On Feb 13, 2018, at 8:04 PM, Alex Harui <aha...@adobe.com.INVALID>
>> wrote:
>>> 
>>> I think we are working against an older closure-compiler.  Volunteers are
>>> welcome to move us to the latest.
>>> 
>>> I think we only patch a dozen files or so, so yes, even if you coned the
>>> originals to royale-extras, I thought you would just cherry pick the few
>>> files we need.  IMO, you can do that and get both Maven and Ant working
>>> with less hassle.
>>> 
>>> My 2 cents,
>>> -Alex
>>> 
>>> On 2/13/18, 9:45 AM, "Gabe Harbs" <harbs.li...@gmail.com> wrote:
>>> 
>>>> BTW, when I switched to the newer extern files that turned upon some
>> more
>>>> bugs with them.
>>>> 
>>>> I’m not ure at what point the newer externs are/will be included in the
>>>> closure-compiler download, but more files will become an issue at
>>>> whatever point they do.
>>>> 
>>>>> On Feb 13, 2018, at 7:40 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>>>>> 
>>>>> You mean just download the specific files we need?
>>>>> 
>>>>> I figured we might as well just get all the files from the same repo.
>>>>> 
>>>>>> On Feb 13, 2018, at 7:28 PM, Alex Harui <aha...@adobe.com.INVALID
>>>>>> <mailto:aha...@adobe.com.INVALID>> wrote:
>>>>>> 
>>>>>> I don't understand what is wrong with the way it worked.  Isn't the
>>>>>> idea
>>>>>> that you are overlaying files from royale-extras?  Why can't the
>>>>>> current
>>>>>> build expand the externs from closure-compiler and then your stuff can
>>>>>> overlay it?
>>>>>> 
>>>>>> Thoughts?
>>>>> -Alex
>>>>>> 
>>>>>> On 2/13/18, 5:26 AM, "Gabe Harbs" <harbs.li...@gmail.com
>>>>>> <mailto:harbs.li...@gmail.com>> wrote:
>>>>>> 
>>>>>>> Maybe. I didn’t realize changing the typedefs was going to end up
>>>>>>> being
>>>>>>> so complicated.
>>>>>>> 
>>>>>>> I just changed the ant build to use git instead of svn. It takes
>>>>>>> about a
>>>>>>> minute the first time the repo is needed to be ownloaded, but it’s
>>>>>>> pretty quick afterwards.
>>>>>>> 
>>>>>>> I’m not sure which method is best for Maven.
>>>>>>> 
>>>>>>>> On Feb 13, 2018, at 2:17 PM, Piotr Zarzycki
>>>>>>>> <piotrzarzyck...@gmail.com <mailto:piotrzarzyck...@gmail.com>>
>>>>>>>> wrote:
>>>>>>>> 
>>>>>>>> Btw. Maybe you should move your changes to separate branch. We will
>>>>>>>> have
>>>>>>>> emails with fails for a long time now. Unless someone else look into
>>>>>>>> the
>>>>>>>> Maven.
>>>>>>>> 
>>>>>>>> 2018-02-13 13:03 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com
>>>>>>>> <mailto:harbs.li...@gmail.com>
>>>>>>>> <mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>>:
>>>>>>>> 
>>>>>>>>> FWIW, here’s some other options for downloading a specific folder
>>>>>>>>> from
>>>>>>>>> Github:
>>>>>>>>> 
>>>>>>>>> 
>>>>>&

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Gabe Harbs]

Ultimately, using those files is probably the way to go, but I’ll go back to 
overwriting individual files for now…

I’ll work on this a bit later.

Harbs

> On Feb 13, 2018, at 8:04 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
> 
> I think we are working against an older closure-compiler.  Volunteers are
> welcome to move us to the latest.
> 
> I think we only patch a dozen files or so, so yes, even if you coned the
> originals to royale-extras, I thought you would just cherry pick the few
> files we need.  IMO, you can do that and get both Maven and Ant working
> with less hassle.
> 
> My 2 cents,
> -Alex
> 
> On 2/13/18, 9:45 AM, "Gabe Harbs" <harbs.li...@gmail.com> wrote:
> 
>> BTW, when I switched to the newer extern files that turned upon some more
>> bugs with them.
>> 
>> I’m not ure at what point the newer externs are/will be included in the
>> closure-compiler download, but more files will become an issue at
>> whatever point they do.
>> 
>>> On Feb 13, 2018, at 7:40 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>>> 
>>> You mean just download the specific files we need?
>>> 
>>> I figured we might as well just get all the files from the same repo.
>>> 
>>>> On Feb 13, 2018, at 7:28 PM, Alex Harui <aha...@adobe.com.INVALID
>>>> <mailto:aha...@adobe.com.INVALID>> wrote:
>>>> 
>>>> I don't understand what is wrong with the way it worked.  Isn't the
>>>> idea
>>>> that you are overlaying files from royale-extras?  Why can't the
>>>> current
>>>> build expand the externs from closure-compiler and then your stuff can
>>>> overlay it?
>>>> 
>>>> Thoughts?
>>> -Alex
>>>> 
>>>> On 2/13/18, 5:26 AM, "Gabe Harbs" <harbs.li...@gmail.com
>>>> <mailto:harbs.li...@gmail.com>> wrote:
>>>> 
>>>>> Maybe. I didn’t realize changing the typedefs was going to end up
>>>>> being
>>>>> so complicated.
>>>>> 
>>>>> I just changed the ant build to use git instead of svn. It takes
>>>>> about a
>>>>> minute the first time the repo is needed to be ownloaded, but it’s
>>>>> pretty quick afterwards.
>>>>> 
>>>>> I’m not sure which method is best for Maven.
>>>>> 
>>>>>> On Feb 13, 2018, at 2:17 PM, Piotr Zarzycki
>>>>>> <piotrzarzyck...@gmail.com <mailto:piotrzarzyck...@gmail.com>>
>>>>>> wrote:
>>>>>> 
>>>>>> Btw. Maybe you should move your changes to separate branch. We will
>>>>>> have
>>>>>> emails with fails for a long time now. Unless someone else look into
>>>>>> the
>>>>>> Maven.
>>>>>> 
>>>>>> 2018-02-13 13:03 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com
>>>>>> <mailto:harbs.li...@gmail.com>
>>>>>> <mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>>:
>>>>>> 
>>>>>>> FWIW, here’s some other options for downloading a specific folder
>>>>>>> from
>>>>>>> Github:
>>>>>>> 
>>>>>>> 
>>>>>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstac
>>>>>>> kov 
>>>>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsta
>>>>>>> ckov>
>>>>>>> erflow.com 
>>>>>>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ferfl
>>>>>>> ow.com%2F=02%7C01%7Caharui%40adobe.com%7Cd1228ae32eca45e43ce208d
>>>>>>> 57309af91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63654140779893
>>>>>>> 6061=zxNWE%2BwbCzZDK1diTruXDmroGk%2BxVzdwIVm%2Bxxg4LAc%3D
>>>>>>> ved=0>%2Fa%2F18194523=02%7C01%7Caharui%40adobe.com
>>>>>>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2F40ad
>>>>>>> obe.com%2F=02%7C01%7Caharui%40adobe.com%7Cd1228ae32eca45e43ce208
>>>>>>> d57309af91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365414077989
>>>>>>> 36061=rZuwf0WjH2xZAOacIz7ECWcohPvCLUIJg471M7Yhs%2Fc%3D
>>>>>>> =0>%7C2fc7071c44
>>>>>>> 
>>>>>>> 6245d8331208d572e567a2%7Cfa7b1b5a7b34438794aed2c178

Re: How I can use multiple CSS files

[Gabe Harbs]

Why not just use MXML files?

You can use MXML files to subclass components and specify the CSS in the 
 section.

> On Feb 13, 2018, at 1:20 PM, Carlos Rovira  wrote:
> 
> Hi,
> 
> I'm organizing CSS files in Vivid (new ui set) - VividBlueTheme (first
> theme) - VividExample (example to show all working)
> 
> I want to develop each component look-and-feel and style in a single file
> in the theme project:
> 
> default.css (this could hold global styling like body, headers, background
> color, and more)
> TextField.css (all css to make a TextField be represented in a particular
> way)
> Button.css
> Slider.css
> ...
> 
> in my theme pom I have:
> 
> 
> 
> defaults.css
> ../src/main/resources/defaults.css
> 
> 
> TextField.css
> ../src/main/resources/TextField.css
> 
> 
> 
> and I check the resulting VividBlueTheme.swc and has default.css and
> TextField.css
> 
> * First question here is: Can I collapse all css content in multiple files
> in a single .css (i.e: defaults.css or themename.css)?
> 
> Then in vivid example how CSS in theme projects are referenced? I see
> "defaults.css" is begin applied, but "TextField.css" is not
> 
> * Second question how to apply a included .css file to be used in example
> 
> Notice that if we get all css in one single file we don't need the second
> part.
> 
> Hope you could help me on this in order to continue progress with this
> effort
> 
> thanks
> 
> 
> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Gabe Harbs]

BTW, when I switched to the newer extern files that turned upon some more bugs 
with them.

I’m not sure at what point the newer externs are/will be included in the 
closure-compiler download, but more files will become an issue at whatever 
point they do.

> On Feb 13, 2018, at 7:40 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
> 
> You mean just download the specific files we need?
> 
> I figured we might as well just get all the files from the same repo.
> 
>> On Feb 13, 2018, at 7:28 PM, Alex Harui <aha...@adobe.com.INVALID 
>> <mailto:aha...@adobe.com.INVALID>> wrote:
>> 
>> I don't understand what is wrong with the way it worked.  Isn't the idea
>> that you are overlaying files from royale-extras?  Why can't the current
>> build expand the externs from closure-compiler and then your stuff can
>> overlay it?
>> 
>> Thoughts?
>> -Alex
>> 
>> On 2/13/18, 5:26 AM, "Gabe Harbs" <harbs.li...@gmail.com 
>> <mailto:harbs.li...@gmail.com>> wrote:
>> 
>>> Maybe. I didn’t realize changing the typedefs was going to end up being
>>> so complicated.
>>> 
>>> I just changed the ant build to use git instead of svn. It takes about a
>>> minute the first time the repo is needed to be downloaded, but it’s
>>> pretty quick afterwards.
>>> 
>>> I’m not sure which method is best for Maven.
>>> 
>>>> On Feb 13, 2018, at 2:17 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com 
>>>> <mailto:piotrzarzyck...@gmail.com>>
>>>> wrote:
>>>> 
>>>> Btw. Maybe you should move your changes to separate branch. We will have
>>>> emails with fails for a long time now. Unless someone else look into the
>>>> Maven.
>>>> 
>>>> 2018-02-13 13:03 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com 
>>>> <mailto:harbs.li...@gmail.com>
>>>> <mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>>:
>>>> 
>>>>> FWIW, here’s some other options for downloading a specific folder from
>>>>> Github:
>>>>> 
>>>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackov 
>>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackov>
>>>>> erflow.com 
>>>>> <http://erflow.com/>%2Fa%2F18194523=02%7C01%7Caharui%40adobe.com 
>>>>> <http://40adobe.com/>%7C2fc7071c44
>>>>> 6245d8331208d572e567a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365
>>>>> 41251966892882=hv35Ja58vctUc%2BCbeuID%2FiH9hRZ1gDnv0gumtvfrQ2Y%3D&
>>>>> reserved=0
>>>>> 
>>>>>> On Feb 13, 2018, at 1:57 PM, Gabe Harbs <harbs.li...@gmail.com 
>>>>>> <mailto:harbs.li...@gmail.com>> wrote:
>>>>>> 
>>>>>> If you use Git, you need to download the entire repo which includes
>>>>>> all
>>>>> the bits for the actual compiler.
>>>>>> 
>>>>>> Github supports svn checkouts as well which allows you to checkout a
>>>>> specific folder within a repo.[1]
>>>>>> 
>>>>>> The following command will get the extern files we need from Github:
>>>>>> 
>>>>>> svn checkout 
>>>>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub 
>>>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub>
>>>>>> .com%2Froyale-extras%2Fclosure-compiler%2F=02%7C01%7Caharui%40adob
>>>>>> e.com 
>>>>>> <http://e.com/>%7C2fc7071c446245d8331208d572e567a2%7Cfa7b1b5a7b34438794aed2c178de
>>>>>> cee1%7C0%7C0%7C636541251966892882=a6YLnJTMAiiWgneJukkWb4ErTKLQ4MR
>>>>>> cFMpdNE%2Bhoz8%3D=0
>>>>> branches/royale/externs
>>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub 
>>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub>
>>>>> .com%2Froyale-=02%7C01%7Caharui%40adobe.com 
>>>>> <http://40adobe.com/>%7C2fc7071c446245d833120
>>>>> 8d572e567a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636541251966892
>>>>> 882=ywlYp7LPHuU2TSAxQxldMfkPbAJsoFVVqkpzlySK%2Fmc%3D=0
>>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub 
>>>>> <https://na01.safelinks.protection.outlook.com/

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Gabe Harbs]

You mean just download the specific files we need?

I figured we might as well just get all the files from the same repo.

> On Feb 13, 2018, at 7:28 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
> 
> I don't understand what is wrong with the way it worked.  Isn't the idea
> that you are overlaying files from royale-extras?  Why can't the current
> build expand the externs from closure-compiler and then your stuff can
> overlay it?
> 
> Thoughts?
> -Alex
> 
> On 2/13/18, 5:26 AM, "Gabe Harbs" <harbs.li...@gmail.com 
> <mailto:harbs.li...@gmail.com>> wrote:
> 
>> Maybe. I didn’t realize changing the typedefs was going to end up being
>> so complicated.
>> 
>> I just changed the ant build to use git instead of svn. It takes about a
>> minute the first time the repo is needed to be downloaded, but it’s
>> pretty quick afterwards.
>> 
>> I’m not sure which method is best for Maven.
>> 
>>> On Feb 13, 2018, at 2:17 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com>
>>> wrote:
>>> 
>>> Btw. Maybe you should move your changes to separate branch. We will have
>>> emails with fails for a long time now. Unless someone else look into the
>>> Maven.
>>> 
>>> 2018-02-13 13:03 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com
>>> <mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>>:
>>> 
>>>> FWIW, here’s some other options for downloading a specific folder from
>>>> Github:
>>>> 
>>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackov 
>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackov>
>>>> erflow.com 
>>>> <http://erflow.com/>%2Fa%2F18194523=02%7C01%7Caharui%40adobe.com 
>>>> <http://40adobe.com/>%7C2fc7071c44
>>>> 6245d8331208d572e567a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365
>>>> 41251966892882=hv35Ja58vctUc%2BCbeuID%2FiH9hRZ1gDnv0gumtvfrQ2Y%3D&
>>>> reserved=0
>>>> 
>>>>> On Feb 13, 2018, at 1:57 PM, Gabe Harbs <harbs.li...@gmail.com 
>>>>> <mailto:harbs.li...@gmail.com>> wrote:
>>>>> 
>>>>> If you use Git, you need to download the entire repo which includes
>>>>> all
>>>> the bits for the actual compiler.
>>>>> 
>>>>> Github supports svn checkouts as well which allows you to checkout a
>>>> specific folder within a repo.[1]
>>>>> 
>>>>> The following command will get the extern files we need from Github:
>>>>> 
>>>>> svn checkout 
>>>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub 
>>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub>
>>>>> .com%2Froyale-extras%2Fclosure-compiler%2F=02%7C01%7Caharui%40adob
>>>>> e.com 
>>>>> <http://e.com/>%7C2fc7071c446245d8331208d572e567a2%7Cfa7b1b5a7b34438794aed2c178de
>>>>> cee1%7C0%7C0%7C636541251966892882=a6YLnJTMAiiWgneJukkWb4ErTKLQ4MR
>>>>> cFMpdNE%2Bhoz8%3D=0
>>>> branches/royale/externs
>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub 
>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub>
>>>> .com%2Froyale-=02%7C01%7Caharui%40adobe.com 
>>>> <http://40adobe.com/>%7C2fc7071c446245d833120
>>>> 8d572e567a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636541251966892
>>>> 882=ywlYp7LPHuU2TSAxQxldMfkPbAJsoFVVqkpzlySK%2Fmc%3D=0
>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub 
>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub>
>>>> .com%2Froyale-=02%7C01%7Caharui%40adobe.com 
>>>> <http://40adobe.com/>%7C2fc7071c446245d833120
>>>> 8d572e567a2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636541251966892
>>>> 882=ywlYp7LPHuU2TSAxQxldMfkPbAJsoFVVqkpzlySK%2Fmc%3D=0>
>>>> extras/closure-compiler/branches/royale/externs>
>>>>> 
>>>>> Harbs
>>>>> 
>>>>> 
>>>>> [1]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhel 
>>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhel>
>>>>> p.github.com 
>>>>> <http://p.github.com/>%2Farticles%2Fsupport-for-subversion-clients%2F=02%7C0
>>>

Re: Build failed in Jenkins: royale-asjs_jsonly #295

[Gabe Harbs]

I don’t understand this failure.

This seems to indicate that the directory is there and up to date:
 [exec] Your branch is up to date with 'origin/royale'.
 [exec] Already on 'royale'
 [exec] Already up to date.

> On Feb 13, 2018, at 4:11 PM, apacheroyal...@gmail.com wrote:
> 
> See 
> 
> 
> --
> [...truncated 654.68 KB...]
> [exec] D  test/com/google/javascript/jscomp/regex/CharRangesTest.java
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/array_pattern_test.js
> [exec] D  test/com/google/javascript/jscomp/runtime_tests/arrow_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/async_function_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_block_scope_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_computed_getter_setter_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_exported_getter_setter_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_getter_setter_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_in_goog_module_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_no_constructor_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_spread_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_static_getter_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_static_setter_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/class_super_return_test.js
> [exec] D  test/com/google/javascript/jscomp/runtime_tests/class_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/collections_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/computed_properties_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/default_param_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/es3_style_class.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/extend_es3_test.js
> [exec] D  test/com/google/javascript/jscomp/runtime_tests/for_of_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/generator_allow_call_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/generator_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/identifier_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/inherit_sets_superClass_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/inheritance_with_overriden_function_prototype_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/let_const_loop_typecheck_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/let_const_rename_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/mixed_destructuring_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/mocking_class_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/class_inherits_protected.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/dot_dot_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/export_from_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/export_spec_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/import_class_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/import_default_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/import_mixed_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/import_namespace_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/import_star_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/import_with_js_extension_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/module_order_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/module_runtime_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/classProtectedMethod.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/decl_leg_name_a.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/decl_leg_name_test.js
> [exec] D  
> test/com/google/javascript/jscomp/runtime_tests/module_tests/module_test_resources/exportClass.js
> [exec] D  
> 

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Gabe Harbs]

Maybe. I didn’t realize changing the typedefs was going to end up being so 
complicated.

I just changed the ant build to use git instead of svn. It takes about a minute 
the first time the repo is needed to be downloaded, but it’s pretty quick 
afterwards.

I’m not sure which method is best for Maven.

> On Feb 13, 2018, at 2:17 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com> wrote:
> 
> Btw. Maybe you should move your changes to separate branch. We will have
> emails with fails for a long time now. Unless someone else look into the
> Maven.
> 
> 2018-02-13 13:03 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com 
> <mailto:harbs.li...@gmail.com>>:
> 
>> FWIW, here’s some other options for downloading a specific folder from
>> Github:
>> https://stackoverflow.com/a/18194523
>> 
>>> On Feb 13, 2018, at 1:57 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>>> 
>>> If you use Git, you need to download the entire repo which includes all
>> the bits for the actual compiler.
>>> 
>>> Github supports svn checkouts as well which allows you to checkout a
>> specific folder within a repo.[1]
>>> 
>>> The following command will get the extern files we need from Github:
>>> 
>>> svn checkout https://github.com/royale-extras/closure-compiler/
>> branches/royale/externs <https://github.com/royale- 
>> <https://github.com/royale->
>> extras/closure-compiler/branches/royale/externs>
>>> 
>>> Harbs
>>> 
>>> [1]https://help.github.com/articles/support-for-subversion-clients/ 
>>> <https://help.github.com/articles/support-for-subversion-clients/> <
>> https://help.github.com/articles/support-for-subversion-clients/ 
>> <https://help.github.com/articles/support-for-subversion-clients/>>
>>> 
>>>> On Feb 13, 2018, at 1:54 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com 
>>>> <mailto:piotrzarzyck...@gmail.com>
>> <mailto:piotrzarzyck...@gmail.com <mailto:piotrzarzyck...@gmail.com>>> wrote:
>>>> 
>>>> Actually why are you talking about svn ? You mean GIT actually ?
>>>> 
>>>> 2018-02-13 12:47 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com 
>>>> <mailto:harbs.li...@gmail.com> > harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>>:
>>>> 
>>>>> BTW, there’s a mojo for svn checkout:
>>>>> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html 
>>>>> <https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html> <
>> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html 
>> <https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html>> <
>>>>> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html 
>>>>> <https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html> <
>> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html 
>> <https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html>>>
>>>>> 
>>>>> Maybe you can use that.
>>>>> 
>>>>> Harbs
>>>>> 
>>>>>> On Feb 13, 2018, at 1:41 PM, Gabe Harbs <harbs.li...@gmail.com 
>>>>>> <mailto:harbs.li...@gmail.com>
>> <mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>> wrote:
>>>>>> 
>>>>>> We need to download all the files from here:
>> https://github.com/royale- <https://github.com/royale-> 
>> <https://github.com/royale- <https://github.com/royale->>
>>>>> extras/closure-compiler/tree/royale/externs/ <
>> https://github.com/royale- <https://github.com/royale-> 
>> <https://github.com/royale- <https://github.com/royale->>
>>>>> extras/closure-compiler/tree/royale/externs/> to js/target/downloads.
>>>>>> 
>>>>>> Svn seems like the easiest way to do that, but you can use any method
>>>>> that works.
>>>>>> 
>>>>>> Harbs
>>>>>> 
>>>>>>> On Feb 13, 2018, at 1:39 PM, Piotr Zarzycki <
>> piotrzarzyck...@gmail.com <mailto:piotrzarzyck...@gmail.com> 
>> <mailto:piotrzarzyck...@gmail.com <mailto:piotrzarzyck...@gmail.com>>
>>>>> <mailto:piotrzarzyck...@gmail.com <mailto:piotrzarzyck...@gmail.com> 
>>>>> <mailto:piotrzarzyck...@gmail.com <mailto:piotrzarzyck...@gmail.com>>>>
>> wrote:
>

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Gabe Harbs]

FWIW, here’s some other options for downloading a specific folder from Github:
https://stackoverflow.com/a/18194523

> On Feb 13, 2018, at 1:57 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
> 
> If you use Git, you need to download the entire repo which includes all the 
> bits for the actual compiler.
> 
> Github supports svn checkouts as well which allows you to checkout a specific 
> folder within a repo.[1]
> 
> The following command will get the extern files we need from Github:
> 
> svn checkout 
> https://github.com/royale-extras/closure-compiler/branches/royale/externs 
> <https://github.com/royale-extras/closure-compiler/branches/royale/externs>
> 
> Harbs
> 
> [1]https://help.github.com/articles/support-for-subversion-clients/ 
> <https://help.github.com/articles/support-for-subversion-clients/>
> 
>> On Feb 13, 2018, at 1:54 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com 
>> <mailto:piotrzarzyck...@gmail.com>> wrote:
>> 
>> Actually why are you talking about svn ? You mean GIT actually ?
>> 
>> 2018-02-13 12:47 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com 
>> <mailto:harbs.li...@gmail.com>>:
>> 
>>> BTW, there’s a mojo for svn checkout:
>>> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html 
>>> <https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html> <
>>> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html 
>>> <https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html>>
>>> 
>>> Maybe you can use that.
>>> 
>>> Harbs
>>> 
>>>> On Feb 13, 2018, at 1:41 PM, Gabe Harbs <harbs.li...@gmail.com 
>>>> <mailto:harbs.li...@gmail.com>> wrote:
>>>> 
>>>> We need to download all the files from here: https://github.com/royale- 
>>>> <https://github.com/royale->
>>> extras/closure-compiler/tree/royale/externs/ <https://github.com/royale- 
>>> <https://github.com/royale->
>>> extras/closure-compiler/tree/royale/externs/> to js/target/downloads.
>>>> 
>>>> Svn seems like the easiest way to do that, but you can use any method
>>> that works.
>>>> 
>>>> Harbs
>>>> 
>>>>> On Feb 13, 2018, at 1:39 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com 
>>>>> <mailto:piotrzarzyck...@gmail.com>
>>> <mailto:piotrzarzyck...@gmail.com <mailto:piotrzarzyck...@gmail.com>>> 
>>> wrote:
>>>>> 
>>>>> Can we avoid using svn ? Or it was used before ? I'm not familiar with
>>> that
>>>>> logic.
>>>>> 
>>>>> 2018-02-13 12:37 GMT+01:00 Harbs <ha...@in-tools.com 
>>>>> <mailto:ha...@in-tools.com> >> ha...@in-tools.com <mailto:ha...@in-tools.com>>>:
>>>>> 
>>>>>> We need to add svn checkout of the externs like I did in the ant
>>> script.
>>>>>> 
>>>>>>> On Feb 13, 2018, at 1:36 PM, Apache Jenkins Server <
>>>>>> jenk...@builds.apache.org <mailto:jenk...@builds.apache.org> 
>>>>>> <mailto:jenk...@builds.apache.org <mailto:jenk...@builds.apache.org>>> 
>>>>>> wrote:
>>>>>>> 
>>>>>>> The Apache Jenkins build system has built Royale-typedefs (build #34)
>>>>>>> 
>>>>>>> Status: Failure
>>>>>>> 
>>>>>>> Check console output at https://builds.apache.org/job/ 
>>>>>>> <https://builds.apache.org/job/> <
>>> https://builds.apache.org/job/ <https://builds.apache.org/job/>>
>>>>>> Royale-typedefs/34/ to view the results.
>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> 
>>>>> Piotr Zarzycki
>>>>> 
>>>>> Patreon: *https://www.patreon.com/piotrzarzycki 
>>>>> <https://www.patreon.com/piotrzarzycki> <
>>> https://www.patreon.com/piotrzarzycki 
>>> <https://www.patreon.com/piotrzarzycki>>
>>>>> <https://www.patreon.com/piotrzarzycki 
>>>>> <https://www.patreon.com/piotrzarzycki> <https://www.patreon.com/ 
>>>>> <https://www.patreon.com/>
>>> piotrzarzycki>>*
>>>> 
>>> 
>>> 
>> 
>> 
>> -- 
>> 
>> Piotr Zarzycki
>> 
>> Patreon: *https://www.patreon.com/piotrzarzycki 
>> <https://www.patreon.com/piotrzarzycki>
>> <https://www.patreon.com/piotrzarzycki 
>> <https://www.patreon.com/piotrzarzycki>>*
> 

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Gabe Harbs]

If you use Git, you need to download the entire repo which includes all the 
bits for the actual compiler.

Github supports svn checkouts as well which allows you to checkout a specific 
folder within a repo.[1]

The following command will get the extern files we need from Github:

svn checkout 
https://github.com/royale-extras/closure-compiler/branches/royale/externs

Harbs

[1]https://help.github.com/articles/support-for-subversion-clients/ 
<https://help.github.com/articles/support-for-subversion-clients/>

> On Feb 13, 2018, at 1:54 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com> wrote:
> 
> Actually why are you talking about svn ? You mean GIT actually ?
> 
> 2018-02-13 12:47 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
> 
>> BTW, there’s a mojo for svn checkout:
>> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html <
>> https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html>
>> 
>> Maybe you can use that.
>> 
>> Harbs
>> 
>>> On Feb 13, 2018, at 1:41 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>>> 
>>> We need to download all the files from here: https://github.com/royale-
>> extras/closure-compiler/tree/royale/externs/ <https://github.com/royale-
>> extras/closure-compiler/tree/royale/externs/> to js/target/downloads.
>>> 
>>> Svn seems like the easiest way to do that, but you can use any method
>> that works.
>>> 
>>> Harbs
>>> 
>>>> On Feb 13, 2018, at 1:39 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com
>> <mailto:piotrzarzyck...@gmail.com>> wrote:
>>>> 
>>>> Can we avoid using svn ? Or it was used before ? I'm not familiar with
>> that
>>>> logic.
>>>> 
>>>> 2018-02-13 12:37 GMT+01:00 Harbs <ha...@in-tools.com > ha...@in-tools.com>>:
>>>> 
>>>>> We need to add svn checkout of the externs like I did in the ant
>> script.
>>>>> 
>>>>>> On Feb 13, 2018, at 1:36 PM, Apache Jenkins Server <
>>>>> jenk...@builds.apache.org <mailto:jenk...@builds.apache.org>> wrote:
>>>>>> 
>>>>>> The Apache Jenkins build system has built Royale-typedefs (build #34)
>>>>>> 
>>>>>> Status: Failure
>>>>>> 
>>>>>> Check console output at https://builds.apache.org/job/ <
>> https://builds.apache.org/job/>
>>>>> Royale-typedefs/34/ to view the results.
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> --
>>>> 
>>>> Piotr Zarzycki
>>>> 
>>>> Patreon: *https://www.patreon.com/piotrzarzycki <
>> https://www.patreon.com/piotrzarzycki>
>>>> <https://www.patreon.com/piotrzarzycki <https://www.patreon.com/
>> piotrzarzycki>>*
>>> 
>> 
>> 
> 
> 
> -- 
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*

Re: [MAVEN-BUILD] Royale-typedefs - Build # 34 - Failure

[Gabe Harbs]

BTW, there’s a mojo for svn checkout:
https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html 
<https://maven.apache.org/scm/maven-scm-plugin/checkout-mojo.html>

Maybe you can use that.

Harbs

> On Feb 13, 2018, at 1:41 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
> 
> We need to download all the files from here: 
> https://github.com/royale-extras/closure-compiler/tree/royale/externs/ 
> <https://github.com/royale-extras/closure-compiler/tree/royale/externs/> to 
> js/target/downloads.
> 
> Svn seems like the easiest way to do that, but you can use any method that 
> works.
> 
> Harbs
> 
>> On Feb 13, 2018, at 1:39 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com 
>> <mailto:piotrzarzyck...@gmail.com>> wrote:
>> 
>> Can we avoid using svn ? Or it was used before ? I'm not familiar with that
>> logic.
>> 
>> 2018-02-13 12:37 GMT+01:00 Harbs <ha...@in-tools.com 
>> <mailto:ha...@in-tools.com>>:
>> 
>>> We need to add svn checkout of the externs like I did in the ant script.
>>> 
>>>> On Feb 13, 2018, at 1:36 PM, Apache Jenkins Server <
>>> jenk...@builds.apache.org <mailto:jenk...@builds.apache.org>> wrote:
>>>> 
>>>> The Apache Jenkins build system has built Royale-typedefs (build #34)
>>>> 
>>>> Status: Failure
>>>> 
>>>> Check console output at https://builds.apache.org/job/ 
>>>> <https://builds.apache.org/job/>
>>> Royale-typedefs/34/ to view the results.
>>> 
>>> 
>> 
>> 
>> -- 
>> 
>> Piotr Zarzycki
>> 
>> Patreon: *https://www.patreon.com/piotrzarzycki 
>> <https://www.patreon.com/piotrzarzycki>
>> <https://www.patreon.com/piotrzarzycki 
>> <https://www.patreon.com/piotrzarzycki>>*
> 

Re: Build failed in Jenkins: royale-typedefs #139

[Gabe Harbs]

I changed the extern files directly and changed the download locations.

I have one question though:

There are a whole group of externs under 
https://github.com/royale-extras/closure-compiler/tree/royale/externs 
<https://github.com/royale-extras/closure-compiler/tree/royale/externs>.

These have been downloaded as part of the closure-compiler and unzipped into 
the downloads folder. There’s a few ways we can handle this.

1. One is to use svn checkout 
https://github.com/royale-extras/closure-compiler/branches/royale/externs to 
download the full folder structure from Github. I think both ant and maven 
support calling svn. The only issue I see with this is that svn needs to be 
installed.
2. We can check out the entire git repo and copy the externs from that.
3. We can loop through the files and download each on explicitly. (This is how 
it’s being done for the node.js externs.)

I’m leaning towards option #1 considering it’s over 70 files.

Thoughts?

Harbs


> On Feb 13, 2018, at 11:48 AM, Gabe Harbs <harbs.li...@gmail.com> wrote:
> 
> I created royale-extras and cloned closure-compiler there.[1]
> 
> I believe closure-compiler has all the typedefs we are currently using. The 
> version of svg.js that’s hosted there[2] seems to be vastly improved over the 
> version we’re currently downloading.[3] It looks to me that all the patching 
> we are doing on sag.js is not necessary with the newer version.
> 
> es3.js and es6.js have patches as well I’m unclear on whether those changes 
> need to be applied. I think yes.
> 
> Harbs
> 
> [1]https://github.com/royale-extras/closure-compiler/ 
> <https://github.com/royale-extras/closure-compiler/>
> [2]https://github.com/royale-extras/closure-compiler/blob/master/contrib/externs/svg.js
>  
> <https://github.com/royale-extras/closure-compiler/blob/master/contrib/externs/svg.js>
> [3]https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/closureidl/svg.js
>  
> <https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/closureidl/svg.js>
> 
>> On Feb 13, 2018, at 8:26 AM, Gabe Harbs <harbs.li...@gmail.com 
>> <mailto:harbs.li...@gmail.com>> wrote:
>> 
>> We could make a non-Apache organization for Royale-related stuff which is 
>> not strictly part of our repos. Kind of like what I did for flex-extras[1]
>> 
>> [1]https://github.com/flex-extras <https://github.com/flex-extras>
>> 
>>> On Feb 13, 2018, at 8:06 AM, Alex Harui <aha...@adobe.com.INVALID 
>>> <mailto:aha...@adobe.com.INVALID>> wrote:
>>> 
>>> Where would the fork live?
>>> 
>>> You might also have to verify that all of the things we patch are
>>> available on GH or Git.
>>> 
>>> Seems like a good possibility,
>>> -Alex
>>> 
>>> On 2/12/18, 1:46 PM, "Gabe Harbs" <harbs.li...@gmail.com 
>>> <mailto:harbs.li...@gmail.com>> wrote:
>>> 
>>>> We could fork the Google externs on Github and update those. If we pull
>>>> from the forked repo, we would be able to quickly make changes that we
>>>> need and make PRs back to Google. That would also make it easy to pull in
>>>> changes that are made to Google’s repo.
>>>> 
>>>> Harbs
>>>> 
>>>>> On Feb 12, 2018, at 10:00 PM, Alex Harui <aha...@adobe.com.INVALID 
>>>>> <mailto:aha...@adobe.com.INVALID>>
>>>>> wrote:
>>>>> 
>>>>> For js.patch, see the js/build.xml in royale-typedefs and the make_patch
>>>>> target.
>>>>> 
>>>>> Lately, I've been thinking about finding some other way of dealing with
>>>>> this.  We used patches so we didn't have to host 3rd-party files in our
>>>>> source tree.  I think we may now have 3rd-party files elsewhere in our
>>>>> source tree so we could just put patched versions in our source tree and
>>>>> update LICENSE and headers appropriately.  There is an issue with
>>>>> staying
>>>>> synced up with the master 3rd-party file.  And, we could make
>>>>> pull-requests on the 3rd-party file in some cases.
>>>>> 
>>>>> Thoughts?
>>>>> -Alex 
>>>>> 
>>>>> On 2/12/18, 11:23 AM, "Gabe Harbs" <harbs.li...@gmail.com 
>>>>> <mailto:harbs.li...@gmail.com>
>>>>> <mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>> wrote:
>>>>> 
>>>>>> Where is that and how do I add to the patches?
>

Re: Royale Examples Blog proposal to all the team

[Gabe Harbs]

Great initiative. Yes. I’d be interested in contributing.

One suggestion: Below the source code, we should have the result displayed in 
an iframe.

I’m not sure what you mean by calendar.

Harbs

> On Feb 13, 2018, at 11:54 AM, Carlos Rovira <carlosrov...@apache.org> wrote:
> 
> Thanks Piotr :)
> 
> @Harbs, link are here:
> 
> 
>   - http://royale.apache.org/blog/
> 
> 
> The first one:
> 
> 
>   - http://royale.apache.org/creating-a-hello-world-in-apache-royale/
> 
> 
> 
>   - https://twitter.com/ApacheRoyale/status/963092003075575810
> 
> 
> 
>   - https://www.facebook.com/ApacheRoyaleSDK/  (in facebook can't find the
>   exact url)
> 
> 
> 
> Did you get the calendar I did to organize blog post?
> 
> 
> thanks!
> 
> 2018-02-13 10:48 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
> 
>> Do you have a link?
>> 
>>> On Feb 13, 2018, at 11:44 AM, Carlos Rovira <carlosrov...@apache.org>
>> wrote:
>>> 
>>> Hi just let you know yesterday I make final touched to "Hello World" blog
>>> post example (it had already flexjs namespace refs)
>>> and make it live in twitter and facebook.
>>> 
>>> This is the first of our blog post that shows easy tips to show how easy
>> is
>>> to make things in Royale
>>> 
>>> I'd like to read thoughts from others in the team. What do you think
>> about
>>> this effort, Alex, Peter, Harbs, Erik, Olaf,... will you participate in
>> it?
>>> 
>>> it's only 1 tiny blog post each 6 months. I think is affordable for any
>> of
>>> us...
>>> 
>>> ...and make us to be of social networks each two weeks, (a part from
>> other
>>> appearances about releases, articles, and other things we want to
>> promote)
>>> 
>>> Thanks!
>>> 
>>> Carlos
>>> 
>>> 
>>> 
>>> 2018-02-09 13:19 GMT+01:00 Andrew Wetmore <cottag...@gmail.com>:
>>> 
>>>> I see the calendar!
>>>> 
>>>> On Fri, Feb 9, 2018 at 5:04 AM, Carlos Rovira <carlosrov...@apache.org>
>>>> wrote:
>>>> 
>>>>> Hi Just created the shared calendar and send invitations
>>>>> 
>>>>> please let me know if you received yours. As well, I created events
>> with
>>>>> each name on Mondays each 2 weeks.
>>>>> 
>>>>> We can start this Monday with the already posted "Hello World in
>> Royale"
>>>>> and share it vía twitter and facebook.
>>>>> 
>>>>> Please review the calendar and take into account that as we are a huge
>>>> team
>>>>> we have lots of time to make this real.
>>>>> 
>>>>> If anyone doesn't like the idea or don't want to participate, let us
>> know
>>>>> to make the calendar adjustments
>>>>> 
>>>>> thanks!
>>>>> 
>>>>> Carlos
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 2018-02-09 9:47 GMT+01:00 Carlos Rovira <carlosrov...@apache.org>:
>>>>> 
>>>>>> Great Om!,
>>>>>> 
>>>>>> we can create the post as drafts and a shared calendar. As people ends
>>>>> his
>>>>>> post, we can schedule for the right day of publication (2 weeks per
>>>>> post).
>>>>>> 
>>>>>> I'll be creating a calendar and sharing with you all.
>>>>>> 
>>>>>> Anyone out there that wants to share something like this can join this
>>>>>> thread and talk about it. I think we don't want to close this effort
>>>> only
>>>>>> to royale team members
>>>>>> 
>>>>>> thanks!
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 2018-02-09 4:29 GMT+01:00 OmPrakash Muppirala <bigosma...@gmail.com>:
>>>>>> 
>>>>>>> Great idea, Carlos.
>>>>>>> 
>>>>>>> Here is one I volunteer to write about: Getting started with Royale
>> on
>>>>> npm
>>>>>>> 
>>>>>>> I will write this over the weekend and share it here.  We can post
>>>> after
>>>>>>> Andrew (and others) makes a sweep over it :-)
>>>>>>> 
>>>>>>>

Re: Royale Examples Blog proposal to all the team

[Gabe Harbs]

Do you have a link?

> On Feb 13, 2018, at 11:44 AM, Carlos Rovira  wrote:
> 
> Hi just let you know yesterday I make final touched to "Hello World" blog
> post example (it had already flexjs namespace refs)
> and make it live in twitter and facebook.
> 
> This is the first of our blog post that shows easy tips to show how easy is
> to make things in Royale
> 
> I'd like to read thoughts from others in the team. What do you think about
> this effort, Alex, Peter, Harbs, Erik, Olaf,... will you participate in it?
> 
> it's only 1 tiny blog post each 6 months. I think is affordable for any of
> us...
> 
> ...and make us to be of social networks each two weeks, (a part from other
> appearances about releases, articles, and other things we want to promote)
> 
> Thanks!
> 
> Carlos
> 
> 
> 
> 2018-02-09 13:19 GMT+01:00 Andrew Wetmore :
> 
>> I see the calendar!
>> 
>> On Fri, Feb 9, 2018 at 5:04 AM, Carlos Rovira 
>> wrote:
>> 
>>> Hi Just created the shared calendar and send invitations
>>> 
>>> please let me know if you received yours. As well, I created events with
>>> each name on Mondays each 2 weeks.
>>> 
>>> We can start this Monday with the already posted "Hello World in Royale"
>>> and share it vía twitter and facebook.
>>> 
>>> Please review the calendar and take into account that as we are a huge
>> team
>>> we have lots of time to make this real.
>>> 
>>> If anyone doesn't like the idea or don't want to participate, let us know
>>> to make the calendar adjustments
>>> 
>>> thanks!
>>> 
>>> Carlos
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 2018-02-09 9:47 GMT+01:00 Carlos Rovira :
>>> 
 Great Om!,
 
 we can create the post as drafts and a shared calendar. As people ends
>>> his
 post, we can schedule for the right day of publication (2 weeks per
>>> post).
 
 I'll be creating a calendar and sharing with you all.
 
 Anyone out there that wants to share something like this can join this
 thread and talk about it. I think we don't want to close this effort
>> only
 to royale team members
 
 thanks!
 
 
 
 2018-02-09 4:29 GMT+01:00 OmPrakash Muppirala :
 
> Great idea, Carlos.
> 
> Here is one I volunteer to write about: Getting started with Royale on
>>> npm
> 
> I will write this over the weekend and share it here.  We can post
>> after
> Andrew (and others) makes a sweep over it :-)
> 
> Thanks,
> Om
> 
> On Thu, Feb 8, 2018 at 3:25 AM, Andrew Wetmore 
> wrote:
> 
>> This sounds really good. I will be glad to help people who have
>> strong
>> Royale skills but are uncomfortable writing for publication in
>>> English.
>> 
>> a
>> 
>> On Thu, Feb 8, 2018 at 7:11 AM, Carlos Rovira <
>>> carlosrov...@apache.org>
>> wrote:
>> 
>>> Hi,
>>> 
>>> I want to propose to start introducing some "pearls" (beads? ;))
>> of
> quick
>>> knowledge about Royale in our blog (Peter de Haan's flex examples
>>> blog
>>> style, remember it?)
>>> 
>>> *This will make the effect that each post will be published in
> Facebook
>> and
>>> Twitter and will make us to be "on the air" and reach more people
>>> that
>>> would eventually join us. Is not only about make it easy to learn
> Royale,
>>> but to make people out there know us!)*
>>> 
>>> To make this happen I propose to publish one tiny example each 2
> weeks,
>> and
>>> each time from a different team member.
>>> 
>>> Since we are around 10-15 people supporting this project, we can
>>> make
>>> calendar with publish dates, so we all know when we must publish.
>>> 
>>> In this way each one will be publishing each 6 month (approx.),
>> and
>>> I
>> think
>>> this is very affordable for all of us
>>> 
>>> what do you think?
>>> 
>>> (btw, we can introduce the content in WP and schedule for
>>> publication
> the
>>> day and hour we want, and then make it live royal.a.o)
>>> 
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>>> 
>> 
>> 
>> 
>> --
>> Andrew Wetmore
>> 
>> http://cottage14.blogspot.com/
>> 
> 
> --
> Carlos Rovira
> http://about.me/carlosrovira
> 
> 
> 
>>> 
>>> 
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>>> 
>> 
>> 
>> 
>> --
>> Andrew Wetmore
>> 
>> http://cottage14.blogspot.com/
>> 
> 
> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: ASDoc, Routing, Releases

[Gabe Harbs]

Yes. Having it as part of the release process makes sense.

Another way to go about it would be to have some way to limit which version 
data is displayed, so if unreleased data is set to display, it would show up, 
but by default the ASDoc app would only show data that is relevant to the 
latest release.

> On Feb 13, 2018, at 9:43 AM, Alex Harui <aha...@adobe.com.INVALID> wrote:
> 
> I pushed an Ant script that copies ASDoc from the CI server and copies it
> to the asdoc folder on the site.
> I also pushed the ASDoc.
> 
> I was going to hook this up to a CI build but am having second thoughts.
> Maybe we should only update after a release.  Otherwise, folks may find
> stuff in ASDoc that is only in the nightly and hasn't been released.
> 
> Thoughts?
> -Alex
> 
> On 2/6/18, 12:38 AM, "carlos.rov...@gmail.com 
> <mailto:carlos.rov...@gmail.com> on behalf of Carlos Rovira"
> <carlos.rov...@gmail.com <mailto:carlos.rov...@gmail.com> on behalf of 
> carlosrov...@apache.org <mailto:carlosrov...@apache.org>> wrote:
> 
>> Hi Alex,
>> 
>> in fact I think that's what it should be :)
>> don't know if as part of the website or in the royale-docs live url.
>> Anyway the proposed url is ok.
>> 
>> When I updated the website I overlay the folder with changes, as in the
>> website there's no "/asdoc/" url it will be untouched by my changes
>> 
>> thanks
>> 
>> 
>> 
>> 
>> 
>> 
>> 2018-02-06 6:29 GMT+01:00 Alex Harui <aha...@adobe.com.invalid>:
>> 
>>> ASDoc is looking better.  I was looking into tools to understand how
>>> google crawls sites and found that I can't use them on Jenkins.  I also
>>> saw in another thread that there is a way to get ASF Jenkins to push
>>> changes to a gitpubsub site.  Also, the ASDoc URL is long and ugly.
>>> 
>>> So, I'm thinking we should create a Jenkins job to copy ASDoc to
>>> royale.a.o.  Does anybody have any reason we shouldn't publish ASDoc on
>>> royale.a.o?  Also, what folder should we use?  royale.a.o/asdoc/?
>>> 
>>> Thoughts?
>>> -Alex
>>> 
>>> On 2/5/18, 9:44 AM, "Gabe Harbs" <harbs.li...@gmail.com> wrote:
>>> 
>>>>> What did you clean out?
>>>> 
>>>> Everything.
>>>> 
>>>> I deleted the entire contents of the three repo folders except the .git
>>>> folder.
>>>> 
>>>> I then stashed my local “changes" and pulled develop to bring my repo
>>>> into a clean up-to-date state.
>>>> 
>>>> I’m not sure what the problem was.
>>>> 
>>>> Harbs
>>>> 
>>>>> On Feb 5, 2018, at 7:37 PM, Alex Harui <aha...@adobe.com.INVALID>
>>> wrote:
>>>>> 
>>>>> What did you clean out?  It might help others if you update the
>>> scripts
>>>>> to
>>>>> clean up better.  I thought it was working correctly.
>>>>> 
>>>>> When things get renamed, the scripts don't always clean out the old
>>>>> folders.
>>>>> 
>>>>> -Alex
>>>>> 
>>>>> On 2/5/18, 9:29 AM, "Gabe Harbs" <harbs.li...@gmail.com
>>>>> <mailto:harbs.li...@gmail.com>> wrote:
>>>>> 
>>>>>> I manually cleaned out my repo folders, pulled again and now it
>>> seems
>>>>>> to
>>>>>> be working.
>>>>>> 
>>>>>> It looks like ant wipe-all on the compiler and ant clean all on
>>> asjs,
>>>>>> doesn’t quite clean everything…
>>>>>> 
>>>>>>> On Feb 5, 2018, at 7:13 PM, Gabe Harbs <harbs.li...@gmail.com>
>>> wrote:
>>>>>>> 
>>>>>>> It looks like I needed to set some env vars.
>>>>>>> 
>>>>>>> I did so, and I’m getting some JSON files, but not the full thing.
>>>>>>> 
>>>>>>> I just updated my repos and did ant clean all. I’m now getting a
>>>>>>> failed
>>>>>>> build of Royale and I’m not sure why...
>>>>>>> 
>>>>>>> royale.royaletasks.jar:
>>>>>>> 
>>>>>>> jar:
>>>>>>> 
>>>>>>> main:
>>>>>>> 
>>>>>>> main:
>>>>>>> 
>>>>>>> download:

Re: Build failed in Jenkins: royale-typedefs #139

[Gabe Harbs]

We could fork the Google externs on Github and update those. If we pull from 
the forked repo, we would be able to quickly make changes that we need and make 
PRs back to Google. That would also make it easy to pull in changes that are 
made to Google’s repo.

Harbs

> On Feb 12, 2018, at 10:00 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
> 
> For js.patch, see the js/build.xml in royale-typedefs and the make_patch
> target.
> 
> Lately, I've been thinking about finding some other way of dealing with
> this.  We used patches so we didn't have to host 3rd-party files in our
> source tree.  I think we may now have 3rd-party files elsewhere in our
> source tree so we could just put patched versions in our source tree and
> update LICENSE and headers appropriately.  There is an issue with staying
> synced up with the master 3rd-party file.  And, we could make
> pull-requests on the 3rd-party file in some cases.
> 
> Thoughts?
> -Alex 
> 
> On 2/12/18, 11:23 AM, "Gabe Harbs" <harbs.li...@gmail.com 
> <mailto:harbs.li...@gmail.com>> wrote:
> 
>> Where is that and how do I add to the patches?
>> 
>>> On Feb 12, 2018, at 7:31 PM, Alex Harui <aha...@adobe.com.INVALID>
>>> wrote:
>>> 
>>> Patch files are auto-generated by the Ant script, verified by a build,
>>> then committed to the src/main/patch/js.patch so that the Maven build
>>> can
>>> use it.  If we choose to try to manually maintain the patch files, we
>>> should comment out the auto-generation in the Ant build, otherwise as
>>> soon
>>> as someone uses it, it will blow away manual changes.  And if you had
>>> auto-generated the patch file, it probably wouldn't have had formatting
>>> issues.
>>> 
>>> HTH,
>>> -Alex
>>> 
>>> On 2/12/18, 8:26 AM, "Yishay Weiss" <yishayj...@hotmail.com
>>> <mailto:yishayj...@hotmail.com <mailto:yishayj...@hotmail.com>>> wrote:
>>> 
>>>> Add, see my later mail.
>>>> 
>>>> From: Gabe Harbs<mailto:harbs.li...@gmail.com 
>>>> <mailto:harbs.li...@gmail.com>>
>>>> Sent: Monday, February 12, 2018 6:23 PM
>>>> To: dev@royale.apache.org 
>>>> <mailto:dev@royale.apache.org><mailto:dev@royale.apache.org 
>>>> <mailto:dev@royale.apache.org>>
>>>> Subject: Re: Build failed in Jenkins: royale-typedefs #139
>>>> 
>>>> What was it? Did you add a space, or remove a space?
>>>>> On Feb 12, 2018, at 6:11 PM, Yishay Weiss <yishayj...@hotmail.com 
>>>>> <mailto:yishayj...@hotmail.com>>
>>>>> wrote:
>>>>> 
>>>>> I fixed it for my machine. Hopefully Jenkins will be happy too.
>>>>> 
>>>>> From: Gabe Harbs<mailto:harbs.li...@gmail.com 
>>>>> <mailto:harbs.li...@gmail.com>>
>>>>> Sent: Monday, February 12, 2018 5:18 PM
>>>>> To: dev@royale.apache.org 
>>>>> <mailto:dev@royale.apache.org><mailto:dev@royale.apache.org 
>>>>> <mailto:dev@royale.apache.org>>
>>>>> Subject: Re: Build failed in Jenkins: royale-typedefs #139
>>>>> 
>>>>> Does anyone understand the patch file syntax enough to guess what’s
>>>>> wrong?
>>>>> 
>>>>>> On Feb 12, 2018, at 5:15 PM, Yishay Weiss <yishayj...@hotmail.com 
>>>>>> <mailto:yishayj...@hotmail.com>>
>>>>>> wrote:
>>>>>> 
>>>>>> I  have the same result with ant on my machine. It’s probably a
>>>>>> windows/mac thing.
>>>>>> 
>>>>>> From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com 
>>>>>> <mailto:piotrzarzyck...@gmail.com>>
>>>>>> Sent: Monday, February 12, 2018 3:13 PM
>>>>>> To: dev@royale.apache.org 
>>>>>> <mailto:dev@royale.apache.org><mailto:dev@royale.apache.org 
>>>>>> <mailto:dev@royale.apache.org>>
>>>>>> Subject: Re: Build failed in Jenkins: royale-typedefs #139
>>>>>> 
>>>>>> Locally I have same result. I tried couple of things but nothing
>>>>>> help.
>>>>>> I
>>>>>> see that it is being applied by following command:
>>>>>> 
>>>>>> [DEBUG] Executing command line: [C:\Program Files\Git\cmd\git.exe,
>>>>>> apply,
>>

Re: Build failed in Jenkins: royale-typedefs #139

[Gabe Harbs]

Where is that and how do I add to the patches?

> On Feb 12, 2018, at 7:31 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
> 
> Patch files are auto-generated by the Ant script, verified by a build,
> then committed to the src/main/patch/js.patch so that the Maven build can
> use it.  If we choose to try to manually maintain the patch files, we
> should comment out the auto-generation in the Ant build, otherwise as soon
> as someone uses it, it will blow away manual changes.  And if you had
> auto-generated the patch file, it probably wouldn't have had formatting
> issues.
> 
> HTH,
> -Alex
> 
> On 2/12/18, 8:26 AM, "Yishay Weiss" <yishayj...@hotmail.com 
> <mailto:yishayj...@hotmail.com>> wrote:
> 
>> Add, see my later mail.
>> 
>> From: Gabe Harbs<mailto:harbs.li...@gmail.com>
>> Sent: Monday, February 12, 2018 6:23 PM
>> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
>> Subject: Re: Build failed in Jenkins: royale-typedefs #139
>> 
>> What was it? Did you add a space, or remove a space?
>>> On Feb 12, 2018, at 6:11 PM, Yishay Weiss <yishayj...@hotmail.com>
>>> wrote:
>>> 
>>> I fixed it for my machine. Hopefully Jenkins will be happy too.
>>> 
>>> From: Gabe Harbs<mailto:harbs.li...@gmail.com>
>>> Sent: Monday, February 12, 2018 5:18 PM
>>> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
>>> Subject: Re: Build failed in Jenkins: royale-typedefs #139
>>> 
>>> Does anyone understand the patch file syntax enough to guess what’s
>>> wrong?
>>> 
>>>> On Feb 12, 2018, at 5:15 PM, Yishay Weiss <yishayj...@hotmail.com>
>>>> wrote:
>>>> 
>>>> I  have the same result with ant on my machine. It’s probably a
>>>> windows/mac thing.
>>>> 
>>>> From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
>>>> Sent: Monday, February 12, 2018 3:13 PM
>>>> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
>>>> Subject: Re: Build failed in Jenkins: royale-typedefs #139
>>>> 
>>>> Locally I have same result. I tried couple of things but nothing help.
>>>> I
>>>> see that it is being applied by following command:
>>>> 
>>>> [DEBUG] Executing command line: [C:\Program Files\Git\cmd\git.exe,
>>>> apply,
>>>> --ignore-whitespace, --whitespace=nowarn,
>>>> D:\Work\royale-sources\royale-typedefs\js/src/main/patch/js.patch]
>>>> error: corrupt patch at line 64
>>>> 
>>>> Thanks, Piotr
>>>> 
>>>> 
>>>> 2018-02-12 13:47 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
>>>> 
>>>>> Thanks.
>>>>> 
>>>>>> On Feb 12, 2018, at 2:43 PM, Piotr Zarzycki
>>>>>> <piotrzarzyck...@gmail.com>
>>>>> wrote:
>>>>>> 
>>>>>> Let me build typedefs locally by Maven will see.
>>>>>> 
>>>>>> 2018-02-12 13:36 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
>>>>>> 
>>>>>>> I have no idea why this failed. The patch applied on my machine and
>>>>>>> line
>>>>>>> 64 is an empty line.
>>>>>>> 
>>>>>>> Maybe it’s a Windows line ending problem?
>>>>>>> 
>>>>>>> Thoughts?
>>>>>>> Harbs
>>>>>>> 
>>>>>>>> On Feb 12, 2018, at 2:12 PM, apacheroyal...@gmail.com wrote:
>>>>>>>> 
>>>>>>>> See 
>>>>>>>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapa 
>>>>>>>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapa>
>>>>>>>> cheroyaleci.westus2.cloudapp.azure.com 
>>>>>>>> <http://cheroyaleci.westus2.cloudapp.azure.com/>=02%7C01%7Caharui%40adobe
>>>>>>>> .com%7Ca91f37b4a59c41d2dead08d5723574f0%7Cfa7b1b5a7b34438794aed2c178
>>>>>>>> decee1%7C0%7C0%7C636540496276826984=LL61UmzMw2XOCgf3qyF5QdqkfK
>>>>>>>> iJJpsRUGawhg2Ub8s%3D=0:
>>>>>>> 8080/job/royale-typedefs/139/display/redirect>
>>>>>>>> 
>>>>>>>> --
>>>>>>>> Started by upstream project "royale-compiler" bu

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

[Gabe Harbs]

I was kind of waiting for you to come back online to see where you stood on 
these issues.

You’re the RM and I’m not interested in causing you extra work. If you had 
wanted to do another RC, then I would have waited and tested that one. If the 
npm issue could have been fixed without another RC, even better and I would 
have tested that. If not, like I said, I was happy to vote for this release.

This release passed. Let’s move on.

Harbs

> On Feb 12, 2018, at 7:40 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
> 
> My point is that is shouldn't matter when Om fixed the npm issue.  It was
> too late and not as important as getting other stuff done.  No need to
> wait to see how hard the fix would be.  We want to adopt the philosophy
> that by default, every found issue goes to the next release unless it is
> REALLY important.
> 
> Maybe it is just me, but I find it hard to start in on new big tasks when
> I have active release and develop branches on my machine and have to
> monitor vote and discuss threads.  I am way more efficient when the voting
> is over, the bits are pushed and I can just work in one branch.
> Running the scripts to create an RC isn't "hard" per-se, but it ties up my
> computer and my brain.
> 
> And as I said before, a new RC causes ALL of our users to wait for new
> features and fixes.
> 
> My 2 cents,
> -Alex
> 
> On 2/12/18, 8:41 AM, "Gabe Harbs" <harbs.li...@gmail.com 
> <mailto:harbs.li...@gmail.com>> wrote:
> 
>> My comments were not to say that I wasn’t voting for the release. I was
>> just documenting my difficulties with the approval script.
>> 
>> In fact I was about to vote +1 when I saw that Om fixed the npm issue.
>> 
>> I wanted to test the npm release before I sent in my vote. If you want to
>> push it to next release or fix it post release, that’s fine with me.
>> 
>> Harbs
>> 
>>> On Feb 12, 2018, at 6:24 PM, Alex Harui <aha...@adobe.com.INVALID>
>>> wrote:
>>> 
>>> Voters,
>>> 
>>> Apparently some of you have not quite bought into the new philosophy of
>>> "better than last release and not illegal".  The cost of a new RC is
>>> non-trivial.  We have some users who are asking for help to port their
>>> apps against a deadline.  To me, that is way more important than fixing
>>> js-swf for NPM in this release because js-swf was broken in the prior
>>> release.  This release is "better than the last release and not
>>> illegal".
>>> The next release is will be in 30 days or less.
>>> 
>>> Someone hand-patched package.json and provided it on npm in the last
>>> release.  It can probably be done for this release.  I'll bet there will
>>> be a big bug in every release for a while.  As long as it isn't a major
>>> regression, we should ship it and move on.
>>> 
>>> My 2 cents,
>>> -Alex
>>> 
>>> On 2/12/18, 1:50 AM, "Gabe Harbs" <harbs.li...@gmail.com
>>> <mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>> wrote:
>>> 
>>>> BTW, I noticed that I’m getting an error near the end of my ant build.
>>>> This does not cause the “general bull” to fail:
>>>> 
>>>> check-playerglobal-home:
>>>>   [echo] PLAYERGLOBAL_HOME is /Apache/frameworks/libs/player
>>>>   [echo] playerglobal.version is 11.1
>>>>   [echo] playerglobal.swc is
>>>> /Apache/frameworks/libs/player/11.1/playerglobal.swc
>>>> 
>>>> check-air-home:
>>>>   [echo] AIR_HOME is /Apache/frameworks/AIRSDK_Compiler
>>>> 
>>>> check-compiler-home:
>>>> 
>>>> check-compile-env:
>>>>   [echo] OS: Mac OS X / 10.12.6 / x86_64
>>>>   [echo] VM: Java HotSpot(TM) 64-Bit Server VM / 25.152-b16
>>>>   [echo] Java: 1.8.0_152
>>>>   [echo] Ant: Apache Ant(TM) version 1.10.2 compiled on February 3
>>>> 2018 Ant Java Version: 1.8
>>>> 
>>>> prepare:
>>>> 
>>>> compile:
>>>> 
>>>> flat-ui-icons:
>>>>   [java] 
>>>>   [java] Error: Missing builtin type Object
>>>>   [java] 
>>>>   [java] 
>>>>   [java] Error: Unable to build SWF
>>>> /Apache/royale-asjs/frameworks/fonts/flat-ui-icons-regular.swf
>>>>   [java] 
>>>>   [java] 
>>>>   [java] Java Result: 2
>>>> 
>>>>> On Feb 12, 2018, at 11:21 AM, Gabe Harbs <harbs.li...@gmail.com 
>>>

Re: [VOTE] Release Apache Royale 0.9.1 RC1

[Gabe Harbs]

+1
Package 
https://dist.apache.org/repos/dist/dev/royale/0.9.1/rc1/apache-royale-0.9.1-src.tar.gz
Java 1.8
OS: Mac OS X x86_64 10.12.6
Source kit signatures match: y
Source kit builds: y
README is ok: y
RELEASE_NOTES is ok: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives: y
No unapproved binaries: y

Package 
https://dist.apache.org/repos/dist/dev/royale/0.9.1/rc1/binaries/apache-royale-0.9.1-bin-js-swf.tar.gz
Binary kit signatures match: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives in binary package: y
No unapproved binaries in binary package: y

I could not get the approval script to finish correctly, but:

* I was able to build the compiler and frameworks
* I tested that the artifacts worked in VS Code
* I tested that I was able to build the sample applications
* I tested that I was able to build my own application.
* I noticed that some places “the original code” refers to ASC 2 and other 
places it refers to Flex. I’m assuming that was intentional.

I was not able to install the js-swf version using npm. I noticed that Om just 
commented that he’s checking in a fix for that. I’m unclear on whether we can 
fix this before the next release, but even js-only is better than nothing.

Harbs

> On Feb 11, 2018, at 8:25 PM, Piotr Zarzycki  wrote:
> 
> +1 (Binding)
> 
> Following tests has been performed:
> - I checked IDE compatible binaries with Moonshine IDE - build couple of
> mine examples - OK
> - I checked Maven artifacts and build using them all my examples - OK
> - I have build sources using Maven. I didn't run ANT build. - OK
> 
> I didn't use ApprovalScript, cause it didn't work for me. - Details
> mentioned in Discuss.
> 
> README - we could add more details related to fixes for DataGrid component.
> Let's do this in the next release!
> 
> Thanks, Piotr
> 
> 
> 
> 2018-02-08 21:02 GMT+01:00 Alex Harui :
> 
>> +1
>> Package
>> https://dist.apache.org/repos/dist/dev/royale/0.9.1/rc1/
>> apache-royale-0.9.1
>> -src.tar.gz
>> Java 1.8
>> OS: Mac OS X x86_64 10.12.5
>> Source kit signatures match: y
>> Source kit builds: y
>> README is ok: y
>> RELEASE_NOTES is ok: y
>> NOTICE is ok: y
>> LICENSE is ok: y
>> No unapproved licenses or archives: y
>> No unapproved binaries: y
>> 
>> 
>> Package
>> https://dist.apache.org/repos/dist/dev/royale/0.9.1/rc1/
>> binaries/apache-roy
>> ale-0.9.1-bin-js-swf.tar.gz
>> Binary kit signatures match: y
>> NOTICE is ok: y
>> LICENSE is ok: y
>> No unapproved licenses or archives in binary package: y
>> No unapproved binaries in binary package: y
>> 
>> 
>> 
>> 
>> On 2/8/18, 11:58 AM, "Alex Harui"  wrote:
>> 
>>> Hi,
>>> 
>>> This is vote for the 0.9.1 release of Apache Royale.
>>> 
>>> The release candidate can be found here;
>>> https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fdist.apac
>>> he.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.1%2Frc1%2F&
>> data=02%7C01%7Caharu
>>> i%40adobe.com%7C249d7363c28c4ff6a24308d56f2e
>> 5765%7C71f1da39c0a84d5a8d88a67
>>> b23c30bf4%7C0%7C0%7C636537167178722263=
>> aVaTU9jR5UiDlLc8riHGHMfxCSOMl
>>> Fi43IehIDsvwa8%3D=0
>>> 
>>> Before voting please review the section,'What are the ASF requirements on
>>> approving a release?', at:
>>> https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fwww.apache
>>> .org%2Fdev%2Frelease.html%23approving-a-release=02%
>> 7C01%7Caharui%40ad
>>> obe.com%7C249d7363c28c4ff6a24308d56f2e5765%7C71f1da39c0a84d5a8d88a67b23c3
>> 0
>>> bf4%7C0%7C0%7C636537167178722263=p%2Fbj8jT5O5srU%
>> 2B3xmXJeNU1PZDiKvWG
>>> K7MjXGcNJsQY%3D=0
>>> 
>>> 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://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fdist.apac
>>> he.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.1%2Frc1%
>> 2Fbinaries%2Fapache-roy
>>> =02%7C01%7Caharui%40adobe.com%7C249d7363c28c4ff6a24308d56f2e
>> 5765%7C71
>>> f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%7C636537167178722263&
>> sdata=Rv6NjuIH
>>> gTh2tSfIfSWh0ySnAcpjMLrSBi4Fz3%2B4GCI%3D=0
>>> ale-0.9.1-bin-js.tar.gz -g
>>> 
>>> The full package with SWF support can be installed via:
>>> 
>>> npm install
>>> https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fdist.apac
>>> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

[Gabe Harbs]

My comments were not to say that I wasn’t voting for the release. I was just 
documenting my difficulties with the approval script.

In fact I was about to vote +1 when I saw that Om fixed the npm issue.

I wanted to test the npm release before I sent in my vote. If you want to push 
it to next release or fix it post release, that’s fine with me.

Harbs

> On Feb 12, 2018, at 6:24 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
> 
> Voters,
> 
> Apparently some of you have not quite bought into the new philosophy of
> "better than last release and not illegal".  The cost of a new RC is
> non-trivial.  We have some users who are asking for help to port their
> apps against a deadline.  To me, that is way more important than fixing
> js-swf for NPM in this release because js-swf was broken in the prior
> release.  This release is "better than the last release and not illegal".
> The next release is will be in 30 days or less.
> 
> Someone hand-patched package.json and provided it on npm in the last
> release.  It can probably be done for this release.  I'll bet there will
> be a big bug in every release for a while.  As long as it isn't a major
> regression, we should ship it and move on.
> 
> My 2 cents,
> -Alex
> 
> On 2/12/18, 1:50 AM, "Gabe Harbs" <harbs.li...@gmail.com 
> <mailto:harbs.li...@gmail.com>> wrote:
> 
>> BTW, I noticed that I’m getting an error near the end of my ant build.
>> This does not cause the “general bull” to fail:
>> 
>> check-playerglobal-home:
>>[echo] PLAYERGLOBAL_HOME is /Apache/frameworks/libs/player
>>[echo] playerglobal.version is 11.1
>>[echo] playerglobal.swc is
>> /Apache/frameworks/libs/player/11.1/playerglobal.swc
>> 
>> check-air-home:
>>[echo] AIR_HOME is /Apache/frameworks/AIRSDK_Compiler
>> 
>> check-compiler-home:
>> 
>> check-compile-env:
>>[echo] OS: Mac OS X / 10.12.6 / x86_64
>>[echo] VM: Java HotSpot(TM) 64-Bit Server VM / 25.152-b16
>>[echo] Java: 1.8.0_152
>>[echo] Ant: Apache Ant(TM) version 1.10.2 compiled on February 3
>> 2018 Ant Java Version: 1.8
>> 
>> prepare:
>> 
>> compile:
>> 
>> flat-ui-icons:
>>[java] 
>>[java] Error: Missing builtin type Object
>>[java] 
>>[java] 
>>[java] Error: Unable to build SWF
>> /Apache/royale-asjs/frameworks/fonts/flat-ui-icons-regular.swf
>>[java] 
>>[java] 
>>[java] Java Result: 2
>> 
>>> On Feb 12, 2018, at 11:21 AM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>>> 
>>> Does this require a new rc or can the script just be updated?
>>> 
>>>> On Feb 12, 2018, at 10:08 AM, OmPrakash Muppirala
>>>> <bigosma...@gmail.com> wrote:
>>>> 
>>>> I've pushed in a fix for the broken js-swf npm installation process.
>>>> 
>>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub 
>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub>.
>>>> com%2Fapache%2Froyale-asjs%2Fcommit%2Fb9a1b32975cc755475ade761f36993efc8
>>>> f1f058=02%7C01%7Caharui%40adobe.com 
>>>> <http://40adobe.com/>%7Ca934cb5af6e34aaf4bdd08d571fe1
>>>> 4cc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636540258442339413
>>>> a=3k%2FpsTS20s6JbaVpeTstXsL5MTVZl%2Bf%2FpQ7E8GKI8%2FE%3D=0
>>>> 
>>>> Alex, given that this release is about npm installation (as per the
>>>> RELEASE_NOTES), we need this fix to go in.
>>>> 
>>>> Sorry for the trouble :-(
>>>> 
>>>> Thanks,
>>>> Om
>>>> 
>>>> On Sun, Feb 11, 2018 at 9:41 AM, Gabe Harbs <harbs.li...@gmail.com 
>>>> <mailto:harbs.li...@gmail.com>>
>>>> wrote:
>>>> 
>>>>> Trying that now…
>>>>> 
>>>>>> On Feb 11, 2018, at 5:09 PM, Piotr Zarzycki
>>>>>> <piotrzarzyck...@gmail.com <mailto:piotrzarzyck...@gmail.com>>
>>>>> wrote:
>>>>>> 
>>>>>> In the previous release approval script also runs Maven :) You can
>>>>> manually
>>>>>> copy playerglobal.swc 20.0 to the following location [1]. - That is
>>>>>> an
>>>>>> workaround.
>>>>>> 
>>>>>> [1] .m2\repository\com\adobe\flash\framework\playerglobal\20.0\
>>>>>> 
>>>>>> 2018-02-11 16:00 GMT+01:00 Gabe Harb

Re: Build failed in Jenkins: royale-typedefs #139

[Gabe Harbs]

What was it? Did you add a space, or remove a space?
> On Feb 12, 2018, at 6:11 PM, Yishay Weiss <yishayj...@hotmail.com> wrote:
> 
> I fixed it for my machine. Hopefully Jenkins will be happy too.
> 
> From: Gabe Harbs<mailto:harbs.li...@gmail.com>
> Sent: Monday, February 12, 2018 5:18 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: Build failed in Jenkins: royale-typedefs #139
> 
> Does anyone understand the patch file syntax enough to guess what’s wrong?
> 
>> On Feb 12, 2018, at 5:15 PM, Yishay Weiss <yishayj...@hotmail.com> wrote:
>> 
>> I  have the same result with ant on my machine. It’s probably a windows/mac 
>> thing.
>> 
>> From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
>> Sent: Monday, February 12, 2018 3:13 PM
>> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
>> Subject: Re: Build failed in Jenkins: royale-typedefs #139
>> 
>> Locally I have same result. I tried couple of things but nothing help. I
>> see that it is being applied by following command:
>> 
>> [DEBUG] Executing command line: [C:\Program Files\Git\cmd\git.exe, apply,
>> --ignore-whitespace, --whitespace=nowarn,
>> D:\Work\royale-sources\royale-typedefs\js/src/main/patch/js.patch]
>> error: corrupt patch at line 64
>> 
>> Thanks, Piotr
>> 
>> 
>> 2018-02-12 13:47 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
>> 
>>> Thanks.
>>> 
>>>> On Feb 12, 2018, at 2:43 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com>
>>> wrote:
>>>> 
>>>> Let me build typedefs locally by Maven will see.
>>>> 
>>>> 2018-02-12 13:36 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
>>>> 
>>>>> I have no idea why this failed. The patch applied on my machine and line
>>>>> 64 is an empty line.
>>>>> 
>>>>> Maybe it’s a Windows line ending problem?
>>>>> 
>>>>> Thoughts?
>>>>> Harbs
>>>>> 
>>>>>> On Feb 12, 2018, at 2:12 PM, apacheroyal...@gmail.com wrote:
>>>>>> 
>>>>>> See <http://apacheroyaleci.westus2.cloudapp.azure.com:
>>>>> 8080/job/royale-typedefs/139/display/redirect>
>>>>>> 
>>>>>> --
>>>>>> Started by upstream project "royale-compiler" build number 89
>>>>>> originally caused by:
>>>>>> Started by timer
>>>>>> Building in workspace <http://apacheroyaleci.
>>> westus2.cloudapp.azure.com:
>>>>> 8080/job/royale-typedefs/ws/>
>>>>>>> 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 b50b80fa675d06c5b8e9145b1b3f2e54784f25a8
>>>>> (refs/remotes/origin/develop)
>>>>>>> git.exe config core.sparsecheckout # timeout=10
>>>>>>> git.exe checkout -f b50b80fa675d06c5b8e9145b1b3f2e54784f25a8
>>>>>> Commit message: "Added overflowX and overflowY"
>>>>>>> git.exe rev-list --no-walk b50b80fa675d06c5b8e9145b1b3f2e54784f25a8 #
>>>>> timeout=10
>>>>>> [royale-typedefs] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat
>>>>> main && exit %%ERRORLEVEL%%"
>>>>>> Buildfile: <http://apacheroyaleci.westus2.cloudapp.azure.com:
>>>>> 8080/job/royale-typedefs/ws/build.xml>
>>>>>> 
>>>>>> main:
>>>>>> 
>>>>>> download:
>>>>>>  [echo] <http://apacheroyaleci.westus2.cloudapp.azure.com:
>>>>> 8080/job/royale-typedefs/ws/js/..>
>>>>>> [un

Re: Build failed in Jenkins: royale-typedefs #139

[Gabe Harbs]

Does anyone understand the patch file syntax enough to guess what’s wrong?

> On Feb 12, 2018, at 5:15 PM, Yishay Weiss <yishayj...@hotmail.com> wrote:
> 
> I  have the same result with ant on my machine. It’s probably a windows/mac 
> thing.
> 
> From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
> Sent: Monday, February 12, 2018 3:13 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: Build failed in Jenkins: royale-typedefs #139
> 
> Locally I have same result. I tried couple of things but nothing help. I
> see that it is being applied by following command:
> 
> [DEBUG] Executing command line: [C:\Program Files\Git\cmd\git.exe, apply,
> --ignore-whitespace, --whitespace=nowarn,
> D:\Work\royale-sources\royale-typedefs\js/src/main/patch/js.patch]
> error: corrupt patch at line 64
> 
> Thanks, Piotr
> 
> 
> 2018-02-12 13:47 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
> 
>> Thanks.
>> 
>>> On Feb 12, 2018, at 2:43 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com>
>> wrote:
>>> 
>>> Let me build typedefs locally by Maven will see.
>>> 
>>> 2018-02-12 13:36 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
>>> 
>>>> I have no idea why this failed. The patch applied on my machine and line
>>>> 64 is an empty line.
>>>> 
>>>> Maybe it’s a Windows line ending problem?
>>>> 
>>>> Thoughts?
>>>> Harbs
>>>> 
>>>>> On Feb 12, 2018, at 2:12 PM, apacheroyal...@gmail.com wrote:
>>>>> 
>>>>> See <http://apacheroyaleci.westus2.cloudapp.azure.com:
>>>> 8080/job/royale-typedefs/139/display/redirect>
>>>>> 
>>>>> --
>>>>> Started by upstream project "royale-compiler" build number 89
>>>>> originally caused by:
>>>>> Started by timer
>>>>> Building in workspace <http://apacheroyaleci.
>> westus2.cloudapp.azure.com:
>>>> 8080/job/royale-typedefs/ws/>
>>>>>> 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 b50b80fa675d06c5b8e9145b1b3f2e54784f25a8
>>>> (refs/remotes/origin/develop)
>>>>>> git.exe config core.sparsecheckout # timeout=10
>>>>>> git.exe checkout -f b50b80fa675d06c5b8e9145b1b3f2e54784f25a8
>>>>> Commit message: "Added overflowX and overflowY"
>>>>>> git.exe rev-list --no-walk b50b80fa675d06c5b8e9145b1b3f2e54784f25a8 #
>>>> timeout=10
>>>>> [royale-typedefs] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat
>>>> main && exit %%ERRORLEVEL%%"
>>>>> Buildfile: <http://apacheroyaleci.westus2.cloudapp.azure.com:
>>>> 8080/job/royale-typedefs/ws/build.xml>
>>>>> 
>>>>> main:
>>>>> 
>>>>> download:
>>>>>   [echo] <http://apacheroyaleci.westus2.cloudapp.azure.com:
>>>> 8080/job/royale-typedefs/ws/js/..>
>>>>>  [unjar] Expanding: C:\Program Files (x86)\Jenkins\workspace\
>>>> royale-compiler\compiler-jx\lib\google\closure-compiler\compiler.jar
>> into
>>>> <http://apacheroyaleci.westus2.cloudapp.azure.com:
>>>> 8080/job/royale-typedefs/ws/js/target/temp/externs>
>>>>>  [unzip] Expanding: <http://apacheroyaleci.westus2.cloudapp.azure.com
>> :
>>>> 8080/job/royale-typedefs/ws/js/target/temp/externs/externs.zip> into <
>>>> http://apacheroyaleci.westus2.cloudapp.azure.com:
>>>> 8080/job/royale-typedefs/ws/js/target/downloads>
>>>>>[get] Getting: https://storage.googleapis.com/google-code-archive-
>>>> downloads/v2/code.google.com/closureidl/svg.js
>>>>&g

Re: Build failed in Jenkins: royale-typedefs #139

[Gabe Harbs]

Thanks.

> On Feb 12, 2018, at 2:43 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com> wrote:
> 
> Let me build typedefs locally by Maven will see.
> 
> 2018-02-12 13:36 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
> 
>> I have no idea why this failed. The patch applied on my machine and line
>> 64 is an empty line.
>> 
>> Maybe it’s a Windows line ending problem?
>> 
>> Thoughts?
>> Harbs
>> 
>>> On Feb 12, 2018, at 2:12 PM, apacheroyal...@gmail.com wrote:
>>> 
>>> See <http://apacheroyaleci.westus2.cloudapp.azure.com:
>> 8080/job/royale-typedefs/139/display/redirect>
>>> 
>>> --
>>> Started by upstream project "royale-compiler" build number 89
>>> originally caused by:
>>> Started by timer
>>> Building in workspace <http://apacheroyaleci.westus2.cloudapp.azure.com:
>> 8080/job/royale-typedefs/ws/>
>>>> 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 b50b80fa675d06c5b8e9145b1b3f2e54784f25a8
>> (refs/remotes/origin/develop)
>>>> git.exe config core.sparsecheckout # timeout=10
>>>> git.exe checkout -f b50b80fa675d06c5b8e9145b1b3f2e54784f25a8
>>> Commit message: "Added overflowX and overflowY"
>>>> git.exe rev-list --no-walk b50b80fa675d06c5b8e9145b1b3f2e54784f25a8 #
>> timeout=10
>>> [royale-typedefs] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat
>> main && exit %%ERRORLEVEL%%"
>>> Buildfile: <http://apacheroyaleci.westus2.cloudapp.azure.com:
>> 8080/job/royale-typedefs/ws/build.xml>
>>> 
>>> main:
>>> 
>>> download:
>>>[echo] <http://apacheroyaleci.westus2.cloudapp.azure.com:
>> 8080/job/royale-typedefs/ws/js/..>
>>>   [unjar] Expanding: C:\Program Files (x86)\Jenkins\workspace\
>> royale-compiler\compiler-jx\lib\google\closure-compiler\compiler.jar into
>> <http://apacheroyaleci.westus2.cloudapp.azure.com:
>> 8080/job/royale-typedefs/ws/js/target/temp/externs>
>>>   [unzip] Expanding: <http://apacheroyaleci.westus2.cloudapp.azure.com:
>> 8080/job/royale-typedefs/ws/js/target/temp/externs/externs.zip> into <
>> http://apacheroyaleci.westus2.cloudapp.azure.com:
>> 8080/job/royale-typedefs/ws/js/target/downloads>
>>> [get] Getting: https://storage.googleapis.com/google-code-archive-
>> downloads/v2/code.google.com/closureidl/svg.js
>>> [get] To: <http://apacheroyaleci.westus2.cloudapp.azure.com:
>> 8080/job/royale-typedefs/ws/js/target/downloads/svg.js>
>>> 
>>> double-check-file:
>>>[echo] ${env.ROYALE_DOWNLOAD_CACHE}
>>>[echo] Need file: ${still_no_file}
>>> 
>>> get-from-cache-if-needed:
>>> 
>>> fail-if-not-found:
>>> 
>>> preprocess:
>>>[exec] error: corrupt patch at line 64
>>> 
>>> BUILD FAILED
>>> <http://apacheroyaleci.westus2.cloudapp.azure.com:
>> 8080/job/royale-typedefs/ws/build.xml>:52: The following error occurred
>> while executing this line:
>>> <http://apacheroyaleci.westus2.cloudapp.azure.com:
>> 8080/job/royale-typedefs/ws/js/build.xml>:149: exec returned: 128
>>> 
>>> Total time: 2 seconds
>>> Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
>>> Build step 'Invoke Ant' marked build as failure
>> 
>> 
> 
> 
> -- 
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*

Re: Build failed in Jenkins: royale-typedefs #139

[Gabe Harbs]

I have no idea why this failed. The patch applied on my machine and line 64 is 
an empty line.

Maybe it’s a Windows line ending problem?

Thoughts?
Harbs

> On Feb 12, 2018, at 2:12 PM, apacheroyal...@gmail.com wrote:
> 
> See 
> 
> 
> --
> Started by upstream project "royale-compiler" build number 89
> 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 b50b80fa675d06c5b8e9145b1b3f2e54784f25a8 
> (refs/remotes/origin/develop)
>> git.exe config core.sparsecheckout # timeout=10
>> git.exe checkout -f b50b80fa675d06c5b8e9145b1b3f2e54784f25a8
> Commit message: "Added overflowX and overflowY"
>> git.exe rev-list --no-walk b50b80fa675d06c5b8e9145b1b3f2e54784f25a8 # 
>> 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:
> [exec] error: corrupt patch at line 64
> 
> BUILD FAILED
> :52:
>  The following error occurred while executing this line:
> :149:
>  exec returned: 128
> 
> Total time: 2 seconds
> Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
> Build step 'Invoke Ant' marked build as failure

Re: [MAVEN-BUILD] Royale-asjs - Build # 485 - Failure

[Gabe Harbs]

I don’t know about scaleX and rotate, but I was able to get translateY() to 
work by using @namespace "http://www.w3.org/1999/xhtml”;

It’s worth a shot…

Harbs

> On Feb 12, 2018, at 1:54 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com> wrote:
> 
> I had problem lately. I did found workaround. It looks like I will raise
> issue on the compiler in that case.
> 
> Thanks! Piotr
> 
> 2018-02-12 12:51 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
> 
>> I’m pretty sure that those need to be handled in the compiler.
>> 
>> The compiler needs to understand CSS as it parses it.
>> 
>> Harbs
>> 
>>> On Feb 12, 2018, at 1:48 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com>
>> wrote:
>>> 
>>> Harbs,
>>> 
>>> Does that file is also the place where we may add some missing functions
>>> from CSS ? For example scaleY, rotate etc. ?
>>> 
>>> Thanks,
>>> Piotr
>>> 
>>> 2018-02-12 12:17 GMT+01:00 Harbs <ha...@in-tools.com>:
>>> 
>>>> The relevant extern file appears to be: w3c_css.js
>>>> 
>>>> Harbs
>>>> 
>>>>> On Feb 12, 2018, at 1:16 PM, Harbs <ha...@in-tools.com> wrote:
>>>>> 
>>>>> The externs for CSSStyleDeclaration has `overflow`, but it’s missing
>>>> `overflowX` and `overflowY`.
>>>>> 
>>>>> That’s causing these two lines to fail (only in maven for some reason):
>>>>> 
>>>>> (value as UIBase).element.style.overflowY = "auto";
>>>>> (contentView as UIBase).element.style.overflowY = "auto”;
>>>>> 
>>>>> I could change these lines to:
>>>>> (value as UIBase).element.style[“overflowY”] = "auto";
>>>>> (contentView as UIBase).element.style[“overflowY”] = "auto”;
>>>>> 
>>>>> Although, I think patching the extern file is probably a better
>> solution.
>>>>> 
>>>>> I’m not clear on how to patch it though. Any pointers?
>>>>> 
>>>>> Harbs
>>>>> 
>>>>>> On Feb 12, 2018, at 1:00 PM, Apache Jenkins Server <
>>>> jenk...@builds.apache.org> wrote:
>>>>>> 
>>>>>> The Apache Jenkins build system has built Royale-asjs (build #485)
>>>>>> 
>>>>>> Status: Failure
>>>>>> 
>>>>>> Check console output at https://builds.apache.org/job/
>> Royale-asjs/485/
>>>> to view the results.
>>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> 
>>> Piotr Zarzycki
>>> 
>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>> <https://www.patreon.com/piotrzarzycki>*
>> 
>> 
> 
> 
> -- 
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*

Re: [MAVEN-BUILD] Royale-asjs - Build # 485 - Failure

[Gabe Harbs]

I’m pretty sure that those need to be handled in the compiler.

The compiler needs to understand CSS as it parses it.

Harbs

> On Feb 12, 2018, at 1:48 PM, Piotr Zarzycki  wrote:
> 
> Harbs,
> 
> Does that file is also the place where we may add some missing functions
> from CSS ? For example scaleY, rotate etc. ?
> 
> Thanks,
> Piotr
> 
> 2018-02-12 12:17 GMT+01:00 Harbs :
> 
>> The relevant extern file appears to be: w3c_css.js
>> 
>> Harbs
>> 
>>> On Feb 12, 2018, at 1:16 PM, Harbs  wrote:
>>> 
>>> The externs for CSSStyleDeclaration has `overflow`, but it’s missing
>> `overflowX` and `overflowY`.
>>> 
>>> That’s causing these two lines to fail (only in maven for some reason):
>>> 
>>> (value as UIBase).element.style.overflowY = "auto";
>>> (contentView as UIBase).element.style.overflowY = "auto”;
>>> 
>>> I could change these lines to:
>>> (value as UIBase).element.style[“overflowY”] = "auto";
>>> (contentView as UIBase).element.style[“overflowY”] = "auto”;
>>> 
>>> Although, I think patching the extern file is probably a better solution.
>>> 
>>> I’m not clear on how to patch it though. Any pointers?
>>> 
>>> Harbs
>>> 
 On Feb 12, 2018, at 1:00 PM, Apache Jenkins Server <
>> jenk...@builds.apache.org> wrote:
 
 The Apache Jenkins build system has built Royale-asjs (build #485)
 
 Status: Failure
 
 Check console output at https://builds.apache.org/job/Royale-asjs/485/
>> to view the results.
>>> 
>> 
>> 
> 
> 
> -- 
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> *

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

[Gabe Harbs]

BTW, I noticed that I’m getting an error near the end of my ant build. This 
does not cause the “general bull” to fail:

check-playerglobal-home:
 [echo] PLAYERGLOBAL_HOME is /Apache/frameworks/libs/player
 [echo] playerglobal.version is 11.1
 [echo] playerglobal.swc is 
/Apache/frameworks/libs/player/11.1/playerglobal.swc

check-air-home:
 [echo] AIR_HOME is /Apache/frameworks/AIRSDK_Compiler

check-compiler-home:

check-compile-env:
 [echo] OS: Mac OS X / 10.12.6 / x86_64
 [echo] VM: Java HotSpot(TM) 64-Bit Server VM / 25.152-b16
 [echo] Java: 1.8.0_152
 [echo] Ant: Apache Ant(TM) version 1.10.2 compiled on February 3 2018 Ant 
Java Version: 1.8

prepare:

compile:

flat-ui-icons:
 [java] 
 [java] Error: Missing builtin type Object
 [java] 
 [java] 
 [java] Error: Unable to build SWF 
/Apache/royale-asjs/frameworks/fonts/flat-ui-icons-regular.swf
 [java] 
 [java] 
 [java] Java Result: 2

> On Feb 12, 2018, at 11:21 AM, Gabe Harbs <harbs.li...@gmail.com> wrote:
> 
> Does this require a new rc or can the script just be updated?
> 
>> On Feb 12, 2018, at 10:08 AM, OmPrakash Muppirala <bigosma...@gmail.com> 
>> wrote:
>> 
>> I've pushed in a fix for the broken js-swf npm installation process.
>> https://github.com/apache/royale-asjs/commit/b9a1b32975cc755475ade761f36993efc8f1f058
>> 
>> Alex, given that this release is about npm installation (as per the
>> RELEASE_NOTES), we need this fix to go in.
>> 
>> Sorry for the trouble :-(
>> 
>> Thanks,
>> Om
>> 
>> On Sun, Feb 11, 2018 at 9:41 AM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>> 
>>> Trying that now…
>>> 
>>>> On Feb 11, 2018, at 5:09 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com>
>>> wrote:
>>>> 
>>>> In the previous release approval script also runs Maven :) You can
>>> manually
>>>> copy playerglobal.swc 20.0 to the following location [1]. - That is an
>>>> workaround.
>>>> 
>>>> [1] .m2\repository\com\adobe\flash\framework\playerglobal\20.0\
>>>> 
>>>> 2018-02-11 16:00 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com >> harbs.li...@gmail.com>>:
>>>> 
>>>>> Ah. Foo… :-(
>>>>> 
>>>>> The maven build failed on Core (after more than 30 minutes):
>>>>> 
>>>>> [ERROR] Failed to execute goal org.apache.royale.compiler:
>>>>> royale-maven-plugin:0.9.1:compile-as (default-compile-as) on project
>>>>> Core: Could not resolve dependencies for project
>>>>> org.apache.royale.framework:Core:swc:0.9.1: Could not find artifact
>>>>> com.adobe.air.framework:airglobal:swc:20.0 in apache-release (
>>>>> https://repository.apache.org/content/repositories/releases) -> [Help
>>> 1]
>>>>> 
>>>>> 
>>>>> Additionally, the maven build caused me to have to constantly close
>>> Flash
>>>>> Player Debugger.
>>>>> 
>>>>> Any ideas why the approval script is even running maven?
>>>>> 
>>>>> Harbs
>>>>> 
>>>>>> On Feb 11, 2018, at 4:50 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>>>>>> 
>>>>>> It looks like the ant build was fine. I’m not sure what it’s doing now.
>>>>> It looks like it’s doing a maven build too? (I’m waiting for that to
>>>>> finish…)
>>>>>> 
>>>>>> I also tried installing using nom, but that failed for me.
>>>>>> 
>>>>>> I tried `sudo npm install https://dist.apache.org/repos/
>>>>> dist/dev/royale/0.9.1/rc1/binaries/apache-royale-0.9.1-bin-js-swf.tar.gz
>>> <
>>>>> https://dist.apache.org/repos/dist/dev/royale/0.9.1/ <
>>> https://dist.apache.org/repos/dist/dev/royale/0.9.1/>
>>>>> rc1/binaries/apache-royale-0.9.1-bin-js-swf.tar.gz> -g` and got this
>>>>> result:
>>>>>> https://paste.apache.org/WdR4 <https://paste.apache.org/WdR4> <
>>> https://paste.apache.org/WdR4 <https://paste.apache.org/WdR4>>
>>>>>> 
>>>>>> I’m not sure if the problem is on my end or what. Suggestions?
>>>>>> 
>>>>>> Harbs
>>>>>> 
>>>>>>> On Feb 11, 2018, at 4:25 PM, Gabe Harbs <harbs.li...@gmail.com
>>> <mailto:harbs.li...@gmail.com> >>>> harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

[Gabe Harbs]

Does this require a new rc or can the script just be updated?

> On Feb 12, 2018, at 10:08 AM, OmPrakash Muppirala <bigosma...@gmail.com> 
> wrote:
> 
> I've pushed in a fix for the broken js-swf npm installation process.
> https://github.com/apache/royale-asjs/commit/b9a1b32975cc755475ade761f36993efc8f1f058
> 
> Alex, given that this release is about npm installation (as per the
> RELEASE_NOTES), we need this fix to go in.
> 
> Sorry for the trouble :-(
> 
> Thanks,
> Om
> 
> On Sun, Feb 11, 2018 at 9:41 AM, Gabe Harbs <harbs.li...@gmail.com> wrote:
> 
>> Trying that now…
>> 
>>> On Feb 11, 2018, at 5:09 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com>
>> wrote:
>>> 
>>> In the previous release approval script also runs Maven :) You can
>> manually
>>> copy playerglobal.swc 20.0 to the following location [1]. - That is an
>>> workaround.
>>> 
>>> [1] .m2\repository\com\adobe\flash\framework\playerglobal\20.0\
>>> 
>>> 2018-02-11 16:00 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com > harbs.li...@gmail.com>>:
>>> 
>>>> Ah. Foo… :-(
>>>> 
>>>> The maven build failed on Core (after more than 30 minutes):
>>>> 
>>>> [ERROR] Failed to execute goal org.apache.royale.compiler:
>>>> royale-maven-plugin:0.9.1:compile-as (default-compile-as) on project
>>>> Core: Could not resolve dependencies for project
>>>> org.apache.royale.framework:Core:swc:0.9.1: Could not find artifact
>>>> com.adobe.air.framework:airglobal:swc:20.0 in apache-release (
>>>> https://repository.apache.org/content/repositories/releases) -> [Help
>> 1]
>>>> 
>>>> 
>>>> Additionally, the maven build caused me to have to constantly close
>> Flash
>>>> Player Debugger.
>>>> 
>>>> Any ideas why the approval script is even running maven?
>>>> 
>>>> Harbs
>>>> 
>>>>> On Feb 11, 2018, at 4:50 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>>>>> 
>>>>> It looks like the ant build was fine. I’m not sure what it’s doing now.
>>>> It looks like it’s doing a maven build too? (I’m waiting for that to
>>>> finish…)
>>>>> 
>>>>> I also tried installing using nom, but that failed for me.
>>>>> 
>>>>> I tried `sudo npm install https://dist.apache.org/repos/
>>>> dist/dev/royale/0.9.1/rc1/binaries/apache-royale-0.9.1-bin-js-swf.tar.gz
>> <
>>>> https://dist.apache.org/repos/dist/dev/royale/0.9.1/ <
>> https://dist.apache.org/repos/dist/dev/royale/0.9.1/>
>>>> rc1/binaries/apache-royale-0.9.1-bin-js-swf.tar.gz> -g` and got this
>>>> result:
>>>>> https://paste.apache.org/WdR4 <https://paste.apache.org/WdR4> <
>> https://paste.apache.org/WdR4 <https://paste.apache.org/WdR4>>
>>>>> 
>>>>> I’m not sure if the problem is on my end or what. Suggestions?
>>>>> 
>>>>> Harbs
>>>>> 
>>>>>> On Feb 11, 2018, at 4:25 PM, Gabe Harbs <harbs.li...@gmail.com
>> <mailto:harbs.li...@gmail.com> >>> harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>> wrote:
>>>>>> 
>>>>>> It finished building and then failed while building the examples
>>>> because I didn’t have maven installed on my machine. I just installed
>> maven
>>>> and I’m trying again…
>>>>>> 
>>>>>> Harbs
>>>>>> 
>>>>>>> On Feb 11, 2018, at 4:23 PM, Gabe Harbs <harbs.li...@gmail.com
>> <mailto:harbs.li...@gmail.com>
>>>> <mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>> wrote:
>>>>>>> 
>>>>>>> I got it to run when I ran the script a second time (after cleaning
>>>> out the folder with the approval script).
>>>>>>> 
>>>>>>>> On Feb 11, 2018, at 3:24 PM, Piotr Zarzycki <
>>>> piotrzarzyck...@gmail.com <mailto:piotrzarzyck...@gmail.com> > piotrzarzyck...@gmail.com <mailto:piotrzarzyck...@gmail.com>>> wrote:
>>>>>>>> 
>>>>>>>> Unfortunately I have also problems with my newest Windows
>>>> installation. :/
>>>>>>>> Anyone experience earlier such things ?
>>>>>>>> 
>>>>>>>> rat

Re: [VOTE] Release Apache Royale 0.9.1 RC1

[Gabe Harbs]

I will wait to cast my vote for that.

> On Feb 12, 2018, at 9:57 AM, OmPrakash Muppirala  wrote:
> 
> js-swf npm package seems to have a bug.  I will check in a fix to 0.9.1
> branch soon.

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

[Gabe Harbs]

Trying that now…

> On Feb 11, 2018, at 5:09 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com> wrote:
> 
> In the previous release approval script also runs Maven :) You can manually
> copy playerglobal.swc 20.0 to the following location [1]. - That is an
> workaround.
> 
> [1] .m2\repository\com\adobe\flash\framework\playerglobal\20.0\
> 
> 2018-02-11 16:00 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com 
> <mailto:harbs.li...@gmail.com>>:
> 
>> Ah. Foo… :-(
>> 
>> The maven build failed on Core (after more than 30 minutes):
>> 
>> [ERROR] Failed to execute goal org.apache.royale.compiler:
>> royale-maven-plugin:0.9.1:compile-as (default-compile-as) on project
>> Core: Could not resolve dependencies for project
>> org.apache.royale.framework:Core:swc:0.9.1: Could not find artifact
>> com.adobe.air.framework:airglobal:swc:20.0 in apache-release (
>> https://repository.apache.org/content/repositories/releases) -> [Help 1]
>> 
>> 
>> Additionally, the maven build caused me to have to constantly close Flash
>> Player Debugger.
>> 
>> Any ideas why the approval script is even running maven?
>> 
>> Harbs
>> 
>>> On Feb 11, 2018, at 4:50 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>>> 
>>> It looks like the ant build was fine. I’m not sure what it’s doing now.
>> It looks like it’s doing a maven build too? (I’m waiting for that to
>> finish…)
>>> 
>>> I also tried installing using nom, but that failed for me.
>>> 
>>> I tried `sudo npm install https://dist.apache.org/repos/
>> dist/dev/royale/0.9.1/rc1/binaries/apache-royale-0.9.1-bin-js-swf.tar.gz <
>> https://dist.apache.org/repos/dist/dev/royale/0.9.1/ 
>> <https://dist.apache.org/repos/dist/dev/royale/0.9.1/>
>> rc1/binaries/apache-royale-0.9.1-bin-js-swf.tar.gz> -g` and got this
>> result:
>>> https://paste.apache.org/WdR4 <https://paste.apache.org/WdR4> 
>>> <https://paste.apache.org/WdR4 <https://paste.apache.org/WdR4>>
>>> 
>>> I’m not sure if the problem is on my end or what. Suggestions?
>>> 
>>> Harbs
>>> 
>>>> On Feb 11, 2018, at 4:25 PM, Gabe Harbs <harbs.li...@gmail.com 
>>>> <mailto:harbs.li...@gmail.com> > harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>> wrote:
>>>> 
>>>> It finished building and then failed while building the examples
>> because I didn’t have maven installed on my machine. I just installed maven
>> and I’m trying again…
>>>> 
>>>> Harbs
>>>> 
>>>>> On Feb 11, 2018, at 4:23 PM, Gabe Harbs <harbs.li...@gmail.com 
>>>>> <mailto:harbs.li...@gmail.com>
>> <mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>> wrote:
>>>>> 
>>>>> I got it to run when I ran the script a second time (after cleaning
>> out the folder with the approval script).
>>>>> 
>>>>>> On Feb 11, 2018, at 3:24 PM, Piotr Zarzycki <
>> piotrzarzyck...@gmail.com <mailto:piotrzarzyck...@gmail.com> 
>> <mailto:piotrzarzyck...@gmail.com <mailto:piotrzarzyck...@gmail.com>>> wrote:
>>>>>> 
>>>>>> Unfortunately I have also problems with my newest Windows
>> installation. :/
>>>>>> Anyone experience earlier such things ?
>>>>>> 
>>>>>> rat-check:
>>>>>> Checking files at D:\Work\royale_vote/apache-royale-0.9.1-src,
>> report is
>>>>>> D:\Work\royale_vote/rat-report-src.txt
>>>>>> 
>>>>>> BUILD FAILED
>>>>>> D:\Work\royale_vote\ApproveRoyale.xml:352: The following error
>> occurred
>>>>>> while executing this line:
>>>>>> jar:file:/C:/ant/lib/apache-rat-tasks-0.11.jar!/org/
>> apache/rat/anttasks/antlib.xml:24:
>>>>>> taskdef A class needed by class org.apache.rat.anttasks.Report cannot
>> be
>>>>>> found: org/apache/rat/analysis/IHeaderMatcher
>>>>>> using the classloader AntClassLoader[]
>>>>>> 
>>>>>> Thanks, Piotr
>>>>>> 
>>>>>> 2018-02-11 12:10 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com 
>>>>>> <mailto:harbs.li...@gmail.com> > harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>>:
>>>>>> 
>>>>>>> I’m having some trouble with ant on my new machine.
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

[Gabe Harbs]

Ah. Foo… :-(

The maven build failed on Core (after more than 30 minutes):

[ERROR] Failed to execute goal 
org.apache.royale.compiler:royale-maven-plugin:0.9.1:compile-as 
(default-compile-as) on project Core: Could not resolve dependencies for 
project org.apache.royale.framework:Core:swc:0.9.1: Could not find artifact 
com.adobe.air.framework:airglobal:swc:20.0 in apache-release 
(https://repository.apache.org/content/repositories/releases) -> [Help 1]


Additionally, the maven build caused me to have to constantly close Flash 
Player Debugger.

Any ideas why the approval script is even running maven?

Harbs

> On Feb 11, 2018, at 4:50 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
> 
> It looks like the ant build was fine. I’m not sure what it’s doing now. It 
> looks like it’s doing a maven build too? (I’m waiting for that to finish…)
> 
> I also tried installing using nom, but that failed for me.
> 
> I tried `sudo npm install 
> https://dist.apache.org/repos/dist/dev/royale/0.9.1/rc1/binaries/apache-royale-0.9.1-bin-js-swf.tar.gz
>  
> <https://dist.apache.org/repos/dist/dev/royale/0.9.1/rc1/binaries/apache-royale-0.9.1-bin-js-swf.tar.gz>
>  -g` and got this result:
> https://paste.apache.org/WdR4 <https://paste.apache.org/WdR4>
> 
> I’m not sure if the problem is on my end or what. Suggestions?
> 
> Harbs
> 
>> On Feb 11, 2018, at 4:25 PM, Gabe Harbs <harbs.li...@gmail.com 
>> <mailto:harbs.li...@gmail.com>> wrote:
>> 
>> It finished building and then failed while building the examples because I 
>> didn’t have maven installed on my machine. I just installed maven and I’m 
>> trying again…
>> 
>> Harbs
>> 
>>> On Feb 11, 2018, at 4:23 PM, Gabe Harbs <harbs.li...@gmail.com 
>>> <mailto:harbs.li...@gmail.com>> wrote:
>>> 
>>> I got it to run when I ran the script a second time (after cleaning out the 
>>> folder with the approval script).
>>> 
>>>> On Feb 11, 2018, at 3:24 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com 
>>>> <mailto:piotrzarzyck...@gmail.com>> wrote:
>>>> 
>>>> Unfortunately I have also problems with my newest Windows installation. :/
>>>> Anyone experience earlier such things ?
>>>> 
>>>> rat-check:
>>>> Checking files at D:\Work\royale_vote/apache-royale-0.9.1-src, report is
>>>> D:\Work\royale_vote/rat-report-src.txt
>>>> 
>>>> BUILD FAILED
>>>> D:\Work\royale_vote\ApproveRoyale.xml:352: The following error occurred
>>>> while executing this line:
>>>> jar:file:/C:/ant/lib/apache-rat-tasks-0.11.jar!/org/apache/rat/anttasks/antlib.xml:24:
>>>> taskdef A class needed by class org.apache.rat.anttasks.Report cannot be
>>>> found: org/apache/rat/analysis/IHeaderMatcher
>>>> using the classloader AntClassLoader[]
>>>> 
>>>> Thanks, Piotr
>>>> 
>>>> 2018-02-11 12:10 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com 
>>>> <mailto:harbs.li...@gmail.com>>:
>>>> 
>>>>> I’m having some trouble with ant on my new machine.
>>>>> 
>>>>> I had installed ant using Homebrew, and the approval script complained
>>>>> that ANT_HOME was not defined. I tried setting it to the home-brew
>>>>> installed location and that didn’t work.
>>>>> 
>>>>> I removed the homebrew installation and installed ant manually and added
>>>>> ANT_HOME to my .profile file. That worked to get things to compile until I
>>>>> got to the rat check. The I got an error:
>>>>> 
>>>>> /Users/harbs/Documents/approve_royale/0.9.1/ApproveRoyale.xml:352:
>>>>> Problem: failed to create task or type antlib:org.apache.rat.
>>>>> anttasks:report
>>>>> Cause: The name is undefined.
>>>>> Action: Check the spelling.
>>>>> Action: Check that any custom tasks/types have been declared.
>>>>> Action: Check that any / declarations have taken
>>>>> place.
>>>>> No types or tasks have been defined in this namespace yet
>>>>> 
>>>>> This appears to be an antlib declaration.
>>>>> Action: Check that the implementing library exists in one of:
>>>>>  -/usr/local/apache-ant-1.10.2/lib
>>>>>  -/Users/harbs/.ant/lib
>>>>>  -a directory added on the command line with the -lib argument
>>>>> 
>>>>> 
>>>>> Suggestions on a better setup?
>>>>> 
>>>>> Harbs
>>>>> 
>>>>>> On Feb 9, 2018, at 11:17 AM, Gabe Harbs <harbs.li...@gmail.com 
>>>>>> <mailto:harbs.li...@gmail.com>> wrote:
>>>>>> 
>>>>>> I’m recovering from pneumonia. I’ll try to check the release on Sunday.
>>>>>> 
>>>>>> Harbs
>>>>>> 
>>>>>>> On Feb 8, 2018, at 9:58 PM, Alex Harui <aha...@adobe.com.INVALID 
>>>>>>> <mailto:aha...@adobe.com.INVALID>>
>>>>> wrote:
>>>>>>> 
>>>>>>> This is the discussion thread.
>>>>>>> 
>>>>>>> Thanks,
>>>>>>> Alex Harui
>>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> 
>>>> Piotr Zarzycki
>>>> 
>>>> Patreon: *https://www.patreon.com/piotrzarzycki 
>>>> <https://www.patreon.com/piotrzarzycki>
>>>> <https://www.patreon.com/piotrzarzycki 
>>>> <https://www.patreon.com/piotrzarzycki>>*
>>> 
>> 
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

[Gabe Harbs]

It looks like the ant build was fine. I’m not sure what it’s doing now. It 
looks like it’s doing a maven build too? (I’m waiting for that to finish…)

I also tried installing using nom, but that failed for me.

I tried `sudo npm install 
https://dist.apache.org/repos/dist/dev/royale/0.9.1/rc1/binaries/apache-royale-0.9.1-bin-js-swf.tar.gz
 -g` and got this result:
https://paste.apache.org/WdR4 <https://paste.apache.org/WdR4>

I’m not sure if the problem is on my end or what. Suggestions?

Harbs

> On Feb 11, 2018, at 4:25 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
> 
> It finished building and then failed while building the examples because I 
> didn’t have maven installed on my machine. I just installed maven and I’m 
> trying again…
> 
> Harbs
> 
>> On Feb 11, 2018, at 4:23 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>> 
>> I got it to run when I ran the script a second time (after cleaning out the 
>> folder with the approval script).
>> 
>>> On Feb 11, 2018, at 3:24 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com> 
>>> wrote:
>>> 
>>> Unfortunately I have also problems with my newest Windows installation. :/
>>> Anyone experience earlier such things ?
>>> 
>>> rat-check:
>>> Checking files at D:\Work\royale_vote/apache-royale-0.9.1-src, report is
>>> D:\Work\royale_vote/rat-report-src.txt
>>> 
>>> BUILD FAILED
>>> D:\Work\royale_vote\ApproveRoyale.xml:352: The following error occurred
>>> while executing this line:
>>> jar:file:/C:/ant/lib/apache-rat-tasks-0.11.jar!/org/apache/rat/anttasks/antlib.xml:24:
>>> taskdef A class needed by class org.apache.rat.anttasks.Report cannot be
>>> found: org/apache/rat/analysis/IHeaderMatcher
>>> using the classloader AntClassLoader[]
>>> 
>>> Thanks, Piotr
>>> 
>>> 2018-02-11 12:10 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
>>> 
>>>> I’m having some trouble with ant on my new machine.
>>>> 
>>>> I had installed ant using Homebrew, and the approval script complained
>>>> that ANT_HOME was not defined. I tried setting it to the home-brew
>>>> installed location and that didn’t work.
>>>> 
>>>> I removed the homebrew installation and installed ant manually and added
>>>> ANT_HOME to my .profile file. That worked to get things to compile until I
>>>> got to the rat check. The I got an error:
>>>> 
>>>> /Users/harbs/Documents/approve_royale/0.9.1/ApproveRoyale.xml:352:
>>>> Problem: failed to create task or type antlib:org.apache.rat.
>>>> anttasks:report
>>>> Cause: The name is undefined.
>>>> Action: Check the spelling.
>>>> Action: Check that any custom tasks/types have been declared.
>>>> Action: Check that any / declarations have taken
>>>> place.
>>>> No types or tasks have been defined in this namespace yet
>>>> 
>>>> This appears to be an antlib declaration.
>>>> Action: Check that the implementing library exists in one of:
>>>>  -/usr/local/apache-ant-1.10.2/lib
>>>>  -/Users/harbs/.ant/lib
>>>>  -a directory added on the command line with the -lib argument
>>>> 
>>>> 
>>>> Suggestions on a better setup?
>>>> 
>>>> Harbs
>>>> 
>>>>> On Feb 9, 2018, at 11:17 AM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>>>>> 
>>>>> I’m recovering from pneumonia. I’ll try to check the release on Sunday.
>>>>> 
>>>>> Harbs
>>>>> 
>>>>>> On Feb 8, 2018, at 9:58 PM, Alex Harui <aha...@adobe.com.INVALID>
>>>> wrote:
>>>>>> 
>>>>>> This is the discussion thread.
>>>>>> 
>>>>>> Thanks,
>>>>>> Alex Harui
>>>>>> 
>>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> -- 
>>> 
>>> Piotr Zarzycki
>>> 
>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>> <https://www.patreon.com/piotrzarzycki>*
>> 
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

[Gabe Harbs]

It finished building and then failed while building the examples because I 
didn’t have maven installed on my machine. I just installed maven and I’m 
trying again…

Harbs

> On Feb 11, 2018, at 4:23 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
> 
> I got it to run when I ran the script a second time (after cleaning out the 
> folder with the approval script).
> 
>> On Feb 11, 2018, at 3:24 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com> 
>> wrote:
>> 
>> Unfortunately I have also problems with my newest Windows installation. :/
>> Anyone experience earlier such things ?
>> 
>> rat-check:
>> Checking files at D:\Work\royale_vote/apache-royale-0.9.1-src, report is
>> D:\Work\royale_vote/rat-report-src.txt
>> 
>> BUILD FAILED
>> D:\Work\royale_vote\ApproveRoyale.xml:352: The following error occurred
>> while executing this line:
>> jar:file:/C:/ant/lib/apache-rat-tasks-0.11.jar!/org/apache/rat/anttasks/antlib.xml:24:
>> taskdef A class needed by class org.apache.rat.anttasks.Report cannot be
>> found: org/apache/rat/analysis/IHeaderMatcher
>> using the classloader AntClassLoader[]
>> 
>> Thanks, Piotr
>> 
>> 2018-02-11 12:10 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
>> 
>>> I’m having some trouble with ant on my new machine.
>>> 
>>> I had installed ant using Homebrew, and the approval script complained
>>> that ANT_HOME was not defined. I tried setting it to the home-brew
>>> installed location and that didn’t work.
>>> 
>>> I removed the homebrew installation and installed ant manually and added
>>> ANT_HOME to my .profile file. That worked to get things to compile until I
>>> got to the rat check. The I got an error:
>>> 
>>> /Users/harbs/Documents/approve_royale/0.9.1/ApproveRoyale.xml:352:
>>> Problem: failed to create task or type antlib:org.apache.rat.
>>> anttasks:report
>>> Cause: The name is undefined.
>>> Action: Check the spelling.
>>> Action: Check that any custom tasks/types have been declared.
>>> Action: Check that any / declarations have taken
>>> place.
>>> No types or tasks have been defined in this namespace yet
>>> 
>>> This appears to be an antlib declaration.
>>> Action: Check that the implementing library exists in one of:
>>>   -/usr/local/apache-ant-1.10.2/lib
>>>   -/Users/harbs/.ant/lib
>>>   -a directory added on the command line with the -lib argument
>>> 
>>> 
>>> Suggestions on a better setup?
>>> 
>>> Harbs
>>> 
>>>> On Feb 9, 2018, at 11:17 AM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>>>> 
>>>> I’m recovering from pneumonia. I’ll try to check the release on Sunday.
>>>> 
>>>> Harbs
>>>> 
>>>>> On Feb 8, 2018, at 9:58 PM, Alex Harui <aha...@adobe.com.INVALID>
>>> wrote:
>>>>> 
>>>>> This is the discussion thread.
>>>>> 
>>>>> Thanks,
>>>>> Alex Harui
>>>>> 
>>>> 
>>> 
>>> 
>> 
>> 
>> -- 
>> 
>> Piotr Zarzycki
>> 
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> <https://www.patreon.com/piotrzarzycki>*
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

[Gabe Harbs]

I got it to run when I ran the script a second time (after cleaning out the 
folder with the approval script).

> On Feb 11, 2018, at 3:24 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com> wrote:
> 
> Unfortunately I have also problems with my newest Windows installation. :/
> Anyone experience earlier such things ?
> 
> rat-check:
> Checking files at D:\Work\royale_vote/apache-royale-0.9.1-src, report is
> D:\Work\royale_vote/rat-report-src.txt
> 
> BUILD FAILED
> D:\Work\royale_vote\ApproveRoyale.xml:352: The following error occurred
> while executing this line:
> jar:file:/C:/ant/lib/apache-rat-tasks-0.11.jar!/org/apache/rat/anttasks/antlib.xml:24:
> taskdef A class needed by class org.apache.rat.anttasks.Report cannot be
> found: org/apache/rat/analysis/IHeaderMatcher
> using the classloader AntClassLoader[]
> 
> Thanks, Piotr
> 
> 2018-02-11 12:10 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
> 
>> I’m having some trouble with ant on my new machine.
>> 
>> I had installed ant using Homebrew, and the approval script complained
>> that ANT_HOME was not defined. I tried setting it to the home-brew
>> installed location and that didn’t work.
>> 
>> I removed the homebrew installation and installed ant manually and added
>> ANT_HOME to my .profile file. That worked to get things to compile until I
>> got to the rat check. The I got an error:
>> 
>> /Users/harbs/Documents/approve_royale/0.9.1/ApproveRoyale.xml:352:
>> Problem: failed to create task or type antlib:org.apache.rat.
>> anttasks:report
>> Cause: The name is undefined.
>> Action: Check the spelling.
>> Action: Check that any custom tasks/types have been declared.
>> Action: Check that any / declarations have taken
>> place.
>> No types or tasks have been defined in this namespace yet
>> 
>> This appears to be an antlib declaration.
>> Action: Check that the implementing library exists in one of:
>>-/usr/local/apache-ant-1.10.2/lib
>>-/Users/harbs/.ant/lib
>>-a directory added on the command line with the -lib argument
>> 
>> 
>> Suggestions on a better setup?
>> 
>> Harbs
>> 
>>> On Feb 9, 2018, at 11:17 AM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>>> 
>>> I’m recovering from pneumonia. I’ll try to check the release on Sunday.
>>> 
>>> Harbs
>>> 
>>>> On Feb 8, 2018, at 9:58 PM, Alex Harui <aha...@adobe.com.INVALID>
>> wrote:
>>>> 
>>>> This is the discussion thread.
>>>> 
>>>> Thanks,
>>>> Alex Harui
>>>> 
>>> 
>> 
>> 
> 
> 
> -- 
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*

Re: vars in CSS

[Gabe Harbs]

No. I think it was the “>” operator which didn’t work, but I don’t remember for 
sure.

> On Feb 11, 2018, at 1:53 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com> wrote:
> 
> Hi Harbs,
> 
> Are you saying that without this namespace following situation didn't work?
> 
> .myCss {
> }
> 
> .myCss .newCss {
> }
> 
> Thanks,
> Piotr
> 
> On Sun, Feb 11, 2018, 10:27 Gabe Harbs <harbs.li...@gmail.com> wrote:
> 
>> If it could work on Express, even better, but my impression was that the
>> structure was going to have to change pretty significantly in some cases to
>> get the theming to work.
>> 
>> Harbs
>> 
>>> On Feb 11, 2018, at 11:23 AM, Carlos Rovira <carlosrov...@apache.org>
>> wrote:
>>> 
>>> Hi,
>>> 
>>> I think CSS vars would be a good addition although IE still doesn't
>> handle
>>> it.
>>> 
>>> But in the other hand the Alex proposal seems to fit perfectly with what
>> I
>>> want to do.
>>> 
>>> I didn't know that we have "-theme=" compiler option, and I think I will
>>> use that extensively
>>> 
>>> My last thought about all of this is if I should make this work on
>> Express
>>> instead of creating a complete new UI set (Vivid)
>>> 
>>> thanks!
>>> 
>>> 
>>> 
>>> 2018-02-11 9:53 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
>>> 
>>>> I don’t remember the details, but I’ve had css which would not compile
>>>> until I specified the html namespace. It might have been using descender
>>>> selectors. Not sure.
>>>> 
>>>> Harbs
>>>> 
>>>>> On Feb 11, 2018, at 9:20 AM, Alex Harui <aha...@adobe.com.INVALID>
>>>> wrote:
>>>>> 
>>>>> I'm not clear how namespace would help.
>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>> 
>> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

[Gabe Harbs]

I’m having some trouble with ant on my new machine.

I had installed ant using Homebrew, and the approval script complained that 
ANT_HOME was not defined. I tried setting it to the home-brew installed 
location and that didn’t work.

I removed the homebrew installation and installed ant manually and added 
ANT_HOME to my .profile file. That worked to get things to compile until I got 
to the rat check. The I got an error:

/Users/harbs/Documents/approve_royale/0.9.1/ApproveRoyale.xml:352: Problem: 
failed to create task or type antlib:org.apache.rat.anttasks:report
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any / declarations have taken place.
No types or tasks have been defined in this namespace yet

This appears to be an antlib declaration. 
Action: Check that the implementing library exists in one of:
-/usr/local/apache-ant-1.10.2/lib
-/Users/harbs/.ant/lib
-a directory added on the command line with the -lib argument


Suggestions on a better setup?

Harbs

> On Feb 9, 2018, at 11:17 AM, Gabe Harbs <harbs.li...@gmail.com> wrote:
> 
> I’m recovering from pneumonia. I’ll try to check the release on Sunday.
> 
> Harbs
> 
>> On Feb 8, 2018, at 9:58 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
>> 
>> This is the discussion thread.
>> 
>> Thanks,
>> Alex Harui
>> 
> 

Re: vars in CSS

[Gabe Harbs]

If it could work on Express, even better, but my impression was that the 
structure was going to have to change pretty significantly in some cases to get 
the theming to work.

Harbs

> On Feb 11, 2018, at 11:23 AM, Carlos Rovira <carlosrov...@apache.org> wrote:
> 
> Hi,
> 
> I think CSS vars would be a good addition although IE still doesn't handle
> it.
> 
> But in the other hand the Alex proposal seems to fit perfectly with what I
> want to do.
> 
> I didn't know that we have "-theme=" compiler option, and I think I will
> use that extensively
> 
> My last thought about all of this is if I should make this work on Express
> instead of creating a complete new UI set (Vivid)
> 
> thanks!
> 
> 
> 
> 2018-02-11 9:53 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
> 
>> I don’t remember the details, but I’ve had css which would not compile
>> until I specified the html namespace. It might have been using descender
>> selectors. Not sure.
>> 
>> Harbs
>> 
>>> On Feb 11, 2018, at 9:20 AM, Alex Harui <aha...@adobe.com.INVALID>
>> wrote:
>>> 
>>> I'm not clear how namespace would help.
>> 
>> 
> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: vars in CSS

[Gabe Harbs]

I don’t remember the details, but I’ve had css which would not compile until I 
specified the html namespace. It might have been using descender selectors. Not 
sure.

Harbs

> On Feb 11, 2018, at 9:20 AM, Alex Harui  wrote:
> 
> I'm not clear how namespace would help.

Re: New UI Set

[Gabe Harbs]

+1

> On Feb 11, 2018, at 9:11 AM, Alex Harui  wrote:
> 
> One goal for 0.9.2 is to get rid of the "*" selector in Basic's
> defaults.css.  And anything else that has "global" impact.  So I recommend
> making any decision about extend or copy regarding other logistics.  IMO,
> you sort of want to do what Express did. New namespace, lots of components
> simply subclass the Basic ones and add functionality.  Then we'll see what
> actually needs to be done to get the results you want.
> 
> My 2 cents,
> -Alex
> 
> On 2/10/18, 10:03 AM, "Piotr Zarzycki"  > wrote:
> 
>> Maybe there is other way for exclusion thank at the compilation stage of
>> application. Maybe you can exclude styles on the compilation stage of swc
>> itself.
>> 
>> 2018-02-10 19:01 GMT+01:00 Piotr Zarzycki :
>> 
>>> Hi Carlos,
>>> 
>>> I think you should extend and exclude for that controls Basic.css - you
>>> are ready to go. It doesn't make sense to me copy all the code. Let's
>>> see
>>> how others see that.
>>> 
>>> Thanks,
>>> Piotr
>>> 
>>> 2018-02-10 18:52 GMT+01:00 Carlos Rovira :
>>> 
 Hi,
 
 I remember talking about the new UI Set that has the focus and "how it
 looks".
 People vote for a complete new UI set instead of tweak existing ones
 (Basic
 or Express)
 I called new set Vivid for now
 
 So I started this journey and I started copy & paste controls like
 Button,
 TextInput or Slider and from Basic and then tweak
 I was doing in this way so changes in Basic doesn't affect Vivid
 controls.
 
 What do you think about it? I should extend for example Basic Button
 instead make a complete new component or viceversa?
 
 --
 Carlos Rovira
 
 https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me 
 
 %2Fcarlosrovira=02%7C01%7Caharui%40adobe.com 
 %7Ce850976812e149a411a2
 08d570b08ece%7C71f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%7C63653882605269
 5877=7lcd4XB26Tzbaj2XybgYYZLCeFhmJMDtVr2ClYZQxiY%3D=0
 
>>> 
>>> 
>>> 
>>> --
>>> 
>>> Piotr Zarzycki
>>> 
>>> Patreon: 
>>> *https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.pat 
>>> 
>>> reon.com 
>>> %2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com 
>>> %7Ce850976812e1
>>> 49a411a208d570b08ece%7C71f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%7C6365388
>>> 26052695877=BdgDeIFmGByN3nQa0aREZI2OkNXuGKCpsDRz08xdCBo%3D
>>> =0
>>> 
>>> >> 
>>> reon.com 
>>> %2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com 
>>> %7Ce850976812e1
>>> 49a411a208d570b08ece%7C71f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%7C6365388
>>> 26052695877=BdgDeIFmGByN3nQa0aREZI2OkNXuGKCpsDRz08xdCBo%3D
>>> =0>*
>>> 
>> 
>> 
>> 
>> -- 
>> 
>> Piotr Zarzycki
>> 
>> Patreon: 
>> *https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patr 
>> 
>> eon.com %2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com 
>> %7Ce850976812e149
>> a411a208d570b08ece%7C71f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%7C6365388260
>> 52695877=BdgDeIFmGByN3nQa0aREZI2OkNXuGKCpsDRz08xdCBo%3D=0
>> > 
>> eon.com %2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com 
>> %7Ce850976812e149
>> a411a208d570b08ece%7C71f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%7C6365388260
>> 52695877=BdgDeIFmGByN3nQa0aREZI2OkNXuGKCpsDRz08xdCBo%3D=0>*

Re: vars in CSS

[Gabe Harbs]

BTW, CSS vars is not supported in IE:
https://caniuse.com/#feat=css-variables 


> On Feb 10, 2018, at 8:26 PM, Carlos Rovira  wrote:
> 
> Hi
> 
> I'm figuring how to configure easy colors in CSS in a reusable way.
> 
> I get to CSS vars:
> 
> https://developer.mozilla.org/es/docs/Web/CSS/Using_CSS_variables
> 
> but something like the basic example described in that CSS makes the
> compiler breaks:
> 
> java.util.NoSuchElementException: can't look backwards more than one token
> in this stream org.antlr.runtime.misc.LookaheadStream.LB
> (LookaheadStream.java:159)org.antlr.runtime.misc.LookaheadStream.LT(LookaheadStream.java:120)org.antlr.runtime.RecognitionException.extractInformationFromTreeNodeStream(RecognitionException.java:144)org.antlr.runtime.RecognitionException.(RecognitionException.java:111)org.antlr.runtime.MismatchedTreeNodeException.(MismatchedTreeNodeException.java:42)org.antlr.runtime.tree.TreeParser.recoverFromMismatchedToken(TreeParser.java:135)org.antlr.runtime.BaseRecognizer.match(BaseRecognizer.java:115)org.apache.royale.compiler.internal.css.CSSTree.declarationsBlock(CSSTree.java:1725)org.apache.royale.compiler.internal.css.CSSTree.ruleset(CSSTree.java:786)org.apache.royale.compiler.internal.css.CSSTree.stylesheet(CSSTree.java:289)org.apache.royale.compiler.internal.css.CSSDocument.parse(CSSDocument.java:81)org.apache.royale.compiler.internal.caches.CSSDocumentCache$CSSDocumentCacheKey.parse(CSSDocumentCache.java:251)org.apache.royale.compiler.internal.caches.CSSDocumentCache.createEntryValue(CSSDocumentCache.java:337)org.apache.royale.compiler.internal.caches.CSSDocumentCache.createEntryValue(CSSDocumentCache.java:55)org.apache.royale.compiler.internal.caches.ConcurrentCacheStoreBase.get(ConcurrentCacheStoreBase.java:69)org.apache.royale.compiler.internal.caches.CSSDocumentCache.getDefaultsCSS(CSSDocumentCache.java:381)org.apache.royale.compiler.internal.css.CSSManager.getDefaultCSS(CSSManager.java:182)org.apache.royale.compiler.internal.targets.RoyaleJSTarget.getAllDefaultCSS(RoyaleJSTarget.java:289)org.apache.royale.compiler.internal.targets.RoyaleJSTarget.findAllCompilationUnitsToLink(RoyaleJSTarget.java:195)org.apache.royale.compiler.internal.targets.Target.buildAllCompilationUnits(Target.java:297)org.apache.royale.compiler.internal.targets.Target.getBuiltCompilationUnitSet(Target.java:306)org.apache.royale.compiler.internal.targets.JSTarget.buildAndCollectProblems(JSTarget.java:186)org.apache.royale.compiler.internal.targets.JSTarget.build(JSTarget.java:114)org.apache.royale.compiler.internal.targets.JSTarget.build(JSTarget.java:226)org.apache.royale.compiler.clients.MXMLJSCRoyale.buildApplication(MXMLJSCRoyale.java:455)org.apache.royale.compiler.clients.MXMLJSCRoyale.buildJSTarget(MXMLJSCRoyale.java:420)org.apache.royale.compiler.clients.MXMLJSCRoyale.buildArtifact(MXMLJSCRoyale.java:411)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:308)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:240)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:197)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:343)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:279)org.apache.royale.compiler.clients.MXMLJSC.execute(MXMLJSC.java:210)org.apache.royale.maven.BaseMojo.execute(BaseMojo.java:302)org.apache.royale.maven.CompileAppMojo.execute(CompileAppMojo.java:107)org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)org.apache.maven.cli.MavenCli.main(MavenCli.java:191)sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> 

Re: vars in CSS

[Gabe Harbs]

Try using @namespace "http://www.w3.org/1999/xhtml”;

> On Feb 10, 2018, at 8:26 PM, Carlos Rovira  wrote:
> 
> Hi
> 
> I'm figuring how to configure easy colors in CSS in a reusable way.
> 
> I get to CSS vars:
> 
> https://developer.mozilla.org/es/docs/Web/CSS/Using_CSS_variables
> 
> but something like the basic example described in that CSS makes the
> compiler breaks:
> 
> java.util.NoSuchElementException: can't look backwards more than one token
> in this stream org.antlr.runtime.misc.LookaheadStream.LB
> (LookaheadStream.java:159)org.antlr.runtime.misc.LookaheadStream.LT(LookaheadStream.java:120)org.antlr.runtime.RecognitionException.extractInformationFromTreeNodeStream(RecognitionException.java:144)org.antlr.runtime.RecognitionException.(RecognitionException.java:111)org.antlr.runtime.MismatchedTreeNodeException.(MismatchedTreeNodeException.java:42)org.antlr.runtime.tree.TreeParser.recoverFromMismatchedToken(TreeParser.java:135)org.antlr.runtime.BaseRecognizer.match(BaseRecognizer.java:115)org.apache.royale.compiler.internal.css.CSSTree.declarationsBlock(CSSTree.java:1725)org.apache.royale.compiler.internal.css.CSSTree.ruleset(CSSTree.java:786)org.apache.royale.compiler.internal.css.CSSTree.stylesheet(CSSTree.java:289)org.apache.royale.compiler.internal.css.CSSDocument.parse(CSSDocument.java:81)org.apache.royale.compiler.internal.caches.CSSDocumentCache$CSSDocumentCacheKey.parse(CSSDocumentCache.java:251)org.apache.royale.compiler.internal.caches.CSSDocumentCache.createEntryValue(CSSDocumentCache.java:337)org.apache.royale.compiler.internal.caches.CSSDocumentCache.createEntryValue(CSSDocumentCache.java:55)org.apache.royale.compiler.internal.caches.ConcurrentCacheStoreBase.get(ConcurrentCacheStoreBase.java:69)org.apache.royale.compiler.internal.caches.CSSDocumentCache.getDefaultsCSS(CSSDocumentCache.java:381)org.apache.royale.compiler.internal.css.CSSManager.getDefaultCSS(CSSManager.java:182)org.apache.royale.compiler.internal.targets.RoyaleJSTarget.getAllDefaultCSS(RoyaleJSTarget.java:289)org.apache.royale.compiler.internal.targets.RoyaleJSTarget.findAllCompilationUnitsToLink(RoyaleJSTarget.java:195)org.apache.royale.compiler.internal.targets.Target.buildAllCompilationUnits(Target.java:297)org.apache.royale.compiler.internal.targets.Target.getBuiltCompilationUnitSet(Target.java:306)org.apache.royale.compiler.internal.targets.JSTarget.buildAndCollectProblems(JSTarget.java:186)org.apache.royale.compiler.internal.targets.JSTarget.build(JSTarget.java:114)org.apache.royale.compiler.internal.targets.JSTarget.build(JSTarget.java:226)org.apache.royale.compiler.clients.MXMLJSCRoyale.buildApplication(MXMLJSCRoyale.java:455)org.apache.royale.compiler.clients.MXMLJSCRoyale.buildJSTarget(MXMLJSCRoyale.java:420)org.apache.royale.compiler.clients.MXMLJSCRoyale.buildArtifact(MXMLJSCRoyale.java:411)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:308)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:240)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:197)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:343)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:279)org.apache.royale.compiler.clients.MXMLJSC.execute(MXMLJSC.java:210)org.apache.royale.maven.BaseMojo.execute(BaseMojo.java:302)org.apache.royale.maven.CompileAppMojo.execute(CompileAppMojo.java:107)org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)org.apache.maven.cli.MavenCli.main(MavenCli.java:191)sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

[Gabe Harbs]

I’m recovering from pneumonia. I’ll try to check the release on Sunday.

Harbs

> On Feb 8, 2018, at 9:58 PM, Alex Harui  wrote:
> 
> This is the discussion thread.
> 
> Thanks,
> Alex Harui
> 

Re: What is x and y? What is width and height?

[Gabe Harbs]

Yes. Flexbox solves a lot of problems, and I use the “flex” layouts pretty 
extensively.

However, I have run into lots of cases which are hard to solve and the old 
Flex-style layouts would have been helpful.

> On Feb 7, 2018, at 6:34 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com> wrote:
> 
> Lately I had huge exercises with FlexBox mechanism and it is finally
> something. I have never seen better working things in HTML than this. If I
> wanted to make elements on the right they are really displays on the right.
> - Without FlexBox I would be nowhere.
> 
> Maybe it is not the answer for the constrained layout, but it is something.
> 
> Thanks,
> Piotr
> 
> 2018-02-07 17:24 GMT+01:00 Gabe Harbs <harbs.li...@gmail.com>:
> 
>> FWIW, I do think we need a “constrained layout” which places *everything*
>> absolutely and does not rely on browser layout. If that layout were to be
>> used, the bounding box values would be correct.
>> 
>>> On Feb 7, 2018, at 6:00 PM, Peter Ent <p...@adobe.com.INVALID> wrote:
>>> 
>>> I think I agree with Harbs about x,y,width,height just returning the set
>>> values if the calculation would be expensive. I wonder what the
>>> circumstances are that we actually need to have precise values in
>>> calculations. For example, if I wanted to make a circulate layout, how
>>> would I go about doing that?
>>> 
>>> In the places I've done layouts without regard to platform I'm just
>>> assuming things work. For example, in the DataGridLayout, I need to
>>> transfer the column width given on the js:DataGridColumn definition to
>>> both the List (column) and the corresponding Button in the ButtonBar.
>>> Ideally, the browser takes that (along with display and position styles)
>>> and just does the right thing with minimum code on our part (that's not
>>> actually what I'm doing, so perhaps I should rethink that one more time).
>>> 
>>> ‹peter
>>> 
>>> On 2/7/18, 8:35 AM, "Gabe Harbs" <harbs.li...@gmail.com> wrote:
>>> 
>>>> The offset values are very expensive.
>>>> 
>>>> They are also not completely accurate. I¹ve found it¹s difficult to get
>>>> accurate values where SVG and transforms are in play.
>>>> 
>>>> I would suggest that x,y,widht and height should reflect *set* values
>>>> even if they are not always the actual ones.
>>>> 
>>>> For cases where it¹s necessary to get accurate measured x,y,width and
>>>> height, I would suggest using ³measured² variations of these values, or
>>>> better, a getMeasuredBounds() method.
>>>> 
>>>>> On Feb 7, 2018, at 10:43 AM, Alex Harui <aha...@adobe.com.INVALID>
>>>>> wrote:
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> In Royale on JS, we are trying to leverage the browser's layout code as
>>>>> much as possible.  We only run our own layout code in a few places.
>>>>> In debugging a few layout issues I discovered that UIBase is not
>>>>> reporting
>>>>> x and y the way we expect it from Flex/Flash.  Browser elements don't
>>>>> have
>>>>> x and y properties, instead they have offsetLeft and offsetTop.  Mainly
>>>>> for backward-compatibility with Flex/Flash, Royale has had x and y in
>>>>> the
>>>>> API since the beginning.  I think it is a bug that x and y do not act
>>>>> like
>>>>> they do in Flex and plan to fix that after this release.  Thoughts?
>>>>> I'm a
>>>>> bit concerned of the expense of calculating x and y because you have to
>>>>> check if the offsetParent is your immediate parent and get the
>>>>> offsetLeft/offsetTop of the immediate parent, but I think that's what
>> it
>>>>> would take to fix it.
>>>>> 
>>>>> Similarly (well, sort of), Flex did not support CSS margins, only
>>>>> padding.
>>>>> The browser reports width (offsetWidth) as factoring in content,
>> padding
>>>>> and borders, but not margin.  I think that's right, and matches Flex.
>>>>> However, our custom layout algorithms do not currently factor in
>> margins
>>>>> since they are not reported in width.  I think our custom layout should
>>>>> request width and margins and do the math.  We should not change width
>>>>> to
>>>>> include margins.  Thoughts?  This will make our custom layout code a
>> bit
>>>>> more expensive as well as it will probably need to call
>>>>> getComputedStyles() on all of the children in order to get margins.
>>>>> This
>>>>> is also something to fix in the next release.
>>>>> 
>>>>> Of course, I could be wrong.  Thoughts?
>>>>> 
>>>>> -Alex
>>>>> 
>>>> 
>>> 
>> 
>> 
> 
> 
> -- 
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*

Re: What is x and y? What is width and height?

[Gabe Harbs]

FWIW, I do think we need a “constrained layout” which places *everything* 
absolutely and does not rely on browser layout. If that layout were to be used, 
the bounding box values would be correct.

> On Feb 7, 2018, at 6:00 PM, Peter Ent <p...@adobe.com.INVALID> wrote:
> 
> I think I agree with Harbs about x,y,width,height just returning the set
> values if the calculation would be expensive. I wonder what the
> circumstances are that we actually need to have precise values in
> calculations. For example, if I wanted to make a circulate layout, how
> would I go about doing that?
> 
> In the places I've done layouts without regard to platform I'm just
> assuming things work. For example, in the DataGridLayout, I need to
> transfer the column width given on the js:DataGridColumn definition to
> both the List (column) and the corresponding Button in the ButtonBar.
> Ideally, the browser takes that (along with display and position styles)
> and just does the right thing with minimum code on our part (that's not
> actually what I'm doing, so perhaps I should rethink that one more time).
> 
> ‹peter
> 
> On 2/7/18, 8:35 AM, "Gabe Harbs" <harbs.li...@gmail.com> wrote:
> 
>> The offset values are very expensive.
>> 
>> They are also not completely accurate. I¹ve found it¹s difficult to get
>> accurate values where SVG and transforms are in play.
>> 
>> I would suggest that x,y,widht and height should reflect *set* values
>> even if they are not always the actual ones.
>> 
>> For cases where it¹s necessary to get accurate measured x,y,width and
>> height, I would suggest using ³measured² variations of these values, or
>> better, a getMeasuredBounds() method.
>> 
>>> On Feb 7, 2018, at 10:43 AM, Alex Harui <aha...@adobe.com.INVALID>
>>> wrote:
>>> 
>>> Hi,
>>> 
>>> In Royale on JS, we are trying to leverage the browser's layout code as
>>> much as possible.  We only run our own layout code in a few places.
>>> In debugging a few layout issues I discovered that UIBase is not
>>> reporting
>>> x and y the way we expect it from Flex/Flash.  Browser elements don't
>>> have
>>> x and y properties, instead they have offsetLeft and offsetTop.  Mainly
>>> for backward-compatibility with Flex/Flash, Royale has had x and y in
>>> the
>>> API since the beginning.  I think it is a bug that x and y do not act
>>> like
>>> they do in Flex and plan to fix that after this release.  Thoughts?
>>> I'm a
>>> bit concerned of the expense of calculating x and y because you have to
>>> check if the offsetParent is your immediate parent and get the
>>> offsetLeft/offsetTop of the immediate parent, but I think that's what it
>>> would take to fix it.
>>> 
>>> Similarly (well, sort of), Flex did not support CSS margins, only
>>> padding.
>>> The browser reports width (offsetWidth) as factoring in content, padding
>>> and borders, but not margin.  I think that's right, and matches Flex.
>>> However, our custom layout algorithms do not currently factor in margins
>>> since they are not reported in width.  I think our custom layout should
>>> request width and margins and do the math.  We should not change width
>>> to
>>> include margins.  Thoughts?  This will make our custom layout code a bit
>>> more expensive as well as it will probably need to call
>>> getComputedStyles() on all of the children in order to get margins.
>>> This
>>> is also something to fix in the next release.
>>> 
>>> Of course, I could be wrong.  Thoughts?
>>> 
>>> -Alex
>>> 
>> 
> 

Re: What is x and y? What is width and height?

[Gabe Harbs]

The offset values are very expensive.

They are also not completely accurate. I’ve found it’s difficult to get 
accurate values where SVG and transforms are in play.

I would suggest that x,y,widht and height should reflect *set* values even if 
they are not always the actual ones.

For cases where it’s necessary to get accurate measured x,y,width and height, I 
would suggest using “measured” variations of these values, or better, a 
getMeasuredBounds() method.

> On Feb 7, 2018, at 10:43 AM, Alex Harui  wrote:
> 
> Hi,
> 
> In Royale on JS, we are trying to leverage the browser's layout code as
> much as possible.  We only run our own layout code in a few places.
> In debugging a few layout issues I discovered that UIBase is not reporting
> x and y the way we expect it from Flex/Flash.  Browser elements don't have
> x and y properties, instead they have offsetLeft and offsetTop.  Mainly
> for backward-compatibility with Flex/Flash, Royale has had x and y in the
> API since the beginning.  I think it is a bug that x and y do not act like
> they do in Flex and plan to fix that after this release.  Thoughts?  I'm a
> bit concerned of the expense of calculating x and y because you have to
> check if the offsetParent is your immediate parent and get the
> offsetLeft/offsetTop of the immediate parent, but I think that's what it
> would take to fix it.
> 
> Similarly (well, sort of), Flex did not support CSS margins, only padding.
> The browser reports width (offsetWidth) as factoring in content, padding
> and borders, but not margin.  I think that's right, and matches Flex.
> However, our custom layout algorithms do not currently factor in margins
> since they are not reported in width.  I think our custom layout should
> request width and margins and do the math.  We should not change width to
> include margins.  Thoughts?  This will make our custom layout code a bit
> more expensive as well as it will probably need to call
> getComputedStyles() on all of the children in order to get margins.  This
> is also something to fix in the next release.
> 
> Of course, I could be wrong.  Thoughts?
> 
> -Alex
> 

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

[Gabe Harbs]

I’m really not sure how you plan on going about strongly typing hierarchical 
data.

> On Feb 6, 2018, at 7:13 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
> 
> What kind of utility do you have in mind?
> 
> 
>> On Feb 6, 2018, at 7:09 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
>> 
>> Don't bother making VO's by hand for ASDoc.  Let's write a utility to
>> generate it.  It will save everyone time.  If you want to see
>> bin/js-release, change the build to not use ADVANCED_OPTIMIZATIONS for now.
>> 
>> There are lots of reasons to avoid using plain Object in a Royale app
>> other than as a hash map.  IMO, most C and Java apps don't use generic
>> untyped dynamic bags of properties.  If I add a warning about Object use,
>> there will be a directive to suppress it.  Objects are prone to error, and
>> there is some indication that runtimes work better with type information.
>> The JS runtimes wouldn't bother type inferencing otherwise.  WASM hints
>> that it wants types.
>> 
>> My 2 cents,
>> -Alex
>> 
>> On 2/6/18, 8:45 AM, "Gabe Harbs" <harbs.li...@gmail.com> wrote:
>> 
>>> Huh?
>>> 
>>> I don’t see how it’s possible to avoid Object completely. Even using VOs
>>> require constructing them from Objects when coming from outside sources.
>>> 
>>> Again: I’m not arguing against using VOs when possible/practical. I’m
>>> just arguing that use of dot notation on Objects shouldn’t blow up your
>>> app.
>>> 
>>> Right now, I’m creating VOs for the ASDoc app. It’s kind of tedious work…
>>> 
>>> Harbs
>>> 
>>>> On Feb 6, 2018, at 6:40 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
>>>> 
>>>> Good catch. I fixed that.
>>>> 
>>>> Actually, you are arguing in favor of ValueObjects.  The error was there
>>>> because commitObj was a plain Object so the compiler couldn't understand
>>>> more about it.  We want to not have any plain objects in a Royale app.
>>>> They only create potential problems.  In fact, maybe it is time for me
>>>> to
>>>> figure out how to generate warnings on every use of plain Object.
>>>> Eventually we will have typedefs for the GitHub value objects and then
>>>> there wouldn't be an issue like this.
>>>> 
>>>> Thanks for proving my point.
>>>> 
>>>> -Alex
>>>> 
>>>> On 2/6/18, 2:59 AM, "Gabe Harbs" <harbs.li...@gmail.com> wrote:
>>>> 
>>>>> To illustrate that the VO solution is also error prone, I’m pretty sure
>>>>> that this page has a mistake:
>>>>> 
>>>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapachero
>>>>> ya
>>>>> 
>>>>> leci.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyaleDocs_Staging%2Flast
>>>>> Su
>>>>> 
>>>>> ccessfulBuild%2Fartifact%2F_site%2Fcreate-an-application%2Fapplication-t
>>>>> ut
>>>>> 
>>>>> orial%2Fvalue-objects.html=02%7C01%7Caharui%40adobe.com%7C924b229e4
>>>>> 9b
>>>>> 
>>>>> b443ddbf708d56d50cd97%7C71f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%7C63653
>>>>> 51
>>>>> 
>>>>> 16172815360=e9FoFwJfNJfjmFlWF4%2FRIwCNU4R5mhEEQ9GYz70W3Ls%3D
>>>>> ve
>>>>> d=0 
>>>>> 
>>>>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacher
>>>>> oy
>>>>> 
>>>>> aleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyaleDocs_Staging%2Flas
>>>>> tS
>>>>> 
>>>>> uccessfulBuild%2Fartifact%2F_site%2Fcreate-an-application%2Fapplication-
>>>>> tu
>>>>> 
>>>>> torial%2Fvalue-objects.html=02%7C01%7Caharui%40adobe.com%7C924b229e
>>>>> 49
>>>>> 
>>>>> bb443ddbf708d56d50cd97%7C71f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%7C6365
>>>>> 35
>>>>> 
>>>>> 116172825365=3m3kTW910JYWV8MaM4%2F%2B3v82l5EvxIqgRjqAtIC7N%2BU%3D&
>>>>> re
>>>>> served=0>
>>>>> 
>>>>> Unless I’m missing something, the following line can be renamed:
>>>>> data.message = commitObj.message;
>>>>> 
>>>>> I think it should have been:
>>>>> data.message = commitObj[“message

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

[Gabe Harbs]

What kind of utility do you have in mind?


> On Feb 6, 2018, at 7:09 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
> 
> Don't bother making VO's by hand for ASDoc.  Let's write a utility to
> generate it.  It will save everyone time.  If you want to see
> bin/js-release, change the build to not use ADVANCED_OPTIMIZATIONS for now.
> 
> There are lots of reasons to avoid using plain Object in a Royale app
> other than as a hash map.  IMO, most C and Java apps don't use generic
> untyped dynamic bags of properties.  If I add a warning about Object use,
> there will be a directive to suppress it.  Objects are prone to error, and
> there is some indication that runtimes work better with type information.
> The JS runtimes wouldn't bother type inferencing otherwise.  WASM hints
> that it wants types.
> 
> My 2 cents,
> -Alex
> 
> On 2/6/18, 8:45 AM, "Gabe Harbs" <harbs.li...@gmail.com> wrote:
> 
>> Huh?
>> 
>> I don’t see how it’s possible to avoid Object completely. Even using VOs
>> require constructing them from Objects when coming from outside sources.
>> 
>> Again: I’m not arguing against using VOs when possible/practical. I’m
>> just arguing that use of dot notation on Objects shouldn’t blow up your
>> app.
>> 
>> Right now, I’m creating VOs for the ASDoc app. It’s kind of tedious work…
>> 
>> Harbs
>> 
>>> On Feb 6, 2018, at 6:40 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
>>> 
>>> Good catch. I fixed that.
>>> 
>>> Actually, you are arguing in favor of ValueObjects.  The error was there
>>> because commitObj was a plain Object so the compiler couldn't understand
>>> more about it.  We want to not have any plain objects in a Royale app.
>>> They only create potential problems.  In fact, maybe it is time for me
>>> to
>>> figure out how to generate warnings on every use of plain Object.
>>> Eventually we will have typedefs for the GitHub value objects and then
>>> there wouldn't be an issue like this.
>>> 
>>> Thanks for proving my point.
>>> 
>>> -Alex
>>> 
>>> On 2/6/18, 2:59 AM, "Gabe Harbs" <harbs.li...@gmail.com> wrote:
>>> 
>>>> To illustrate that the VO solution is also error prone, I’m pretty sure
>>>> that this page has a mistake:
>>>> 
>>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapachero
>>>> ya
>>>> 
>>>> leci.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyaleDocs_Staging%2Flast
>>>> Su
>>>> 
>>>> ccessfulBuild%2Fartifact%2F_site%2Fcreate-an-application%2Fapplication-t
>>>> ut
>>>> 
>>>> orial%2Fvalue-objects.html=02%7C01%7Caharui%40adobe.com%7C924b229e4
>>>> 9b
>>>> 
>>>> b443ddbf708d56d50cd97%7C71f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%7C63653
>>>> 51
>>>> 
>>>> 16172815360=e9FoFwJfNJfjmFlWF4%2FRIwCNU4R5mhEEQ9GYz70W3Ls%3D
>>>> ve
>>>> d=0 
>>>> 
>>>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacher
>>>> oy
>>>> 
>>>> aleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyaleDocs_Staging%2Flas
>>>> tS
>>>> 
>>>> uccessfulBuild%2Fartifact%2F_site%2Fcreate-an-application%2Fapplication-
>>>> tu
>>>> 
>>>> torial%2Fvalue-objects.html=02%7C01%7Caharui%40adobe.com%7C924b229e
>>>> 49
>>>> 
>>>> bb443ddbf708d56d50cd97%7C71f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%7C6365
>>>> 35
>>>> 
>>>> 116172825365=3m3kTW910JYWV8MaM4%2F%2B3v82l5EvxIqgRjqAtIC7N%2BU%3D&
>>>> re
>>>> served=0>
>>>> 
>>>> Unless I’m missing something, the following line can be renamed:
>>>>  data.message = commitObj.message;
>>>> 
>>>> I think it should have been:
>>>>  data.message = commitObj[“message”];
>>>> 
>>>> Harbs
>>>> 
>>>>> On Feb 6, 2018, at 12:48 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>>>>> 
>>>>> Related:
>>>>> 
>>>>> On this page: 
>>>>> 
>>>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacher
>>>>> oy
>>>>> 
>>>>> aleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyaleDocs_Staging%2Fla
>>>>> st
>>>>> 
>>

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

[Gabe Harbs]

Huh?

I don’t see how it’s possible to avoid Object completely. Even using VOs 
require constructing them from Objects when coming from outside sources.

Again: I’m not arguing against using VOs when possible/practical. I’m just 
arguing that use of dot notation on Objects shouldn’t blow up your app.

Right now, I’m creating VOs for the ASDoc app. It’s kind of tedious work…

Harbs

> On Feb 6, 2018, at 6:40 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
> 
> Good catch. I fixed that.
> 
> Actually, you are arguing in favor of ValueObjects.  The error was there
> because commitObj was a plain Object so the compiler couldn't understand
> more about it.  We want to not have any plain objects in a Royale app.
> They only create potential problems.  In fact, maybe it is time for me to
> figure out how to generate warnings on every use of plain Object.
> Eventually we will have typedefs for the GitHub value objects and then
> there wouldn't be an issue like this.
> 
> Thanks for proving my point.
> 
> -Alex
> 
> On 2/6/18, 2:59 AM, "Gabe Harbs" <harbs.li...@gmail.com> wrote:
> 
>> To illustrate that the VO solution is also error prone, I’m pretty sure
>> that this page has a mistake:
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroya
>> leci.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyaleDocs_Staging%2FlastSu
>> ccessfulBuild%2Fartifact%2F_site%2Fcreate-an-application%2Fapplication-tut
>> orial%2Fvalue-objects.html=02%7C01%7Caharui%40adobe.com%7C924b229e49b
>> b443ddbf708d56d50cd97%7C71f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%7C6365351
>> 16172815360=e9FoFwJfNJfjmFlWF4%2FRIwCNU4R5mhEEQ9GYz70W3Ls%3D
>> d=0 
>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroy
>> aleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyaleDocs_Staging%2FlastS
>> uccessfulBuild%2Fartifact%2F_site%2Fcreate-an-application%2Fapplication-tu
>> torial%2Fvalue-objects.html=02%7C01%7Caharui%40adobe.com%7C924b229e49
>> bb443ddbf708d56d50cd97%7C71f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%7C636535
>> 116172825365=3m3kTW910JYWV8MaM4%2F%2B3v82l5EvxIqgRjqAtIC7N%2BU%3D
>> served=0>
>> 
>> Unless I’m missing something, the following line can be renamed:
>>   data.message = commitObj.message;
>> 
>> I think it should have been:
>>   data.message = commitObj[“message”];
>> 
>> Harbs
>> 
>>> On Feb 6, 2018, at 12:48 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>>> 
>>> Related:
>>> 
>>> On this page: 
>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroy
>>> aleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyaleDocs_Staging%2Flast
>>> SuccessfulBuild%2Fartifact%2F_site%2Fcreate-an-application%2Fapplication-
>>> tutorial%2Fdata.html=02%7C01%7Caharui%40adobe.com%7C924b229e49bb443d
>>> dbf708d56d50cd97%7C71f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%7C63653511617
>>> 2825365=IgeSJZENyrUXHWMMzG7U5ZIBYdBe5so%2BeO81N%2B1u%2B%2Fc%3D
>>> rved=0 
>>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapachero
>>> yaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyaleDocs_Staging%2Flas
>>> tSuccessfulBuild%2Fartifact%2F_site%2Fcreate-an-application%2Fapplication
>>> -tutorial%2Fdata.html=02%7C01%7Caharui%40adobe.com%7C924b229e49bb443
>>> ddbf708d56d50cd97%7C71f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%7C6365351161
>>> 72825365=IgeSJZENyrUXHWMMzG7U5ZIBYdBe5so%2BeO81N%2B1u%2B%2Fc%3D
>>> erved=0>
>>> 
>>> Shouldn’t the following code have trouble with minification?
>>> 
>>> {
>>>  repos = configurator.json.repos;
>>>  projectName = configurator.json.projectName;
>>> }
>>> 
>>> What’s preventing json.repos and json.projectName from being renamed?
>>> 
>>>> On Feb 5, 2018, at 11:34 PM, Alex Harui <aha...@adobe.com.INVALID
>>>> <mailto:aha...@adobe.com.INVALID>> wrote:
>>>> 
>>>> Maybe I'm missing something.  I don't think Royale has any extra
>>>> problems
>>>> with JSON objects than other JS Frameworks have.  If you want to
>>>> minify,
>>>> you have to use brackets and strings.  If you don't want to minify,
>>>> then
>>>> you don't need to worry about that.  Am I wrong about that?
>>>> 
>>>> 
>>>> JSON has something like a "reviver".  Has anyone played with that to
>>>> see
>>>> if it can be used to convert straight to VO's?
>>>> 
>>>> Thanks,
>>&g

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

[Gabe Harbs]

To illustrate that the VO solution is also error prone, I’m pretty sure that 
this page has a mistake:
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/RoyaleDocs_Staging/lastSuccessfulBuild/artifact/_site/create-an-application/application-tutorial/value-objects.html
 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/RoyaleDocs_Staging/lastSuccessfulBuild/artifact/_site/create-an-application/application-tutorial/value-objects.html>

Unless I’m missing something, the following line can be renamed:
data.message = commitObj.message;

I think it should have been:
data.message = commitObj[“message”];

Harbs

> On Feb 6, 2018, at 12:48 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
> 
> Related:
> 
> On this page: 
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/RoyaleDocs_Staging/lastSuccessfulBuild/artifact/_site/create-an-application/application-tutorial/data.html
>  
> <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/RoyaleDocs_Staging/lastSuccessfulBuild/artifact/_site/create-an-application/application-tutorial/data.html>
> 
> Shouldn’t the following code have trouble with minification?
> 
> {
>   repos = configurator.json.repos;
>   projectName = configurator.json.projectName;
> }
> 
> What’s preventing json.repos and json.projectName from being renamed?
> 
>> On Feb 5, 2018, at 11:34 PM, Alex Harui <aha...@adobe.com.INVALID 
>> <mailto:aha...@adobe.com.INVALID>> wrote:
>> 
>> Maybe I'm missing something.  I don't think Royale has any extra problems
>> with JSON objects than other JS Frameworks have.  If you want to minify,
>> you have to use brackets and strings.  If you don't want to minify, then
>> you don't need to worry about that.  Am I wrong about that?
>> 
>> 
>> JSON has something like a "reviver".  Has anyone played with that to see
>> if it can be used to convert straight to VO's?
>> 
>> Thanks,
>> -Alex 
>> 
>> On 2/5/18, 1:08 PM, "Gabe Harbs" <harbs.li...@gmail.com 
>> <mailto:harbs.li...@gmail.com>> wrote:
>> 
>>> An additional point:
>>> 
>>> How do you propose handling json that’s multiple levels deep? Walk the
>>> json and construct VOs on each level? That seems to me just as bad as the
>>> problem. Imagine you just want foo.baz.thingy.uid? You’d need to create a
>>> VO of foo, baz and thingy or be forced to use
>>> foo[“baz”][“thingy”][“uid”]. Of course the average user is not going to
>>> remember to do that until their release build doesn’t work…
>>> 
>>> Creating VOs means you can’t simply use JSON.parse(). You’d need your own
>>> parser for each type of json you’re consuming. OK. Maybe not full
>>> parsing, but the constructors for these VOs will get pretty messy —
>>> especially if the structure is a bit fluid.
>>> 
>>> Harbs
>>> 
>>> 
>>>> On Feb 5, 2018, at 10:36 PM, Gabe Harbs <harbs.li...@gmail.com 
>>>> <mailto:harbs.li...@gmail.com>> wrote:
>>>> 
>>>> In theory, everything you say is true. It might even be good practice.
>>>> 
>>>> I’m telling you that this was a pain point when migrating my app.
>>>> Simply declaring types as VOs didn't solve the problem for me. The way
>>>> I’ve found that’s needed to solve the problem was passing the object
>>>> literal into a VO constructor and declaring the variables using
>>>> bracketed access. I was likely going about it wrong, but it was easier
>>>> to just go with the bracketed literals.
>>>> 
>>>> Again: Suggesting using VOs (if we can figure out easy instructions to
>>>> do so) is probably a good idea and better recommended practice, but
>>>> people live on the edge using other JS frameworks, and I’d rather not
>>>> make it harder than it needs to be if they do want to use untyped object
>>>> literals.
>>>> 
>>>> Harbs
>>>> 
>>>>> On Feb 5, 2018, at 8:01 PM, Alex Harui <aha...@adobe.com.INVALID 
>>>>> <mailto:aha...@adobe.com.INVALID>>
>>>>> wrote:
>>>>> 
>>>>> It was great to skip type-checking in Flash at times, but the runtime
>>>>> was
>>>>> also strongly typed.  Also, JS was not a practical language for Flash.
>>>>> It
>>>>> is more risky to do skip type-checking in Royale for JS.  These new
>>>>> cars
>>>>> with lane warnings are a rough analogy.  They only let you be l

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

[Gabe Harbs]

Related:

On this page: 
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/RoyaleDocs_Staging/lastSuccessfulBuild/artifact/_site/create-an-application/application-tutorial/data.html
 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/RoyaleDocs_Staging/lastSuccessfulBuild/artifact/_site/create-an-application/application-tutorial/data.html>

Shouldn’t the following code have trouble with minification?

{
  repos = configurator.json.repos;
  projectName = configurator.json.projectName;
}

What’s preventing json.repos and json.projectName from being renamed?

> On Feb 5, 2018, at 11:34 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
> 
> Maybe I'm missing something.  I don't think Royale has any extra problems
> with JSON objects than other JS Frameworks have.  If you want to minify,
> you have to use brackets and strings.  If you don't want to minify, then
> you don't need to worry about that.  Am I wrong about that?
> 
> 
> JSON has something like a "reviver".  Has anyone played with that to see
> if it can be used to convert straight to VO's?
> 
> Thanks,
> -Alex 
> 
> On 2/5/18, 1:08 PM, "Gabe Harbs" <harbs.li...@gmail.com> wrote:
> 
>> An additional point:
>> 
>> How do you propose handling json that’s multiple levels deep? Walk the
>> json and construct VOs on each level? That seems to me just as bad as the
>> problem. Imagine you just want foo.baz.thingy.uid? You’d need to create a
>> VO of foo, baz and thingy or be forced to use
>> foo[“baz”][“thingy”][“uid”]. Of course the average user is not going to
>> remember to do that until their release build doesn’t work…
>> 
>> Creating VOs means you can’t simply use JSON.parse(). You’d need your own
>> parser for each type of json you’re consuming. OK. Maybe not full
>> parsing, but the constructors for these VOs will get pretty messy —
>> especially if the structure is a bit fluid.
>> 
>> Harbs
>> 
>> 
>>> On Feb 5, 2018, at 10:36 PM, Gabe Harbs <harbs.li...@gmail.com> wrote:
>>> 
>>> In theory, everything you say is true. It might even be good practice.
>>> 
>>> I’m telling you that this was a pain point when migrating my app.
>>> Simply declaring types as VOs didn't solve the problem for me. The way
>>> I’ve found that’s needed to solve the problem was passing the object
>>> literal into a VO constructor and declaring the variables using
>>> bracketed access. I was likely going about it wrong, but it was easier
>>> to just go with the bracketed literals.
>>> 
>>> Again: Suggesting using VOs (if we can figure out easy instructions to
>>> do so) is probably a good idea and better recommended practice, but
>>> people live on the edge using other JS frameworks, and I’d rather not
>>> make it harder than it needs to be if they do want to use untyped object
>>> literals.
>>> 
>>> Harbs
>>> 
>>>> On Feb 5, 2018, at 8:01 PM, Alex Harui <aha...@adobe.com.INVALID>
>>>> wrote:
>>>> 
>>>> It was great to skip type-checking in Flash at times, but the runtime
>>>> was
>>>> also strongly typed.  Also, JS was not a practical language for Flash.
>>>> It
>>>> is more risky to do skip type-checking in Royale for JS.  These new
>>>> cars
>>>> with lane warnings are a rough analogy.  They only let you be less
>>>> attentive on nice new painted highways.  Flash's runtime wouldn't let
>>>> you
>>>> make type mismatches so it effectively had lane lines.  JS is a road
>>>> without lane lines.  A ValueObject keeps your eyes on the road.  An
>>>> ounce
>>>> of prevention is better than a pound of cure.
>>>> 
>>>> IMO, you might be better off writing a bead that you can pass a JSON
>>>> object and it will generate the AS class for you to copy from the
>>>> clipboard and paste into a file.  Then you could guess at the types.
>>>> That
>>>> wouldn't require compiler changes and would encourage early prevention.
>>>> 
>>>> Just an idea,
>>>> -Alex
>>>> 
>>>> On 2/5/18, 9:39 AM, "Gabe Harbs" <harbs.li...@gmail.com> wrote:
>>>> 
>>>>> Yeah. That’s what you’ve argued in the past, and in a pure world
>>>>> you’d be
>>>>> right.
>>>>> 
>>>>> However, I’d prefer the option to be practical when dealing with more
>>>>> data types. Being forced to fiddle with pro

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

[Gabe Harbs]

I’m suggesting we have a compiler option to do it for all Object-typed 
properties. This problem is not limited to objects coming from JSON.

The bracket access gets converted to dot access when google minifies the code, 
so there’s no effect on the minified code other than preventing the renaming.

I’m all for making using value objects easier too.

You lost me on the part about SOAP.

Harbs

> On Feb 6, 2018, at 11:05 AM, Alex Harui <aha...@adobe.com.INVALID> wrote:
> 
> I'm not convinced we can know when to generate obj.property vs
> obj["property"] unless we do it for all Objects, not just ones that came
> from JSON.  Or for all property access.  And that is at least 3 extra
> characters per access for anything that isn't JSON.
> 
> I would rather we find ways to make use of ValueObjects easier.  IMO, type
> information will make development faster by catching errors sooner, and
> has the potential to make the runtime performance faster, especially if we
> consider other targets besides JS some day.
> 
> To me, the problem is roughly the same as XML decoding into ValueObjects.
> In XML/SOAP there was a WSDL and some utility converted it to AS
> ValueObjects.  Other metadata instructed AMF to construct real classes
> instead of plain objects.  I think there are APIs for that in JSON.parse.
> I guess I will look into that for the next release.  IMO, if we can't
> convince folks to use the type system, we lose a major productivity
> advantage of Royale.  There is always going to be more setup work for
> Royale. You can't just copy a file and view it in the browser.  You have
> to run our compiler first.  We should encourage you to create ValueObjects
> at some point.  My tutorial suggests doing it before creating a production
> version.
> 
> My 2 cents,
> -Alex
> 
> On 2/6/18, 12:51 AM, "Gabe Harbs" <harbs.li...@gmail.com> wrote:
> 
>> Quite sure. In my angular app I was using an older version of the closure
>> compiler to minify the js files. I was using the default options which
>> clearly does not use ADVANCED_OPTIMIZATIONS, so the object literals
>> didn’t get renamed.
>> 
>> I think most modern app frameworks use other tools such as Babel for
>> magnification, but I believe that handles object literals correctly too.
>> 
>> We definitely want to use ADVANCED_OPTIMIZATIONS, but that’s killing
>> object literals. I’m proposing a compiler *option* to allow to continue
>> using ADVANCED_OPTIMIZATIONS, but prevent renaming on objects which
>> should not be renamed.
>> 
>> Harbs
>> 
>>> On Feb 6, 2018, at 9:38 AM, Alex Harui <aha...@adobe.com.INVALID> wrote:
>>> 
>>> Are you sure Angular and React minify your code instead of running it
>>> against their minified framework?
>>> 
>>> -Alex
>>> 
>>> On 2/5/18, 11:22 PM, "Gabe Harbs" <harbs.li...@gmail.com> wrote:
>>> 
>>>>> Maybe I'm missing something.  I don't think Royale has any extra
>>>>> problems
>>>>> with JSON objects than other JS Frameworks have.  If you want to
>>>>> minify,
>>>>> you have to use brackets and strings.
>>>> 
>>>> It does.
>>>> 
>>>> I’ve written angular apps and I’ve never had to worry about using
>>>> bracket
>>>> notation for minifying simple js objects. I’m pretty sure the same is
>>>> for
>>>> React, etc.
>>>> 
>>>>> On Feb 5, 2018, at 11:34 PM, Alex Harui <aha...@adobe.com.INVALID>
>>>>> wrote:
>>>>> 
>>>>> Maybe I'm missing something.  I don't think Royale has any extra
>>>>> problems
>>>>> with JSON objects than other JS Frameworks have.  If you want to
>>>>> minify,
>>>>> you have to use brackets and strings.  If you don't want to minify,
>>>>> then
>>>>> you don't need to worry about that.  Am I wrong about that?
>>>>> 
>>>>> 
>>>>> JSON has something like a "reviver".  Has anyone played with that to
>>>>> see
>>>>> if it can be used to convert straight to VO's?
>>>>> 
>>>>> Thanks,
>>>>> -Alex 
>>>>> 
>>>>> On 2/5/18, 1:08 PM, "Gabe Harbs" <harbs.li...@gmail.com> wrote:
>>>>> 
>>>>>> An additional point:
>>>>>> 
>>>>>> How do you propose handling json that’s multiple levels deep? Walk
>>>>>> the
>>>>

Re: Website description

[Gabe Harbs]

(I was just sending some friends a link to Royale so they could check it out.)

> On Feb 6, 2018, at 9:23 AM, Gabe Harbs <harbs.li...@gmail.com> wrote:
> 
> It’s a private Slack channel I belong to. Nothing to do with Royale.
> 
>> On Feb 5, 2018, at 11:26 PM, Justin Mclean <jus...@classsoftware.com> wrote:
>> 
>> Hi,
>> 
>>> I was not aware of this. I think I solved it. If you try now to link on
>>> slack you should see right values (if there's no catching...)
>> 
>> How does someone sign up to this slack channel?
>> 
>> Thanks,
>> Justin
> 

Re: Website description

[Gabe Harbs]

It’s a private Slack channel I belong to. Nothing to do with Royale.

> On Feb 5, 2018, at 11:26 PM, Justin Mclean  wrote:
> 
> Hi,
> 
>> I was not aware of this. I think I solved it. If you try now to link on
>> slack you should see right values (if there's no catching...)
> 
> How does someone sign up to this slack channel?
> 
> Thanks,
> Justin