Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[Dany Dhondt]

Alex,

The version number here came from package.json so it should have been updated 
by someone.

I reinstalled from the link you provided with no problem.
But running the royale server:debug [1] command gives me the same errors as 
before.

I noticed that when running: royale new  my-royale-app, only an app folder is 
created with a src folder in it.
In this src folder, there is a main.mxml file. So no other files or folders 
whatsoever are created by the 'new' command.

This explains the error:
Error: ENOENT: no such file or directory, open '/Volumes/Macintosh 
HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/src/bin/js-debug/index.html'

-Dany

[1] https://github.com/apache/royale-asjs/tree/develop/npm/cli

Op 2 mei 2018 om 05:13 uur uur schreef Alex Harui :

That's my windows machine that I used for 0.9.2.

Where did it say 0.9.3? I'm trying to remember if I published the package to 
NPM or if you did. Maybe the scripts are running or were run after some 
versions got updated in the repos. I have not run a build on my windows machine 
since the release.

-Alex

On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" 
 wrote:

On Tue, May 1, 2018 at 1:36 PM, Alex Harui  wrote:


Om,

I got the warnings when we released 0.9.2 but it appeared to leave a
functional SDK. Now it is hanging for me and Dany.

I don't think I've run a publish and I don't think the CI server is
either, but you never know. Try grabbing one of the SWCs. Unzip it and
swfdump the library.swf. There should be debugfile bytecodes with paths to
the source that give us a clue.



Good idea. Here is what I see in swfdump:

2) + 0:1 debugfile
"C:\temp\rc\royale-asjs\frameworks\projects\Collections\src\main\royale;org\apache\royale\collections;FlattenedList.as"

Any idea whose machine this could have been?

Thanks,
Om



-Alex

On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
Muppirala"  wrote:

On Tue, May 1, 2018 at 8:57 AM, Alex Harui 
wrote:

> Hi Dany,
>
> The link is directly to a tar.gz built by our CI server. No humans
> involved, and no special packaging for NPM. NPM says it can install
any
> tar.gz file. Try downloading the file at that link and using Mac
Finder to
> expand it into a folder. For me it expands without errors. This is
why I
> believe it is some incompatibility with NPM.
>
> If the tar.gz expands for you on Mac, you can try to "npm install"
the
> folder. Running:
>
> sudo npm install -g 
>
> seemed to work for me.
>
> -Alex
>

I just tried
npm install @apache-royale/royale-js -g
on windwos and it installed just fine.

Although, I notice that @apache-royale/royale-js@0.9.3 was
installed. It
should have installed 0.9.2. Did we publish 0.9.3 to npm by mistake?
Could that be related?

Thanks,
Om


>
> On 5/1/18, 1:51 AM, "Dany Dhondt"  wrote:
>
> Hi Alex,
>
> I tried the direct link you provided: same result (hundreds of
> ‘invalid entry’ messages)
>
> My version of npm is 6.0.0
>
> downgrading to a lower npm version is not an option at this
moment
> because I’m on a production mac with crucial projects on it.
>
> Amids all the invalid entry messages, now and then is a somewhat
> longer message like
>
> WARN⸨ ░░░⸩ ⠸ extract:@apache-royale/royale-js:
verb
> lock using /Users/ tar invalid entry
>
>
>
>
> Is it Om that created this package? This might give him an idea
of
> what’s going on?
>
> -Dany
>
>
>
> > Op 30 apr. 2018, om 18:39 heeft Alex Harui
 > het volgende geschreven:
> >
> > Hmm. I'm getting that too on my Mac. It used to complete
anyway
> and work, but now it appears to be hanging.
> >
> > The internet hints that it might have to do with the version
of NPM
> used to create the package vs the NPM we are using to install. Om,
did
> you create the packages for publishing to NPM? If so, what version
did you
> use?
> >
> > On the other hand, just installing the nightly build also
gives a
> ton of those warnings but seems to complete and produce a runnable
compiler.
> >
> > sudo npm install -g 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fna01.safelinks=02%7C01%7Caharui%40adobe.com%7Ca57dd23c4db24e0a18d008d5afa88c6b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636608060969636900=sgZBuZoOmRwla%2Bti%2FwtU0vRemJMy7MjB5sRC9d0Qdic%3D=0.
protection.outlook.com/?url=https%3A%2F%2Fna01.safelinks&
data=02%7C01%7Caharui%40adobe.com%7C00079fd32a194a4caf1b08d5af8bd09e%
7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636607937396983186=D%
2BedD6Pv8Eh7GSR8q1dLpGxi6RL5R43uCdchzXoECD0%3D=0.
> protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.
> westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_
> jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2Fapache-
> 

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[OmPrakash Muppirala]

On Tue, May 1, 2018, 8:13 PM Alex Harui  wrote:

> That's my windows machine that I used for 0.9.2.
>
> Where did it say 0.9.3?


It shows up after the npm install completes.


I'm trying to remember if I published the package to NPM or if you did.
> Maybe the scripts are running or were run after some versions got updated
> in the repos.  I have not run a build on my windows machine since the
> release.


>
>
>
>
> -Alex
>
> On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
>  wrote:
>
> On Tue, May 1, 2018 at 1:36 PM, Alex Harui 
> wrote:
>
> > Om,
> >
> > I got the warnings when we released 0.9.2 but it appeared to leave a
> > functional SDK.  Now it is hanging for me and Dany.
> >
> > I don't think I've run a publish and I don't think the CI server is
> > either, but you never know.  Try grabbing one of the SWCs.  Unzip it
> and
> > swfdump the library.swf.  There should be debugfile bytecodes with
> paths to
> > the source that give us a clue.
> >
> >
> Good idea.  Here is what I see in swfdump:
>
> 2) + 0:1 debugfile
>
> "C:\temp\rc\royale-asjs\frameworks\projects\Collections\src\main\royale;org\apache\royale\collections;FlattenedList.as"
>
> Any idea whose machine this could have been?
>
> Thanks,
> Om
>
>
> > -Alex
> >
> > On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
> > Muppirala" 
> wrote:
> >
> > On Tue, May 1, 2018 at 8:57 AM, Alex Harui
> 
> > wrote:
> >
> > > Hi Dany,
> > >
> > > The link is directly to a tar.gz built by our CI server.  No
> humans
> > > involved, and no special packaging for NPM.  NPM says it can
> install
> > any
> > > tar.gz file.  Try downloading the file at that link and using
> Mac
> > Finder to
> > > expand it into a folder.  For me it expands without errors.
> This is
> > why I
> > > believe it is some incompatibility with NPM.
> > >
> > > If the tar.gz expands for you on Mac, you can try to "npm
> install"
> > the
> > > folder.  Running:
> > >
> > > sudo npm install -g 
> > >
> > > seemed to work for me.
> > >
> > > -Alex
> > >
> >
> > I just tried
> > npm install @apache-royale/royale-js -g
> > on windwos and it installed just fine.
> >
> > Although, I notice that  @apache-royale/royale-js@0.9.3 was
> > installed.  It
> > should have installed 0.9.2.  Did we publish 0.9.3 to npm by
> mistake?
> > Could that be related?
> >
> > Thanks,
> > Om
> >
> >
> > >
> > > On 5/1/18, 1:51 AM, "Dany Dhondt"  wrote:
> > >
> > > Hi Alex,
> > >
> > > I tried the direct link you provided: same result
> (hundreds of
> > > ‘invalid entry’ messages)
> > >
> > > My version of npm is 6.0.0
> > >
> > > downgrading to a lower npm version is not an option at this
> > moment
> > > because I’m on a production mac with crucial projects on it.
> > >
> > > Amids all the invalid entry messages, now and then is a
> somewhat
> > > longer message like
> > >
> > > WARN⸨   ░░░⸩ ⠸ extract:@apache-royale
> /royale-js:
> > verb
> > > lock using /Users/ tar invalid entry
> > >
> > >
> > >
> > >
> > > Is it Om that created this package? This might give him an
> idea
> > of
> > > what’s going on?
> > >
> > > -Dany
> > >
> > >
> > >
> > > > Op 30 apr. 2018, om 18:39 heeft Alex Harui
> >  > > > het volgende geschreven:
> > > >
> > > > Hmm.  I'm getting that too on my Mac.  It used to
> complete
> > anyway
> > > and work, but now it appears to be hanging.
> > > >
> > > > The internet hints that it might have to do with the
> version
> > of NPM
> > > used to create the package vs the  NPM we are using to
> install.  Om,
> > did
> > > you create the packages for publishing to NPM?  If so, what
> version
> > did you
> > > use?
> > > >
> > > > On the other hand, just installing the nightly build also
> > gives a
> > > ton of those warnings but seems to complete and produce a
> runnable
> > compiler.
> > > >
> > > > sudo npm install -g
> 

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[Alex Harui]

That's my windows machine that I used for 0.9.2.

Where did it say 0.9.3?  I'm trying to remember if I published the package to 
NPM or if you did.  Maybe the scripts are running or were run after some 
versions got updated in the repos.  I have not run a build on my windows 
machine since the release.

-Alex

On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" 
 wrote:

On Tue, May 1, 2018 at 1:36 PM, Alex Harui  wrote:

> Om,
>
> I got the warnings when we released 0.9.2 but it appeared to leave a
> functional SDK.  Now it is hanging for me and Dany.
>
> I don't think I've run a publish and I don't think the CI server is
> either, but you never know.  Try grabbing one of the SWCs.  Unzip it and
> swfdump the library.swf.  There should be debugfile bytecodes with paths 
to
> the source that give us a clue.
>
>
Good idea.  Here is what I see in swfdump:

2) + 0:1 debugfile

"C:\temp\rc\royale-asjs\frameworks\projects\Collections\src\main\royale;org\apache\royale\collections;FlattenedList.as"

Any idea whose machine this could have been?

Thanks,
Om


> -Alex
>
> On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
> Muppirala"  wrote:
>
> On Tue, May 1, 2018 at 8:57 AM, Alex Harui 
> wrote:
>
> > Hi Dany,
> >
> > The link is directly to a tar.gz built by our CI server.  No humans
> > involved, and no special packaging for NPM.  NPM says it can install
> any
> > tar.gz file.  Try downloading the file at that link and using Mac
> Finder to
> > expand it into a folder.  For me it expands without errors.  This is
> why I
> > believe it is some incompatibility with NPM.
> >
> > If the tar.gz expands for you on Mac, you can try to "npm install"
> the
> > folder.  Running:
> >
> > sudo npm install -g 
> >
> > seemed to work for me.
> >
> > -Alex
> >
>
> I just tried
> npm install @apache-royale/royale-js -g
> on windwos and it installed just fine.
>
> Although, I notice that  @apache-royale/royale-js@0.9.3 was
> installed.  It
> should have installed 0.9.2.  Did we publish 0.9.3 to npm by mistake?
> Could that be related?
>
> Thanks,
> Om
>
>
> >
> > On 5/1/18, 1:51 AM, "Dany Dhondt"  wrote:
> >
> > Hi Alex,
> >
> > I tried the direct link you provided: same result (hundreds of
> > ‘invalid entry’ messages)
> >
> > My version of npm is 6.0.0
> >
> > downgrading to a lower npm version is not an option at this
> moment
> > because I’m on a production mac with crucial projects on it.
> >
> > Amids all the invalid entry messages, now and then is a somewhat
> > longer message like
> >
> > WARN⸨   ░░░⸩ ⠸ extract:@apache-royale/royale-js:
> verb
> > lock using /Users/ tar invalid entry
> >
> >
> >
> >
> > Is it Om that created this package? This might give him an idea
> of
> > what’s going on?
> >
> > -Dany
> >
> >
> >
> > > Op 30 apr. 2018, om 18:39 heeft Alex Harui
>  > > het volgende geschreven:
> > >
> > > Hmm.  I'm getting that too on my Mac.  It used to complete
> anyway
> > and work, but now it appears to be hanging.
> > >
> > > The internet hints that it might have to do with the version
> of NPM
> > used to create the package vs the  NPM we are using to install.  Om,
> did
> > you create the packages for publishing to NPM?  If so, what version
> did you
> > use?
> > >
> > > On the other hand, just installing the nightly build also
> gives a
> > ton of those warnings but seems to complete and produce a runnable
> compiler.
> > >
> > > sudo npm install -g 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fna01.safelinks=02%7C01%7Caharui%40adobe.com%7Ca57dd23c4db24e0a18d008d5afa88c6b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636608060969636900=sgZBuZoOmRwla%2Bti%2FwtU0vRemJMy7MjB5sRC9d0Qdic%3D=0.
> protection.outlook.com/?url=https%3A%2F%2Fna01.safelinks&
> data=02%7C01%7Caharui%40adobe.com%7C00079fd32a194a4caf1b08d5af8bd09e%
> 

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[OmPrakash Muppirala]

On Tue, May 1, 2018 at 1:36 PM, Alex Harui  wrote:

> Om,
>
> I got the warnings when we released 0.9.2 but it appeared to leave a
> functional SDK.  Now it is hanging for me and Dany.
>
> I don't think I've run a publish and I don't think the CI server is
> either, but you never know.  Try grabbing one of the SWCs.  Unzip it and
> swfdump the library.swf.  There should be debugfile bytecodes with paths to
> the source that give us a clue.
>
>
Good idea.  Here is what I see in swfdump:

2) + 0:1 debugfile
"C:\temp\rc\royale-asjs\frameworks\projects\Collections\src\main\royale;org\apache\royale\collections;FlattenedList.as"

Any idea whose machine this could have been?

Thanks,
Om


> -Alex
>
> On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
> Muppirala"  wrote:
>
> On Tue, May 1, 2018 at 8:57 AM, Alex Harui 
> wrote:
>
> > Hi Dany,
> >
> > The link is directly to a tar.gz built by our CI server.  No humans
> > involved, and no special packaging for NPM.  NPM says it can install
> any
> > tar.gz file.  Try downloading the file at that link and using Mac
> Finder to
> > expand it into a folder.  For me it expands without errors.  This is
> why I
> > believe it is some incompatibility with NPM.
> >
> > If the tar.gz expands for you on Mac, you can try to "npm install"
> the
> > folder.  Running:
> >
> > sudo npm install -g 
> >
> > seemed to work for me.
> >
> > -Alex
> >
>
> I just tried
> npm install @apache-royale/royale-js -g
> on windwos and it installed just fine.
>
> Although, I notice that  @apache-royale/royale-js@0.9.3 was
> installed.  It
> should have installed 0.9.2.  Did we publish 0.9.3 to npm by mistake?
> Could that be related?
>
> Thanks,
> Om
>
>
> >
> > On 5/1/18, 1:51 AM, "Dany Dhondt"  wrote:
> >
> > Hi Alex,
> >
> > I tried the direct link you provided: same result (hundreds of
> > ‘invalid entry’ messages)
> >
> > My version of npm is 6.0.0
> >
> > downgrading to a lower npm version is not an option at this
> moment
> > because I’m on a production mac with crucial projects on it.
> >
> > Amids all the invalid entry messages, now and then is a somewhat
> > longer message like
> >
> > WARN⸨   ░░░⸩ ⠸ extract:@apache-royale/royale-js:
> verb
> > lock using /Users/ tar invalid entry
> >
> >
> >
> >
> > Is it Om that created this package? This might give him an idea
> of
> > what’s going on?
> >
> > -Dany
> >
> >
> >
> > > Op 30 apr. 2018, om 18:39 heeft Alex Harui
>  > > het volgende geschreven:
> > >
> > > Hmm.  I'm getting that too on my Mac.  It used to complete
> anyway
> > and work, but now it appears to be hanging.
> > >
> > > The internet hints that it might have to do with the version
> of NPM
> > used to create the package vs the  NPM we are using to install.  Om,
> did
> > you create the packages for publishing to NPM?  If so, what version
> did you
> > use?
> > >
> > > On the other hand, just installing the nightly build also
> gives a
> > ton of those warnings but seems to complete and produce a runnable
> compiler.
> > >
> > > sudo npm install -g https://na01.safelinks.
> protection.outlook.com/?url=https%3A%2F%2Fna01.safelinks&
> data=02%7C01%7Caharui%40adobe.com%7C00079fd32a194a4caf1b08d5af8bd09e%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636607937396983186=D%
> 2BedD6Pv8Eh7GSR8q1dLpGxi6RL5R43uCdchzXoECD0%3D=0.
> > protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.
> > westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_
> > jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2Fapache-
> > royale-0.9.3-bin-js.tar.gz=02%7C01%7Caharui%40adobe.com%
> > 7C0c405d2ff9134638451608d5af40c2f1%7Cfa7b1b5a7b34438794aed2c178de
> > cee1%7C0%7C0%7C636607615050264364=zKrYmme3fourKgDPSyULPEiiR5%
> > 2FfXBUXmGQ49qdY0aM%3D=0  protection.outlook.com/?url=https%3A%2F%2Fna01.safelinks&
> data=02%7C01%7Caharui%40adobe.com%7C00079fd32a194a4caf1b08d5af8bd09e%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636607937396983186=D%
> 2BedD6Pv8Eh7GSR8q1dLpGxi6RL5R43uCdchzXoECD0%3D=0.
> > protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.
> > westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_
> > jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2Fapache-
> > royale-0.9.3-bin-js.tar.gz=02%7C01%7Caharui%40adobe.com%
> > 7C0c405d2ff9134638451608d5af40c2f1%7Cfa7b1b5a7b34438794aed2c178de
> > cee1%7C0%7C0%7C636607615050264364=zKrYmme3fourKgDPSyULPEiiR5%
>  

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[Alex Harui]

Om,

I got the warnings when we released 0.9.2 but it appeared to leave a functional 
SDK.  Now it is hanging for me and Dany.

I don't think I've run a publish and I don't think the CI server is either, but 
you never know.  Try grabbing one of the SWCs.  Unzip it and swfdump the 
library.swf.  There should be debugfile bytecodes with paths to the source that 
give us a clue.

-Alex

On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" 
 wrote:

On Tue, May 1, 2018 at 8:57 AM, Alex Harui  wrote:

> Hi Dany,
>
> The link is directly to a tar.gz built by our CI server.  No humans
> involved, and no special packaging for NPM.  NPM says it can install any
> tar.gz file.  Try downloading the file at that link and using Mac Finder 
to
> expand it into a folder.  For me it expands without errors.  This is why I
> believe it is some incompatibility with NPM.
>
> If the tar.gz expands for you on Mac, you can try to "npm install" the
> folder.  Running:
>
> sudo npm install -g 
>
> seemed to work for me.
>
> -Alex
>

I just tried
npm install @apache-royale/royale-js -g
on windwos and it installed just fine.

Although, I notice that  @apache-royale/royale-js@0.9.3 was installed.  It
should have installed 0.9.2.  Did we publish 0.9.3 to npm by mistake?
Could that be related?

Thanks,
Om


>
> On 5/1/18, 1:51 AM, "Dany Dhondt"  wrote:
>
> Hi Alex,
>
> I tried the direct link you provided: same result (hundreds of
> ‘invalid entry’ messages)
>
> My version of npm is 6.0.0
>
> downgrading to a lower npm version is not an option at this moment
> because I’m on a production mac with crucial projects on it.
>
> Amids all the invalid entry messages, now and then is a somewhat
> longer message like
>
> WARN⸨   ░░░⸩ ⠸ extract:@apache-royale/royale-js: verb
> lock using /Users/ tar invalid entry
>
>
>
>
> Is it Om that created this package? This might give him an idea of
> what’s going on?
>
> -Dany
>
>
>
> > Op 30 apr. 2018, om 18:39 heeft Alex Harui  > het volgende geschreven:
> >
> > Hmm.  I'm getting that too on my Mac.  It used to complete anyway
> and work, but now it appears to be hanging.
> >
> > The internet hints that it might have to do with the version of NPM
> used to create the package vs the  NPM we are using to install.  Om, did
> you create the packages for publishing to NPM?  If so, what version did 
you
> use?
> >
> > On the other hand, just installing the nightly build also gives a
> ton of those warnings but seems to complete and produce a runnable 
compiler.
> >
> > sudo npm install -g 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fna01.safelinks=02%7C01%7Caharui%40adobe.com%7C00079fd32a194a4caf1b08d5af8bd09e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636607937396983186=D%2BedD6Pv8Eh7GSR8q1dLpGxi6RL5R43uCdchzXoECD0%3D=0.
> protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.
> westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_
> jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2Fapache-
> royale-0.9.3-bin-js.tar.gz=02%7C01%7Caharui%40adobe.com%
> 7C0c405d2ff9134638451608d5af40c2f1%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636607615050264364=zKrYmme3fourKgDPSyULPEiiR5%
> 2FfXBUXmGQ49qdY0aM%3D=0 
 protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.
> westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_
> jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2Fapache-
> royale-0.9.3-bin-js.tar.gz=02%7C01%7Caharui%40adobe.com%
> 7C0c405d2ff9134638451608d5af40c2f1%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636607615050264364=zKrYmme3fourKgDPSyULPEiiR5%
> 2FfXBUXmGQ49qdY0aM%3D=0>
> >
> > I haven't tried downgrading or upgrading my version of NPM (5.6).
> Dany which version are you running?  Can you try different versions of 
NPM?
> >
> > HTH,
> > -Alex
> >
> > On 4/30/18, 1:11 AM, "Dany Dhondt" > wrote:
> >
> >Hi Om,
> >
> >I did that!
> >
> >In the mean time I tried all sorts of things:
> >install 0.9.1 instead of 0.9.3
> >

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[Dany Dhondt]

Hi Om

I also noticed that 0.9.3 was installeren so I tried ...@0.9.2 but that was non 
existing. ...@0.9.1 did exist but gave the same result/errors

-Dany

Verstuurd vanaf mijn iPhone

> Op 1 mei 2018 om 19:48 heeft OmPrakash Muppirala  het 
> volgende geschreven:
> 
>> On Tue, May 1, 2018 at 8:57 AM, Alex Harui  wrote:
>> 
>> Hi Dany,
>> 
>> The link is directly to a tar.gz built by our CI server.  No humans
>> involved, and no special packaging for NPM.  NPM says it can install any
>> tar.gz file.  Try downloading the file at that link and using Mac Finder to
>> expand it into a folder.  For me it expands without errors.  This is why I
>> believe it is some incompatibility with NPM.
>> 
>> If the tar.gz expands for you on Mac, you can try to "npm install" the
>> folder.  Running:
>> 
>>sudo npm install -g 
>> 
>> seemed to work for me.
>> 
>> -Alex
>> 
> 
> I just tried
> npm install @apache-royale/royale-js -g
> on windwos and it installed just fine.
> 
> Although, I notice that  @apache-royale/royale-js@0.9.3 was installed.  It
> should have installed 0.9.2.  Did we publish 0.9.3 to npm by mistake?
> Could that be related?
> 
> Thanks,
> Om
> 
> 
>> 
>> On 5/1/18, 1:51 AM, "Dany Dhondt"  wrote:
>> 
>>Hi Alex,
>> 
>>I tried the direct link you provided: same result (hundreds of
>> ‘invalid entry’ messages)
>> 
>>My version of npm is 6.0.0
>> 
>>downgrading to a lower npm version is not an option at this moment
>> because I’m on a production mac with crucial projects on it.
>> 
>>Amids all the invalid entry messages, now and then is a somewhat
>> longer message like
>> 
>>WARN⸨   ░░░⸩ ⠸ extract:@apache-royale/royale-js: verb
>> lock using /Users/ tar invalid entry
>> 
>> 
>> 
>> 
>>Is it Om that created this package? This might give him an idea of
>> what’s going on?
>> 
>>-Dany
>> 
>> 
>> 
>>> Op 30 apr. 2018, om 18:39 heeft Alex Harui > > het volgende geschreven:
>>> 
>>> Hmm.  I'm getting that too on my Mac.  It used to complete anyway
>> and work, but now it appears to be hanging.
>>> 
>>> The internet hints that it might have to do with the version of NPM
>> used to create the package vs the  NPM we are using to install.  Om, did
>> you create the packages for publishing to NPM?  If so, what version did you
>> use?
>>> 
>>> On the other hand, just installing the nightly build also gives a
>> ton of those warnings but seems to complete and produce a runnable compiler.
>>> 
>>> sudo npm install -g https://na01.safelinks.
>> protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.
>> westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_
>> jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2Fapache-
>> royale-0.9.3-bin-js.tar.gz=02%7C01%7Caharui%40adobe.com%
>> 7C0c405d2ff9134638451608d5af40c2f1%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C636607615050264364=zKrYmme3fourKgDPSyULPEiiR5%
>> 2FfXBUXmGQ49qdY0aM%3D=0 > protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.
>> westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_
>> jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2Fapache-
>> royale-0.9.3-bin-js.tar.gz=02%7C01%7Caharui%40adobe.com%
>> 7C0c405d2ff9134638451608d5af40c2f1%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C636607615050264364=zKrYmme3fourKgDPSyULPEiiR5%
>> 2FfXBUXmGQ49qdY0aM%3D=0>
>>> 
>>> I haven't tried downgrading or upgrading my version of NPM (5.6).
>> Dany which version are you running?  Can you try different versions of NPM?
>>> 
>>> HTH,
>>> -Alex
>>> 
>>> On 4/30/18, 1:11 AM, "Dany Dhondt"  archeme...@mac.com>> wrote:
>>> 
>>>   Hi Om,
>>> 
>>>   I did that!
>>> 
>>>   In the mean time I tried all sorts of things:
>>>   install 0.9.1 instead of 0.9.3
>>>   reinstalled npm
>>> 
>>>   nothing works
>>> 
>>>   -Dany
>>> 
>>> 
 Op 30 apr. 2018, om 09:59 heeft OmPrakash Muppirala <
>> bigosma...@gmail.com > het volgende
>> geschreven:
 
 Dany,
 
 I haven't tested this on a Mac.  I am told that Mac users need to
>> use "sudo
 install npm  " depending on how they installed npm.
>> Perhaps
 you can try that out?
 
 Thanks,
 Om
 
 On Mon, Apr 30, 2018 at 12:54 AM, Dany Dhondt > > wrote:
 
> Hi Om,
> 
> Thanks for pointing that out.
> 
> I’ll have a go with that scenario.
> 
> 1. (re) installing royale
> npm install @apache-royale/royale-js -g
> WARN tar invalid entry extract:@apache-royale/royale-js: verb
>> lock using
> /Users/dany/.npm/_locks/staging-3a08f0df5026584d.lock for
> /usr/local/lib/node_modules/.staging
> WARN tar invalid entry
> 
> Then hundreds of ‘invalid entry’ lines in the terminal.
> 
> And finally
> 
> …
> 
> WARN tar invalid entry

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[OmPrakash Muppirala]

On Tue, May 1, 2018 at 8:57 AM, Alex Harui  wrote:

> Hi Dany,
>
> The link is directly to a tar.gz built by our CI server.  No humans
> involved, and no special packaging for NPM.  NPM says it can install any
> tar.gz file.  Try downloading the file at that link and using Mac Finder to
> expand it into a folder.  For me it expands without errors.  This is why I
> believe it is some incompatibility with NPM.
>
> If the tar.gz expands for you on Mac, you can try to "npm install" the
> folder.  Running:
>
> sudo npm install -g 
>
> seemed to work for me.
>
> -Alex
>

I just tried
npm install @apache-royale/royale-js -g
on windwos and it installed just fine.

Although, I notice that  @apache-royale/royale-js@0.9.3 was installed.  It
should have installed 0.9.2.  Did we publish 0.9.3 to npm by mistake?
Could that be related?

Thanks,
Om


>
> On 5/1/18, 1:51 AM, "Dany Dhondt"  wrote:
>
> Hi Alex,
>
> I tried the direct link you provided: same result (hundreds of
> ‘invalid entry’ messages)
>
> My version of npm is 6.0.0
>
> downgrading to a lower npm version is not an option at this moment
> because I’m on a production mac with crucial projects on it.
>
> Amids all the invalid entry messages, now and then is a somewhat
> longer message like
>
> WARN⸨   ░░░⸩ ⠸ extract:@apache-royale/royale-js: verb
> lock using /Users/ tar invalid entry
>
>
>
>
> Is it Om that created this package? This might give him an idea of
> what’s going on?
>
> -Dany
>
>
>
> > Op 30 apr. 2018, om 18:39 heeft Alex Harui  > het volgende geschreven:
> >
> > Hmm.  I'm getting that too on my Mac.  It used to complete anyway
> and work, but now it appears to be hanging.
> >
> > The internet hints that it might have to do with the version of NPM
> used to create the package vs the  NPM we are using to install.  Om, did
> you create the packages for publishing to NPM?  If so, what version did you
> use?
> >
> > On the other hand, just installing the nightly build also gives a
> ton of those warnings but seems to complete and produce a runnable compiler.
> >
> > sudo npm install -g https://na01.safelinks.
> protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.
> westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_
> jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2Fapache-
> royale-0.9.3-bin-js.tar.gz=02%7C01%7Caharui%40adobe.com%
> 7C0c405d2ff9134638451608d5af40c2f1%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636607615050264364=zKrYmme3fourKgDPSyULPEiiR5%
> 2FfXBUXmGQ49qdY0aM%3D=0  protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.
> westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_
> jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2Fapache-
> royale-0.9.3-bin-js.tar.gz=02%7C01%7Caharui%40adobe.com%
> 7C0c405d2ff9134638451608d5af40c2f1%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636607615050264364=zKrYmme3fourKgDPSyULPEiiR5%
> 2FfXBUXmGQ49qdY0aM%3D=0>
> >
> > I haven't tried downgrading or upgrading my version of NPM (5.6).
> Dany which version are you running?  Can you try different versions of NPM?
> >
> > HTH,
> > -Alex
> >
> > On 4/30/18, 1:11 AM, "Dany Dhondt" > wrote:
> >
> >Hi Om,
> >
> >I did that!
> >
> >In the mean time I tried all sorts of things:
> >install 0.9.1 instead of 0.9.3
> >reinstalled npm
> >
> >nothing works
> >
> >-Dany
> >
> >
> >> Op 30 apr. 2018, om 09:59 heeft OmPrakash Muppirala <
> bigosma...@gmail.com > het volgende
> geschreven:
> >>
> >> Dany,
> >>
> >> I haven't tested this on a Mac.  I am told that Mac users need to
> use "sudo
> >> install npm  " depending on how they installed npm.
> Perhaps
> >> you can try that out?
> >>
> >> Thanks,
> >> Om
> >>
> >> On Mon, Apr 30, 2018 at 12:54 AM, Dany Dhondt  > wrote:
> >>
> >>> Hi Om,
> >>>
> >>> Thanks for pointing that out.
> >>>
> >>> I’ll have a go with that scenario.
> >>>
> >>> 1. (re) installing royale
> >>> npm install @apache-royale/royale-js -g
> >>> WARN tar invalid entry extract:@apache-royale/royale-js: verb
> lock using
> >>> /Users/dany/.npm/_locks/staging-3a08f0df5026584d.lock for
> >>> /usr/local/lib/node_modules/.staging
> >>> WARN tar invalid entry
> >>>
> >>> Then hundreds of ‘invalid entry’ lines in the terminal.
> >>>
> >>> And finally
> >>>
> >>> …
> >>>
> >>> WARN tar invalid entry
> >>> /usr/local/bin/asjscompc -> /usr/local/lib/node_modules/@
> >>> apache-royale/royale-js/royale-asjs/js/bin/asjscompcnpm
> >>> /usr/local/bin/asjsc -> 

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[Dany Dhondt]

Hi Om,

I did that!

In the mean time I tried all sorts of things:
install 0.9.1 instead of 0.9.3
reinstalled npm

nothing works

-Dany


> Op 30 apr. 2018, om 09:59 heeft OmPrakash Muppirala  
> het volgende geschreven:
> 
> Dany,
> 
> I haven't tested this on a Mac.  I am told that Mac users need to use "sudo
> install npm  " depending on how they installed npm.  Perhaps
> you can try that out?
> 
> Thanks,
> Om
> 
> On Mon, Apr 30, 2018 at 12:54 AM, Dany Dhondt  wrote:
> 
>> Hi Om,
>> 
>> Thanks for pointing that out.
>> 
>> I’ll have a go with that scenario.
>> 
>> 1. (re) installing royale
>> npm install @apache-royale/royale-js -g
>> WARN tar invalid entry extract:@apache-royale/royale-js: verb lock using
>> /Users/dany/.npm/_locks/staging-3a08f0df5026584d.lock for
>> /usr/local/lib/node_modules/.staging
>> WARN tar invalid entry
>> 
>> Then hundreds of ‘invalid entry’ lines in the terminal.
>> 
>> And finally
>> 
>> …
>> 
>> WARN tar invalid entry
>> /usr/local/bin/asjscompc -> /usr/local/lib/node_modules/@
>> apache-royale/royale-js/royale-asjs/js/bin/asjscompcnpm
>> /usr/local/bin/asjsc -> /usr/local/lib/node_modules/@
>> apache-royale/royale-js/royale-asjs/js/bin/asjscnpm
>> /usr/local/bin/compc -> /usr/local/lib/node_modules/@
>> apache-royale/royale-js/royale-asjs/js/bin/compcnpm
>> /usr/local/bin/externc -> /usr/local/lib/node_modules/@
>> apache-royale/royale-js/royale-asjs/js/bin/externcnpm
>> /usr/local/bin/asnodec -> /usr/local/lib/node_modules/@
>> apache-royale/royale-js/royale-asjs/js/bin/asnodecnpm
>> /usr/local/bin/mxmlc -> /usr/local/lib/node_modules/@
>> apache-royale/royale-js/royale-asjs/js/bin/mxmlcnpm
>> + @apache-royale/royale-js@0.9.3
>> updated 1 package in 17.395s
>> 
>> 
>> What are those invalid entries??
>> 
>> 2. install cli tool
>> 
>> npm install @apache-royale/cli@alpha -g
>> no problem here
>> 
>> 3. create royale app
>> 
>> royale new helloWorld
>> cd helloWorld
>> 
 no problem
>> 
>> 4. running the app
>> 
>> royale serve:debug
>> 
>> Didn’t work:
>> 
>> helloWorld dany$  > royale serve:debug
>> Compiling...
>> WARNING: An illegal reflective access operation has occurred
>> WARNING: Illegal reflective access by 
>> com.google.common.base.internal.Finalizer
>> (file:/usr/local/lib/node_modules/@apache-royale/royale-
>> js/royale-asjs/js/lib/guava.jar) to field java.lang.Thread.
>> inheritableThreadLocals
>> WARNING: Please consider reporting this to the maintainers of
>> com.google.common.base.internal.Finalizer
>> WARNING: Use --illegal-access=warn to enable warnings of further illegal
>> reflective access operations
>> WARNING: All illegal access operations will be denied in a future release
>> Error: unable to open 'HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/src/Main.
>> mxml'.
>> 
>> 
>> 
>> Command failed: mxmlc /Volumes/Macintosh HD/Documents/ARCHEMEDIA/
>> ROYALE/helloWorld/src/Main.mxml -debug=true
>> WARNING: An illegal reflective access operation has occurred
>> WARNING: Illegal reflective access by 
>> com.google.common.base.internal.Finalizer
>> (file:/usr/local/lib/node_modules/@apache-royale/royale-
>> js/royale-asjs/js/lib/guava.jar) to field java.lang.Thread.
>> inheritableThreadLocals
>> WARNING: Please consider reporting this to the maintainers of
>> com.google.common.base.internal.Finalizer
>> WARNING: Use --illegal-access=warn to enable warnings of further illegal
>> reflective access operations
>> WARNING: All illegal access operations will be denied in a future release
>> Error: unable to open 'HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/src/Main.
>> mxml'.
>> 
>> 
>> 
>> 
>> fs.js:646
>>  return binding.open(pathModule._makeLong(path), stringToFlags(flags),
>> mode);
>> ^
>> 
>> Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
>> HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/bin/js-debug/index.html'
>>at Object.fs.openSync (fs.js:646:18)
>>at Object.fs.readFileSync (fs.js:551:33)
>>at updateIndex (/usr/local/lib/node_modules/@
>> apache-royale/cli/index.js:125:24)
>>at compileDebug (/usr/local/lib/node_modules/@
>> apache-royale/cli/index.js:106:9)
>>at serveDebug (/usr/local/lib/node_modules/@
>> apache-royale/cli/index.js:88:5)
>>at Object. (/usr/local/lib/node_modules/@
>> apache-royale/cli/index.js:59:13)
>>at Module._compile (module.js:652:30)
>>at Object.Module._extensions..js (module.js:663:10)
>>at Module.load (module.js:565:32)
>>at tryModuleLoad (module.js:505:12)
>> helloWorld dany$  >
>> 
>> 
>> 
>> 
>> Any ideas?
>> 
>> -Dany
>> 
>> 
>> 
>> 
>> 

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[OmPrakash Muppirala]

Dany,

I haven't tested this on a Mac.  I am told that Mac users need to use "sudo
install npm  " depending on how they installed npm.  Perhaps
you can try that out?

Thanks,
Om

On Mon, Apr 30, 2018 at 12:54 AM, Dany Dhondt  wrote:

> Hi Om,
>
> Thanks for pointing that out.
>
> I’ll have a go with that scenario.
>
> 1. (re) installing royale
> npm install @apache-royale/royale-js -g
> WARN tar invalid entry extract:@apache-royale/royale-js: verb lock using
> /Users/dany/.npm/_locks/staging-3a08f0df5026584d.lock for
> /usr/local/lib/node_modules/.staging
> WARN tar invalid entry
>
> Then hundreds of ‘invalid entry’ lines in the terminal.
>
> And finally
>
> …
>
> WARN tar invalid entry
> /usr/local/bin/asjscompc -> /usr/local/lib/node_modules/@
> apache-royale/royale-js/royale-asjs/js/bin/asjscompcnpm
> /usr/local/bin/asjsc -> /usr/local/lib/node_modules/@
> apache-royale/royale-js/royale-asjs/js/bin/asjscnpm
> /usr/local/bin/compc -> /usr/local/lib/node_modules/@
> apache-royale/royale-js/royale-asjs/js/bin/compcnpm
> /usr/local/bin/externc -> /usr/local/lib/node_modules/@
> apache-royale/royale-js/royale-asjs/js/bin/externcnpm
> /usr/local/bin/asnodec -> /usr/local/lib/node_modules/@
> apache-royale/royale-js/royale-asjs/js/bin/asnodecnpm
> /usr/local/bin/mxmlc -> /usr/local/lib/node_modules/@
> apache-royale/royale-js/royale-asjs/js/bin/mxmlcnpm
> + @apache-royale/royale-js@0.9.3
> updated 1 package in 17.395s
>
>
> What are those invalid entries??
>
> 2. install cli tool
>
> npm install @apache-royale/cli@alpha -g
> no problem here
>
> 3. create royale app
>
> royale new helloWorld
> cd helloWorld
>
> >> no problem
>
> 4. running the app
>
> royale serve:debug
>
> Didn’t work:
>
> helloWorld dany$  > royale serve:debug
> Compiling...
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.common.base.internal.Finalizer
> (file:/usr/local/lib/node_modules/@apache-royale/royale-
> js/royale-asjs/js/lib/guava.jar) to field java.lang.Thread.
> inheritableThreadLocals
> WARNING: Please consider reporting this to the maintainers of
> com.google.common.base.internal.Finalizer
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Error: unable to open 'HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/src/Main.
> mxml'.
>
>
>
> Command failed: mxmlc /Volumes/Macintosh HD/Documents/ARCHEMEDIA/
> ROYALE/helloWorld/src/Main.mxml -debug=true
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.common.base.internal.Finalizer
> (file:/usr/local/lib/node_modules/@apache-royale/royale-
> js/royale-asjs/js/lib/guava.jar) to field java.lang.Thread.
> inheritableThreadLocals
> WARNING: Please consider reporting this to the maintainers of
> com.google.common.base.internal.Finalizer
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Error: unable to open 'HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/src/Main.
> mxml'.
>
>
>
>
> fs.js:646
>   return binding.open(pathModule._makeLong(path), stringToFlags(flags),
> mode);
>  ^
>
> Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
> HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/bin/js-debug/index.html'
> at Object.fs.openSync (fs.js:646:18)
> at Object.fs.readFileSync (fs.js:551:33)
> at updateIndex (/usr/local/lib/node_modules/@
> apache-royale/cli/index.js:125:24)
> at compileDebug (/usr/local/lib/node_modules/@
> apache-royale/cli/index.js:106:9)
> at serveDebug (/usr/local/lib/node_modules/@
> apache-royale/cli/index.js:88:5)
> at Object. (/usr/local/lib/node_modules/@
> apache-royale/cli/index.js:59:13)
> at Module._compile (module.js:652:30)
> at Object.Module._extensions..js (module.js:663:10)
> at Module.load (module.js:565:32)
> at tryModuleLoad (module.js:505:12)
> helloWorld dany$  >
>
>
>
>
> Any ideas?
>
> -Dany
>
>
>
>
>

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[Dany Dhondt]

Hi Om,

Thanks for pointing that out.

I’ll have a go with that scenario.

1. (re) installing royale
npm install @apache-royale/royale-js -g
WARN tar invalid entry extract:@apache-royale/royale-js: verb lock using 
/Users/dany/.npm/_locks/staging-3a08f0df5026584d.lock for 
/usr/local/lib/node_modules/.staging
WARN tar invalid entry

Then hundreds of ‘invalid entry’ lines in the terminal.

And finally

…

WARN tar invalid entry
/usr/local/bin/asjscompc -> 
/usr/local/lib/node_modules/@apache-royale/royale-js/royale-asjs/js/bin/asjscompcnpm
/usr/local/bin/asjsc -> 
/usr/local/lib/node_modules/@apache-royale/royale-js/royale-asjs/js/bin/asjscnpm
/usr/local/bin/compc -> 
/usr/local/lib/node_modules/@apache-royale/royale-js/royale-asjs/js/bin/compcnpm
/usr/local/bin/externc -> 
/usr/local/lib/node_modules/@apache-royale/royale-js/royale-asjs/js/bin/externcnpm
/usr/local/bin/asnodec -> 
/usr/local/lib/node_modules/@apache-royale/royale-js/royale-asjs/js/bin/asnodecnpm
/usr/local/bin/mxmlc -> 
/usr/local/lib/node_modules/@apache-royale/royale-js/royale-asjs/js/bin/mxmlcnpm
+ @apache-royale/royale-js@0.9.3
updated 1 package in 17.395s


What are those invalid entries??

2. install cli tool

npm install @apache-royale/cli@alpha -g
no problem here

3. create royale app

royale new helloWorld
cd helloWorld

>> no problem

4. running the app

royale serve:debug

Didn’t work:

helloWorld dany$  > royale serve:debug
Compiling...
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.common.base.internal.Finalizer 
(file:/usr/local/lib/node_modules/@apache-royale/royale-js/royale-asjs/js/lib/guava.jar)
 to field java.lang.Thread.inheritableThreadLocals
WARNING: Please consider reporting this to the maintainers of 
com.google.common.base.internal.Finalizer
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
Error: unable to open 'HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/src/Main.mxml'.



Command failed: mxmlc /Volumes/Macintosh 
HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/src/Main.mxml -debug=true
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.common.base.internal.Finalizer 
(file:/usr/local/lib/node_modules/@apache-royale/royale-js/royale-asjs/js/lib/guava.jar)
 to field java.lang.Thread.inheritableThreadLocals
WARNING: Please consider reporting this to the maintainers of 
com.google.common.base.internal.Finalizer
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
Error: unable to open 'HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/src/Main.mxml'.




fs.js:646
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
 ^

Error: ENOENT: no such file or directory, open '/Volumes/Macintosh 
HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/bin/js-debug/index.html'
at Object.fs.openSync (fs.js:646:18)
at Object.fs.readFileSync (fs.js:551:33)
at updateIndex 
(/usr/local/lib/node_modules/@apache-royale/cli/index.js:125:24)
at compileDebug 
(/usr/local/lib/node_modules/@apache-royale/cli/index.js:106:9)
at serveDebug (/usr/local/lib/node_modules/@apache-royale/cli/index.js:88:5)
at Object. 
(/usr/local/lib/node_modules/@apache-royale/cli/index.js:59:13)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
helloWorld dany$  > 




Any ideas?

-Dany

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[Olaf Krueger]

>...I would like to see it posted with a big button at the end saying ‘TRY
ROYALE NOW' 

Additionally to what Om said, we're also working on a browser app which will
let you try out Apache Royale in the browser online:
Write MXML/AS3 and click just one button in order to compile your code and
to display the result.

But keep in mind that it is all volunteer-driven here, so it takes its
time...

Thanks,
Olaf




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

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[Olaf Krueger]

Hi Jerry,
it seems to me that you already answered to our draft of the "Life after
FlashPlayer" post which will be published on the Flex lists soon.
So, first thanks for your feedback!
It would be great if you would post your thoughts on the upcoming "Life
after FlashPlayer" thread again as soon as it is published on the Flex
lists.

Thanks,
Olaf




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

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[Olaf Krueger]

Hi Alex,
good idea, I've revised the draft [1].
If there aren't any objections, I'll post this at dev@flex and users@flex in
about 24 hours.

Thanks,
Olaf
   

[1] 
Life after FlashPlayer, are you prepared? 

Hello from the Apache Royale (FlexJS) team,

even if Flex with AIR is still an awesome and outstanding technology, Flex 
in the browser ends with the end of FlashPlayer in 2020. 
To be clear: There will be no way to run your Flex apps in current browser 
versions around 2020! 

The Flex mailing lists are followed by a few hundred people and we assume
that there are still a lot of Flex browser apps out there. 

So, we are really interested in what you are planning to do with your Flex 
apps, e.g. 

- Do you need to stick with the browser at all? 
- Do you plan to migrate your Flex apps to whatever other technology? 
- Did you already migrate your Flex apps to whatever other technology? 
- ... 

If you are reading this post and have a Flex app, please speak up about what 
your plans are!

Thanks,
The Apache Royale (FlexJS) team



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

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[OmPrakash Muppirala]

On Sun, Apr 29, 2018 at 3:50 AM, Dany Dhondt  wrote:

> Hi all,
>
> A few thoughts:
>
>
> In our organization, I built a big backoffice web application in Flex
> about 2 years ago. Now, we are obliged to make it future proof, which
> means, no Flash dependency at all.
> We chose react.js. So the last couple of months, I studied react, npm,
> node, webpack, babel, …
> It’s clear that the most popular technologies for creating web
> applications nowadays are cli driven packages like react, angular, (vue)
> I really think royale should be in this list!
> The whole thing is about getting people up and running in no time. And
> getting started quickly is all about configuration.
> An example: for react, a npm package create-react-app is available which
> is as simple as:
>
> create-react-app my-app
> cd my-app
> yarn start (or npm start)
>
> These commands setup a whole file structure, configures webpack and babel,
> runs a local dev server and start up a boilerplate app. Ready to go!
>
> couldn’t we make a create-royale-app package?
>
>
We do have such a thing.  Please check out the royale cli tool.
Setup instructions here:
https://github.com/apache/royale-asjs/tree/develop/npm/cli
I think it does what you are asking for and more :-)  For example, it
monitors your src folder and recompiles the Royale app and reloads the
browser as well!

One of these days we need to make a blog post about this.  I would really
really like feedback so we can make this tool better.




> This boilerplate could contain a ready-to-go set of components:
> Navigationheader on top, then a left pane and content pane, which are
> responsive and a set of basic components like drop down, button, list, …
>
> All this packed with a clean but robust set of css styling.
>

Right now, the cli installs a very simple hello-world app.  I am planning
on replacing this with a Jewel themed app soon.  Volunteers are more than
welcome to help out here.


>
> I spent the last couple of days searching for a component library for
> react. A few examples: material-ui, React bootstrap, Ant design, Blueprint,
> …
> So far I didn’t find any package which meet my 2 most important criteria:
>
> - Complete set of components
> - Well written component api documentation
>
> I think that a lot of (former) flex developers chose a similar path like
> me but are more than willing to give royale a go.
>
> It is important to know that the majority of these developers (like
> myself) have quite a lot of ‘development skills and experience’ but have
> far less knowledge of what’s going on under the hood.
> We can’t expect them to go through days of configuration frustrations
> before getting started with what is their core business.
>
> So, as much as I agree with the ‘Life after FlashPlayer’ questionnaire, I
> would like to see it posted with a big button at the end saying ‘TRY ROYALE
> NOW'
>
>
> -Dany
>
>
>
>
>
> > Op 29 apr. 2018, om 10:52 heeft Piotr Zarzycki <
> piotrzarzyck...@gmail.com> het volgende geschreven:
> >
> > +1 for Olaf's email and Alex's changes.
> >
> > Piotr
> >
> > On Sun, Apr 29, 2018, 7:15 AM Alex Harui 
> wrote:
> >
> >> Hi Olaf,
> >>
> >> Great first draft!  It is fine as is, and I really like that it is
> short.
> >>
> >> The only thing I'm tempted to try to add is an earlier introduction to
> who
> >> "we" are, that it is the Royale/FlexJS folks asking and not the Flex
> PMC or
> >> some other group.
> >>
> >> So one idea is to just to start with "Hello from the Royale (FlexJS)
> team"
> >> instead of "Hi".
> >> Or enhancing "So, we are really interested..." with "So, we, the Royale
> >> (FlexJS) team, are really interested..."
> >>
> >> My 2 cents,
> >> -Alex
> >>
> >> On 4/28/18, 1:11 PM, "Olaf Krueger"  wrote:
> >>
> >>   Hi,
> >>
> >>> IMO, we don’t need a survey, just the right words in the subject and
> >> body
> >>> of emails that will start > > > discussion and elicit responses...
> >>
> >>   After thinking about it a bit more I came to the conclusion that
> >> there's no
> >>   need to mention Royale as an alternative to Flex in order to start a
> >>   discussion.
> >>   I guess what we all want to know is what all those Flex users and apps
> >> are
> >>   doing out there.
> >>   So I've focused on this and wrote a first draft [1], please take a
> >> look at
> >>   it and make your comments.
> >>   Feel free to revise it.
> >>
> >>   Thanks,
> >>   Olaf
> >>
> >>
> >>   [1]
> >>
> >>   Life after FlashPlayer, are you prepared?
> >>
> >>   Hi,
> >>   even if Flex with AIR is still an awesome and outstanding technology,
> >> Flex
> >>   in the browser ends with the end of FlashPlayer in 2020.
> >>   To be clear: There will be no way to run your Flex apps in current
> >> Browser
> >>   versions around 2020!
> >>
> >>   The Flex mailing lists are followed by a few hundred people and we
> >> assume
> >>   that there are still a lot of Flex browser apps out there.
> >>
> 

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[Dany Dhondt]

Hi all,

A few thoughts:


In our organization, I built a big backoffice web application in Flex about 2 
years ago. Now, we are obliged to make it future proof, which means, no Flash 
dependency at all.
We chose react.js. So the last couple of months, I studied react, npm, node, 
webpack, babel, …
It’s clear that the most popular technologies for creating web applications 
nowadays are cli driven packages like react, angular, (vue)
I really think royale should be in this list!
The whole thing is about getting people up and running in no time. And getting 
started quickly is all about configuration. 
An example: for react, a npm package create-react-app is available which is as 
simple as:

create-react-app my-app
cd my-app
yarn start (or npm start)

These commands setup a whole file structure, configures webpack and babel, runs 
a local dev server and start up a boilerplate app. Ready to go!

couldn’t we make a create-royale-app package?

This boilerplate could contain a ready-to-go set of components:
Navigationheader on top, then a left pane and content pane, which are 
responsive and a set of basic components like drop down, button, list, …

All this packed with a clean but robust set of css styling.

I spent the last couple of days searching for a component library for react. A 
few examples: material-ui, React bootstrap, Ant design, Blueprint, …
So far I didn’t find any package which meet my 2 most important criteria:

- Complete set of components
- Well written component api documentation

I think that a lot of (former) flex developers chose a similar path like me but 
are more than willing to give royale a go. 

It is important to know that the majority of these developers (like myself) 
have quite a lot of ‘development skills and experience’ but have far less 
knowledge of what’s going on under the hood. 
We can’t expect them to go through days of configuration frustrations before 
getting started with what is their core business.

So, as much as I agree with the ‘Life after FlashPlayer’ questionnaire, I would 
like to see it posted with a big button at the end saying ‘TRY ROYALE NOW'


-Dany





> Op 29 apr. 2018, om 10:52 heeft Piotr Zarzycki  
> het volgende geschreven:
> 
> +1 for Olaf's email and Alex's changes.
> 
> Piotr
> 
> On Sun, Apr 29, 2018, 7:15 AM Alex Harui  wrote:
> 
>> Hi Olaf,
>> 
>> Great first draft!  It is fine as is, and I really like that it is short.
>> 
>> The only thing I'm tempted to try to add is an earlier introduction to who
>> "we" are, that it is the Royale/FlexJS folks asking and not the Flex PMC or
>> some other group.
>> 
>> So one idea is to just to start with "Hello from the Royale (FlexJS) team"
>> instead of "Hi".
>> Or enhancing "So, we are really interested..." with "So, we, the Royale
>> (FlexJS) team, are really interested..."
>> 
>> My 2 cents,
>> -Alex
>> 
>> On 4/28/18, 1:11 PM, "Olaf Krueger"  wrote:
>> 
>>   Hi,
>> 
>>> IMO, we don’t need a survey, just the right words in the subject and
>> body
>>> of emails that will start > > > discussion and elicit responses...
>> 
>>   After thinking about it a bit more I came to the conclusion that
>> there's no
>>   need to mention Royale as an alternative to Flex in order to start a
>>   discussion.
>>   I guess what we all want to know is what all those Flex users and apps
>> are
>>   doing out there.
>>   So I've focused on this and wrote a first draft [1], please take a
>> look at
>>   it and make your comments.
>>   Feel free to revise it.
>> 
>>   Thanks,
>>   Olaf
>> 
>> 
>>   [1]
>> 
>>   Life after FlashPlayer, are you prepared?
>> 
>>   Hi,
>>   even if Flex with AIR is still an awesome and outstanding technology,
>> Flex
>>   in the browser ends with the end of FlashPlayer in 2020.
>>   To be clear: There will be no way to run your Flex apps in current
>> Browser
>>   versions around 2020!
>> 
>>   The Flex mailing lists are followed by a few hundred people and we
>> assume
>>   that there are still a lot of Flex browser apps out there.
>> 
>>   So, we are really interested in what you are planning to do with your
>> Flex
>>   apps, e.g.
>> 
>>   - Do you need to stick with the browser at all?
>>   - Do you plan to migrate your Flex apps to whatever other technology?
>>   - Did you already migrate your Flex apps to whatever other technology?
>>   - ...
>> 
>>   If you are reading this post and have a Flex app, please speak up
>> about what
>>   your plans are.
>> 
>>   Thanks,
>>   Olaf
>>   On behalf of the Apache Royale (FlexJS) PMC
>> 
>> 
>> 
>> 
>>   --
>>   Sent from:
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F=02%7C01%7Caharui%40adobe.com%7C3e3259b920be40097fca08d5ad442a1f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636605430693133595=Rc1UvmlbDwC2clAZc2nFAijvr6kaVrJtlOhlk2e1mr0%3D=0
>> 
>> 
>> 

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[Piotr Zarzycki]

+1 for Olaf's email and Alex's changes.

Piotr

On Sun, Apr 29, 2018, 7:15 AM Alex Harui  wrote:

> Hi Olaf,
>
> Great first draft!  It is fine as is, and I really like that it is short.
>
> The only thing I'm tempted to try to add is an earlier introduction to who
> "we" are, that it is the Royale/FlexJS folks asking and not the Flex PMC or
> some other group.
>
> So one idea is to just to start with "Hello from the Royale (FlexJS) team"
> instead of "Hi".
> Or enhancing "So, we are really interested..." with "So, we, the Royale
> (FlexJS) team, are really interested..."
>
> My 2 cents,
> -Alex
>
> On 4/28/18, 1:11 PM, "Olaf Krueger"  wrote:
>
> Hi,
>
> > IMO, we don’t need a survey, just the right words in the subject and
> body
> > of emails that will start > > > discussion and elicit responses...
>
> After thinking about it a bit more I came to the conclusion that
> there's no
> need to mention Royale as an alternative to Flex in order to start a
> discussion.
> I guess what we all want to know is what all those Flex users and apps
> are
> doing out there.
> So I've focused on this and wrote a first draft [1], please take a
> look at
> it and make your comments.
> Feel free to revise it.
>
> Thanks,
> Olaf
>
>
> [1]
>
> Life after FlashPlayer, are you prepared?
>
> Hi,
> even if Flex with AIR is still an awesome and outstanding technology,
> Flex
> in the browser ends with the end of FlashPlayer in 2020.
> To be clear: There will be no way to run your Flex apps in current
> Browser
> versions around 2020!
>
> The Flex mailing lists are followed by a few hundred people and we
> assume
> that there are still a lot of Flex browser apps out there.
>
> So, we are really interested in what you are planning to do with your
> Flex
> apps, e.g.
>
> - Do you need to stick with the browser at all?
> - Do you plan to migrate your Flex apps to whatever other technology?
> - Did you already migrate your Flex apps to whatever other technology?
> - ...
>
> If you are reading this post and have a Flex app, please speak up
> about what
> your plans are.
>
> Thanks,
> Olaf
> On behalf of the Apache Royale (FlexJS) PMC
>
>
>
>
> --
> Sent from:
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F=02%7C01%7Caharui%40adobe.com%7C3e3259b920be40097fca08d5ad442a1f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636605430693133595=Rc1UvmlbDwC2clAZc2nFAijvr6kaVrJtlOhlk2e1mr0%3D=0
>
>
>

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[Alex Harui]

Hi Olaf,

Great first draft!  It is fine as is, and I really like that it is short.

The only thing I'm tempted to try to add is an earlier introduction to who "we" 
are, that it is the Royale/FlexJS folks asking and not the Flex PMC or some 
other group.

So one idea is to just to start with "Hello from the Royale (FlexJS) team" 
instead of "Hi".
Or enhancing "So, we are really interested..." with "So, we, the Royale 
(FlexJS) team, are really interested..."

My 2 cents,
-Alex

On 4/28/18, 1:11 PM, "Olaf Krueger"  wrote:

Hi,

> IMO, we don’t need a survey, just the right words in the subject and body
> of emails that will start > > > discussion and elicit responses...

After thinking about it a bit more I came to the conclusion that there's no
need to mention Royale as an alternative to Flex in order to start a
discussion.
I guess what we all want to know is what all those Flex users and apps are
doing out there.
So I've focused on this and wrote a first draft [1], please take a look at
it and make your comments.
Feel free to revise it.

Thanks,
Olaf


[1]

Life after FlashPlayer, are you prepared?

Hi,
even if Flex with AIR is still an awesome and outstanding technology, Flex
in the browser ends with the end of FlashPlayer in 2020.
To be clear: There will be no way to run your Flex apps in current Browser
versions around 2020! 

The Flex mailing lists are followed by a few hundred people and we assume
that there are still a lot of Flex browser apps out there.

So, we are really interested in what you are planning to do with your Flex
apps, e.g.

- Do you need to stick with the browser at all?
- Do you plan to migrate your Flex apps to whatever other technology?
- Did you already migrate your Flex apps to whatever other technology?
- ...

If you are reading this post and have a Flex app, please speak up about what
your plans are.

Thanks,
Olaf
On behalf of the Apache Royale (FlexJS) PMC




--
Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F=02%7C01%7Caharui%40adobe.com%7C3e3259b920be40097fca08d5ad442a1f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636605430693133595=Rc1UvmlbDwC2clAZc2nFAijvr6kaVrJtlOhlk2e1mr0%3D=0

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[jerryha...@vdex.com]

Here are a few points that may or may not help:

1- I was a long time Flex Developer 
2- I do not have an app in either app store
3- The Flex market moved away from me, thanks to Steve Jobs, Adobe and other 
factors
4- I’m now doing Swift development for mobile (soon will start an Android 
(Kotlin) version of the app)
5- I miss using Flex and hope Royale becomes a good replacement (hurry up, 
things are falling out of my brain everyday)
6- Only so many hours in a day to learn everything, would like to move to 
Royale for cross platform apps and web  development
7- Can’t participate in the Royale development because I’m spending too much 
time learning Swift, Android and somethings Bootstrap with Javascript

Hope this helps,
Jerry Hamby

> On Apr 28, 2018, at 4:10 PM, Olaf Krueger  wrote:
> 
> Hi,
> 
>> IMO, we don’t need a survey, just the right words in the subject and body
>> of emails that will start > > > discussion and elicit responses...
> 
> After thinking about it a bit more I came to the conclusion that there's no
> need to mention Royale as an alternative to Flex in order to start a
> discussion.
> I guess what we all want to know is what all those Flex users and apps are
> doing out there.
> So I've focused on this and wrote a first draft [1], please take a look at
> it and make your comments.
> Feel free to revise it.
> 
> Thanks,
> Olaf
> 
> 
> [1]
> 
> Life after FlashPlayer, are you prepared?
> 
> Hi,
> even if Flex with AIR is still an awesome and outstanding technology, Flex
> in the browser ends with the end of FlashPlayer in 2020.
> To be clear: There will be no way to run your Flex apps in current Browser
> versions around 2020! 
> 
> The Flex mailing lists are followed by a few hundred people and we assume
> that there are still a lot of Flex browser apps out there.
> 
> So, we are really interested in what you are planning to do with your Flex
> apps, e.g.
> 
> - Do you need to stick with the browser at all?
> - Do you plan to migrate your Flex apps to whatever other technology?
> - Did you already migrate your Flex apps to whatever other technology?
> - ...
> 
> If you are reading this post and have a Flex app, please speak up about what
> your plans are.
> 
> Thanks,
> Olaf
> On behalf of the Apache Royale (FlexJS) PMC
> 
> 
> 
> 
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/

[Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[Olaf Krueger]

Hi,

> IMO, we don’t need a survey, just the right words in the subject and body
> of emails that will start > > > discussion and elicit responses...

After thinking about it a bit more I came to the conclusion that there's no
need to mention Royale as an alternative to Flex in order to start a
discussion.
I guess what we all want to know is what all those Flex users and apps are
doing out there.
So I've focused on this and wrote a first draft [1], please take a look at
it and make your comments.
Feel free to revise it.

Thanks,
Olaf


[1]

Life after FlashPlayer, are you prepared?

Hi,
even if Flex with AIR is still an awesome and outstanding technology, Flex
in the browser ends with the end of FlashPlayer in 2020.
To be clear: There will be no way to run your Flex apps in current Browser
versions around 2020! 

The Flex mailing lists are followed by a few hundred people and we assume
that there are still a lot of Flex browser apps out there.

So, we are really interested in what you are planning to do with your Flex
apps, e.g.

- Do you need to stick with the browser at all?
- Do you plan to migrate your Flex apps to whatever other technology?
- Did you already migrate your Flex apps to whatever other technology?
- ...

If you are reading this post and have a Flex app, please speak up about what
your plans are.

Thanks,
Olaf
On behalf of the Apache Royale (FlexJS) PMC




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