Royale_Release_Step_009 - Build # 6 - Still Failing!

[Apache Royale CI Server]

Royale_Release_Step_009 - Build # 6 - Still Failing:

Check console output at 
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_009/6/
 to view the results.

Royale_Release_Step_009 - Build # 5 - Failure!

[Apache Royale CI Server]

Royale_Release_Step_009 - Build # 5 - Failure:

Check console output at 
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_009/5/
 to view the results.

Release Step 008 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_008 and run the following commands:
git push
git checkout release/0.9.6
git push -u origin release/0.9.6

You will need your Apache/Github username and 2FA token.

Release Step 007 Succeeded

[Apache Royale CI Server]

>From the royale-typedefs repo:
1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.6
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_007_Sign 
-Drelease.version=0.9.6
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_007_Upload 
-Drelease.version=0.9.6
This will upload the signed artifacts to Maven Release Staging.  Do not "Close" 
the staging repository until the other repos have been added.

Re: [royale-asjs] branch develop updated: asdocs: comment some libs that was causing build to fail

[Alex Harui]

Please don't comment out libs.  Please fix the ASDoc in those libs.

Thanks,
-Alex

On 5/28/19, 9:44 AM, "carlosrov...@apache.org"  wrote:

This is an automated email from the ASF dual-hosted git repository.

carlosrovira pushed a commit to branch develop
in repository 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.gitdata=02%7C01%7Caharui%40adobe.com%7Ce1d68e4a34de4488b32508d6e38bcc54%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636946586901013024sdata=AmnyrQoTr%2BWY%2BhcChjWM%2FFcCjw75ixXXdSVMOXUOOC0%3Dreserved=0


The following commit(s) were added to refs/heads/develop by this push:
 new 86aaec6  asdocs: comment some libs that was causing build to fail
86aaec6 is described below

commit 86aaec69118ff6ef392fca882b500f767fe20c49
Author: Carlos Rovira 
AuthorDate: Tue May 28 18:44:22 2019 +0200

asdocs: comment some libs that was causing build to fail
---
 examples/royale/ASDoc/src/main/config/asdoc-js-config.xml  | 14 
+++---
 examples/royale/ASDoc/src/main/config/asdoc-swf-config.xml |  6 +++---
 2 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml 
b/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
index 0ba992b..aa2c983 100644
--- a/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
+++ b/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
@@ -52,7 +52,7 @@
   
   -->
   
-  
${frameworks_dir}/projects/Ace/src/main/royale
+  
   
${frameworks_dir}/projects/Basic/src/main/royale
   
${frameworks_dir}/projects/Binding/src/main/royale
   
${frameworks_dir}/projects/Charts/src/main/royale
@@ -73,9 +73,9 @@
   
${frameworks_dir}/projects/Icons/src/main/royale
   
${frameworks_dir}/projects/Jewel/src/main/royale
   
${frameworks_dir}/projects/JQuery/src/main/royale
-  
${frameworks_dir}/projects/Language/src/main/royale
+  
   
${frameworks_dir}/projects/MaterialDesignLite/src/main/royale
-  
${frameworks_dir}/projects/MXRoyale/src/main/royale
+  
   
${frameworks_dir}/projects/Mobile/src/main/royale
   
${frameworks_dir}/projects/Network/src/main/royale
   
${frameworks_dir}/projects/Reflection/src/main/royale
@@ -147,10 +147,10 @@
 
 
 
-
+
 
 library://ns.apache.org/royale/basic
 
${frameworks_dir}/projects/Basic/src/main/resources/basic-manifest.xml
@@ -223,10 +223,10 @@
 library://ns.apache.org/royale/mdl
 
${frameworks_dir}/projects/MaterialDesignLite/src/main/resources/mdl-manifest.xml
 
-
+
 
 library://ns.apache.org/royale/basic
 
${frameworks_dir}/projects/Mobile/src/main/resources/basic-manifest.xml
diff --git a/examples/royale/ASDoc/src/main/config/asdoc-swf-config.xml 
b/examples/royale/ASDoc/src/main/config/asdoc-swf-config.xml
index e94c975..887fff6 100644
--- a/examples/royale/ASDoc/src/main/config/asdoc-swf-config.xml
+++ b/examples/royale/ASDoc/src/main/config/asdoc-swf-config.xml
@@ -52,7 +52,7 @@
   
   -->
   
-  
${frameworks_dir}/projects/Ace/src/main/royale
+  
   
${frameworks_dir}/projects/Basic/src/main/royale
   
${frameworks_dir}/projects/Binding/src/main/royale
   
${frameworks_dir}/projects/Charts/src/main/royale
@@ -73,9 +73,9 @@
   
${frameworks_dir}/projects/Icons/src/main/royale
   
${frameworks_dir}/projects/Jewel/src/main/royale
   
${frameworks_dir}/projects/JQuery/src/main/royale
-  
${frameworks_dir}/projects/Language/src/main/royale
+  
   
${frameworks_dir}/projects/MaterialDesignLite/src/main/royale
-  
${frameworks_dir}/projects/MXRoyale/src/main/royale
+  
   
${frameworks_dir}/projects/Mobile/src/main/royale
   
${frameworks_dir}/projects/Network/src/main/royale
   
${frameworks_dir}/projects/Reflection/src/main/royale

Build failed in Jenkins: royale-asjs_MXTests #821

[Apache Royale CI Server]

See 


Changes:

[carlosrovira] jewel-alert: fix typo in comment

[carlosrovira] asdocs: comment some libs that was causing build to fail

[carlosrovira] ASDocs: add jewel to "doc-namespaces" and to "doc-sources", but 
still

[carlosrovira] dialogPolyfill: registerDialog needs to be COMPILE::JS

[carlosrovira] ASDocs: remove a Basic duplicate entry and finalize to add Jewel

[carlosrovira] ASDoc: add icons lib

--
[...truncated 2.09 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

Re: Adding Jewel classes to Apache Royale AS3 reference

[Carlos Rovira]

I mean the rest of ASDoc is showing as before, but not Jewel

El mar., 28 may. 2019 a las 19:52, Carlos Rovira ()
escribió:

> Ok,
>
> I tried (we always can revert).
> And I get Jewel showing in ASDoc.
> But, If I click in for example "Card" component I get "Loading..." but
> nothing is showing up
>
> what could be happening?
>
> Thanks
>
> Carlos
>
>
>
>
> El mar., 28 may. 2019 a las 19:43, Carlos Rovira ()
> escribió:
>
>> Hi,
>>
>> I think I get ASDocs building and generating with ANT.
>> Now I need to upload results to website, but this seems not direct.
>> There's some guide, email or something to now what I should overlay in
>> "asdic" folder on the website?
>>
>> I was thinking it should be just upload "bin/bin-release", but I'm seeing
>> contents there seems not all what we have in website (maybe in website we
>> have files that are not needed anymore)
>>
>> Another thing I see in published site is:
>>
>>  - CordovaClasses.js.json <-- this file is not produced by ANT
>>  - CordovaClasses.swf.json.  <-- this file is produced by ANT
>>
>> I always can publish and if things are not as expected revert the change,
>> but hope to be instructed in some basic steps.
>>
>> thanks
>>
>>
>> El vie., 24 may. 2019 a las 20:37, Alex Harui ()
>> escribió:
>>
>>> It appears that the CI build is failing but not reporting a failure.  So
>>> that may also be why you are not getting JSON files on your computers.  A
>>> volunteer is needed to clean up the files that are causing errors.
>>>
>>> I guess that means that nobody is using our ASDoc, since otherwise I
>>> think this would be reported.
>>>
>>>
>>> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/CI/job/Royale_ASDoc_Example/
>>>
>>> -Alex
>>>
>>> On 5/24/19, 9:38 AM, "Carlos Rovira"  wrote:
>>>
>>> Hi Alex, without doubt something for our todo list, but there's many
>>> things
>>> in the plate and maybe other bigger fish to fry for now.
>>> I'll try to run vía ant and see if I can get something generated
>>> that can
>>> be committed to ref site
>>> thanks!
>>>
>>> El vie., 24 may. 2019 a las 18:19, Alex Harui
>>> ()
>>> escribió:
>>>
>>> > Carlos,
>>> >
>>> > When I compare the Ant build to the Maven build, I can see that
>>> the Ant
>>> > build runs the ASDoc compiler to generate the JSON and the Maven
>>> build does
>>> > not.  We definitely need more committers to understand enough of
>>> both Ant
>>> > and Maven so I don't have to do these investigations and have
>>> folks waiting
>>> > on me to do so.
>>> >
>>> > Volunteers are welcome to improve the Maven build by creating a
>>> way to
>>> > call the ASDoc compiler from Maven.
>>> >
>>> > HTH,
>>> > -Alex
>>> >
>>> > On 5/24/19, 3:54 AM, "Carlos Rovira" 
>>> wrote:
>>> >
>>> > Hi Alex,
>>> >
>>> > in my latest commit I added to the files you pointed in your
>>> email the
>>> > missed libraries I detected.
>>> > I build with maven ASDoc app, but I didn't get a delta output.
>>> I was
>>> > expecting some files to commit to reference repo
>>> > Maybe I must run an ANT command line instruction? if so what
>>> should I
>>> > try?
>>> > can you point me to the next steps?
>>> >
>>> > thanks
>>> >
>>> > --
>>> > Carlos Rovira
>>> >
>>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Cbceea294e0914d344f0508d6e06630d3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636943126848010535sdata=wgsVAzxp5ofiT8V4C1s6F%2FZtozBM5O4yrMvvHXf72t8%3Dreserved=0
>>> >
>>> >
>>> >
>>> >
>>>
>>>
>>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

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

Release Step 006 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_006 and run the following commands:
git push
git push origin org.apache.royale.typedefs-0.9.6-rc1

You will need your Apache/Github username and 2FA token.

Re: New article on how to create a desktop app with Apache Royale and ElectronJS

[Antonis Kalodimos]

Thank you for you spended valuable time to help.
I finally made it to compile and worked in vscode with Royale 0.9.6-bin-js
and using hardcoded in asconfig.json for the path for the jewel theme
pointning to  the apache-royale-0.9.6-bin-js-swf

below the asconfig.used

{
"compilerOptions": {
"source-map": true,
"html-template": "index.html",
"theme":
"D:/ApacheFlex/apache-royale-0.9.6-bin-js-swf/royale-asjs/frameworks/themes/JewelTheme/src/main/resources/defaults.css"
},
"additionalOptions": "-warn-public-vars=false",
"files": [
"src/Helloworld.mxml"
],
"targets": [
"JSRoyale"
]
}



Στις Τρί, 28 Μαΐ 2019 στις 4:23 μ.μ., ο/η Carlos Rovira <
carlosrov...@apache.org> έγραψε:

> Thanks for sharing Piotr!
> Great it working for you too! :)
>
> El mar., 28 may. 2019 a las 15:00, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Antonis,
> >
> > I took some time and I have created this example using Moonshine Jewel
> > Hello World. Basically I have created new project and added steps related
> > to Electron and I was able to run it using console window. If you are
> > interested - Example is here with instruction. [1][2]
> > Currently for some reason I cannot download Nightly build of Royale cause
> > Jenkins doesn't work, but I hope Alex launch it today.
> >
> > Judah,
> >
> > Great work!
> >
> > I bump into a small issue - When I copied content of main.js file it
> failed
> > launch application initially due to some characters -> () = {
> >
> > [1]
> https://github.com/prominic/Royale-Examples/tree/master/ElectronRoyale
> > [2]
> >
> >
> https://github.com/prominic/Royale-Examples/blob/master/ElectronRoyale/README.md
> >
> > Thanks,
> > Piotr
> >
> >
> >
> > pon., 27 maj 2019 o 20:40 Antonis Kalodimos  >
> > napisał(a):
> >
> > > Yes i didn't send you the whole file i was the end part only
> > > The whole part is from this page
> > >
> > >
> >
> https://royale.codeoscopic.com/how-to-create-a-desktop-application-with-royale-and-electron/
> > >  the same as in this page the HelloWorld.mxml and above
> > > thetag im inserted the script showed in the same
> > page.
> > >
> > > The first error i found during truing to compile is from this line
> showed
> > > in the example
> > >
> > >  > > this
> > > http://ns.adobe.com/mxml/2009;
> > >
> > > after the build task know with  apache-royale-0.9.4-bin-js  usedfor
> > > building i am receiving this in log  shoewd in terminal vscode window
> > >
> > > last lines
> > > using source file:
> > > c:\Works\NodeWorks\myElectron02\bin\js-debug\HelloWorld.js
> > > The project 'HelloWorld' has been successfully compiled and optimized.
> > > Error: File not found:
> org.apache.royale.events.utils.MouseEventConverter
> > >
> > > 90.8037847 seconds
> > > The terminal process terminated with exit code: 3
> > >
> > > Terminal will be reused by tasks, press any key to close it.
> > >
> > >
> > > Στις Δευ, 27 Μαΐ 2019 στις 9:08 μ.μ., ο/η Harbs  >
> > > έγραψε:
> > >
> > > > The XML is likely not well formed.
> > > >
> > > > Is the opening tag  or  ?
> > > >
> > > > > On May 27, 2019, at 8:47 PM, Antonis Kalodimos <
> > > > antonis.kalodi...@gmail.com> wrote:
> > > > >
> > > > > Yes i had this tag
> > > > > .
> > > > > .
> > > > > .
> > > > >
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > >
> > > > > I found that i was trying to compile it with
> > > > apache-royale-0.9.6-bin-js-swf
> > > > > when i changed that with apache-royale-0.9.4-bin-js
> > > > > problem resolved but nothing showed (with
> > > apache-royale-0.9.6-bin-js-swf
> > > > > the button and the text was showed.)
> > > > >
> > > > >
> > > > >
> > > > > Στις Δευ, 27 Μαΐ 2019 στις 8:39 μ.μ., ο/η Carlos Rovira <
> > > > > carlosrov...@apache.org> έγραψε:
> > > > >
> > > > >> Hi Antonis,
> > > > >>
> > > > >> are you adding it in the HelloWorld.mxml file
> > > > >> before ?
> > > > >> The error seems like you are trying to add it in other part of the
> > > file
> > > > or
> > > > >> in other different file.
> > > > >>
> > > > >> Thanks
> > > > >>
> > > > >>
> > > > >>
> > > > >> El lun., 27 may. 2019 a las 18:21, Antonis Kalodimos (<
> > > > >> antonis.kalodi...@gmail.com>) escribió:
> > > > >>
> > > > >>> Trying to folow this tutorial have these compile errors after
> > putting
> > > > the
> > > > >>>  tag
> > > > >>> col: 1 Error: This tag is unexpected. It will be ignored.
> > > > >>>
> > > > >>> 
> > > > >>> ^
> > > > >>>
> > > > >>> My code is the same as in the tutorial and it worked as expected
> > > until
> > > > >> the
> > > > >>> step i n which fx:script tag need to be added
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>> Στις Δευ, 27 Μαΐ 2019 στις 6:39 μ.μ., ο/η Carlos Rovira <
> > > > >>> carlosrov...@apache.org> έγραψε:
> > > > >>>
> > > >  Hi,
> > > > 
> > > >  new arcticle from Judah Frangipane is up!
> > > > 
> > > >  https://twitter.com/ApacheRoyale/status/1133025119075479552
> > > > 
> > > >  don't forget to share 

Re: Adding Jewel classes to Apache Royale AS3 reference

[Carlos Rovira]

Ok,

I tried (we always can revert).
And I get Jewel showing in ASDoc.
But, If I click in for example "Card" component I get "Loading..." but
nothing is showing up

what could be happening?

Thanks

Carlos




El mar., 28 may. 2019 a las 19:43, Carlos Rovira ()
escribió:

> Hi,
>
> I think I get ASDocs building and generating with ANT.
> Now I need to upload results to website, but this seems not direct.
> There's some guide, email or something to now what I should overlay in
> "asdic" folder on the website?
>
> I was thinking it should be just upload "bin/bin-release", but I'm seeing
> contents there seems not all what we have in website (maybe in website we
> have files that are not needed anymore)
>
> Another thing I see in published site is:
>
>  - CordovaClasses.js.json <-- this file is not produced by ANT
>  - CordovaClasses.swf.json.  <-- this file is produced by ANT
>
> I always can publish and if things are not as expected revert the change,
> but hope to be instructed in some basic steps.
>
> thanks
>
>
> El vie., 24 may. 2019 a las 20:37, Alex Harui ()
> escribió:
>
>> It appears that the CI build is failing but not reporting a failure.  So
>> that may also be why you are not getting JSON files on your computers.  A
>> volunteer is needed to clean up the files that are causing errors.
>>
>> I guess that means that nobody is using our ASDoc, since otherwise I
>> think this would be reported.
>>
>>
>> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/CI/job/Royale_ASDoc_Example/
>>
>> -Alex
>>
>> On 5/24/19, 9:38 AM, "Carlos Rovira"  wrote:
>>
>> Hi Alex, without doubt something for our todo list, but there's many
>> things
>> in the plate and maybe other bigger fish to fry for now.
>> I'll try to run vía ant and see if I can get something generated that
>> can
>> be committed to ref site
>> thanks!
>>
>> El vie., 24 may. 2019 a las 18:19, Alex Harui
>> ()
>> escribió:
>>
>> > Carlos,
>> >
>> > When I compare the Ant build to the Maven build, I can see that the
>> Ant
>> > build runs the ASDoc compiler to generate the JSON and the Maven
>> build does
>> > not.  We definitely need more committers to understand enough of
>> both Ant
>> > and Maven so I don't have to do these investigations and have folks
>> waiting
>> > on me to do so.
>> >
>> > Volunteers are welcome to improve the Maven build by creating a way
>> to
>> > call the ASDoc compiler from Maven.
>> >
>> > HTH,
>> > -Alex
>> >
>> > On 5/24/19, 3:54 AM, "Carlos Rovira" 
>> wrote:
>> >
>> > Hi Alex,
>> >
>> > in my latest commit I added to the files you pointed in your
>> email the
>> > missed libraries I detected.
>> > I build with maven ASDoc app, but I didn't get a delta output.
>> I was
>> > expecting some files to commit to reference repo
>> > Maybe I must run an ANT command line instruction? if so what
>> should I
>> > try?
>> > can you point me to the next steps?
>> >
>> > thanks
>> >
>> > --
>> > Carlos Rovira
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Cbceea294e0914d344f0508d6e06630d3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636943126848010535sdata=wgsVAzxp5ofiT8V4C1s6F%2FZtozBM5O4yrMvvHXf72t8%3Dreserved=0
>> >
>> >
>> >
>> >
>>
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

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

Re: Adding Jewel classes to Apache Royale AS3 reference

[Carlos Rovira]

Hi,

I think I get ASDocs building and generating with ANT.
Now I need to upload results to website, but this seems not direct.
There's some guide, email or something to now what I should overlay in
"asdic" folder on the website?

I was thinking it should be just upload "bin/bin-release", but I'm seeing
contents there seems not all what we have in website (maybe in website we
have files that are not needed anymore)

Another thing I see in published site is:

 - CordovaClasses.js.json <-- this file is not produced by ANT
 - CordovaClasses.swf.json.  <-- this file is produced by ANT

I always can publish and if things are not as expected revert the change,
but hope to be instructed in some basic steps.

thanks


El vie., 24 may. 2019 a las 20:37, Alex Harui ()
escribió:

> It appears that the CI build is failing but not reporting a failure.  So
> that may also be why you are not getting JSON files on your computers.  A
> volunteer is needed to clean up the files that are causing errors.
>
> I guess that means that nobody is using our ASDoc, since otherwise I think
> this would be reported.
>
>
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/CI/job/Royale_ASDoc_Example/
>
> -Alex
>
> On 5/24/19, 9:38 AM, "Carlos Rovira"  wrote:
>
> Hi Alex, without doubt something for our todo list, but there's many
> things
> in the plate and maybe other bigger fish to fry for now.
> I'll try to run vía ant and see if I can get something generated that
> can
> be committed to ref site
> thanks!
>
> El vie., 24 may. 2019 a las 18:19, Alex Harui
> ()
> escribió:
>
> > Carlos,
> >
> > When I compare the Ant build to the Maven build, I can see that the
> Ant
> > build runs the ASDoc compiler to generate the JSON and the Maven
> build does
> > not.  We definitely need more committers to understand enough of
> both Ant
> > and Maven so I don't have to do these investigations and have folks
> waiting
> > on me to do so.
> >
> > Volunteers are welcome to improve the Maven build by creating a way
> to
> > call the ASDoc compiler from Maven.
> >
> > HTH,
> > -Alex
> >
> > On 5/24/19, 3:54 AM, "Carlos Rovira" 
> wrote:
> >
> > Hi Alex,
> >
> > in my latest commit I added to the files you pointed in your
> email the
> > missed libraries I detected.
> > I build with maven ASDoc app, but I didn't get a delta output. I
> was
> > expecting some files to commit to reference repo
> > Maybe I must run an ANT command line instruction? if so what
> should I
> > try?
> > can you point me to the next steps?
> >
> > thanks
> >
> > --
> > Carlos Rovira
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Cbceea294e0914d344f0508d6e06630d3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636943126848010535sdata=wgsVAzxp5ofiT8V4C1s6F%2FZtozBM5O4yrMvvHXf72t8%3Dreserved=0
> >
> >
> >
> >
>
>
>

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

Release Step 005a Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_005a and run the following commands:
git push

You will need your Apache/Github username and 2FA token.

Release Step 005 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_005 and run the following commands:
git push

You will need your Apache/Github username and 2FA token.

Release Step 004 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_004 and run the following commands:
git push
git checkout release/0.9.6
git push -u origin release/0.9.6

You will need your Apache/Github username and 2FA token.

Release Step 003 Succeeded

[Apache Royale CI Server]

>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and 
compiler-build-tools), Run:
  ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
Otherwise, Run:
 ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_003_Sign 
-Drelease.version=0.9.6
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload 
-Drelease.version=0.9.6
This will upload the signed artifacts to Maven Release Staging.  Do not "Close" 
the staging repository until the other repos have been added.

Release Step 002a Succeeded

[Apache Royale CI Server]

Continue on to Release Step 003

Release Step 002 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands:
git push
git push origin org.apache.royale.compiler-0.9.6-rc1

You will need your Apache/Github username and 2FA token.

Release Step 001a Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_001a_If_Utils and run the following 
commands:
git push

You will need your Apache/Github username and 2FA token.

Royale_Release_Step_001a_If_Utils - Build # 15 - Still Failing!

[Apache Royale CI Server]

Royale_Release_Step_001a_If_Utils - Build # 15 - Still Failing:

Check console output at 
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_001a_If_Utils/15/
 to view the results.

Royale_Release_Step_001a_If_Utils - Build # 14 - Still Failing!

[Apache Royale CI Server]

Royale_Release_Step_001a_If_Utils - Build # 14 - Still Failing:

Check console output at 
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_001a_If_Utils/14/
 to view the results.

Royale_Release_Step_001a_If_Utils - Build # 13 - Failure!

[Apache Royale CI Server]

Royale_Release_Step_001a_If_Utils - Build # 13 - Failure:

Check console output at 
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_001a_If_Utils/13/
 to view the results.

Release Step 001 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands:
git push
git checkout release/0.9.6
git push -u origin release/0.9.6

You will need your Apache/Github username and 2FA token.

Royale's Jenkins Server (was Re: 0.9.6 Release)

[Alex Harui]

Changing the subject as I don't think it is specific to the release.

The server itself seems to be running.  Maybe you saw it was not running during 
a forced OS upgrade?

I have seen that the agent momentarily goes off-line and then comes back on 
again after a few seconds.  It is annoying, but jobs eventually get run, so I 
have not bothered to investigate.

HTH,
-Alex

On 5/28/19, 5:44 AM, "Piotr Zarzycki"  wrote:

Hi Alex,

What is happen with our Jenkins server - is it switched OFF for purpose ? I
see that it is happen every day. Today I'm not sure how it launch again.

Thanks,
Piotr

czw., 23 maj 2019 o 18:54 Alex Harui  napisał(a):

> It has turned out to be harder than expected to get the same binaries on
> Mac and Win.  I now have the identical binaries for royale-compiler and
> royale-typedefs Maven artifacts and am starting on royale-asjs.  I might
> get lucky and the changes that fixed royale-typedefs SWCs will magically
> get the royale-asjs SWCs to match.  Then we have to make the Ant artifacts
> match.
>
> There have been a lot of distractions in my non-work life which has also
> impeded progress.  I hope to make much progress this coming week and if
> we're lucky, I will be asking for a volunteer (or volunteers) to test 
drive
> all of this stuff and be the RM for 0.9.6.  I am not going to be the RM.
>
> -Alex
>
> On 5/23/19, 9:39 AM, "Piotr Zarzycki"  wrote:
>
> Hi Alex,
>
> It's been a while since you have started effort with automating build.
> Where are you with that ? Are we closer to started 0.9.6. Do you need
> any
> help with this ?
>
> Thanks,
> Piotr
>
> wt., 2 kwi 2019 o 19:30 Alex Harui 
> napisał(a):
>
> > Update:
> >
> > In order to make verification of binary release packages created on
> the
> > server easier, I have made changes to our build scripts and tools to
> try to
> > generate reproducible binaries.  I've seen two different builds
> compare on
> > my Mac.   The next challenge will be to see if the server can build 
a
> > package on Windows that will compare on Mac.
> >
> > One of the changes I needed to make is to JBurg.  The version of
> JBurg we
> > use generates method names including a hash that doesn't reproduce
> the same
> > name each time.  I have changes to JBurg ready, however JBurg is
> currently
> > under CPL which is category B.  We only need one file, we don't need
> or
> > want all of JBurg at this time.  The one JBurg file is jointly owned
> by
> > Adobe and Tom Harwood.  I've contact Tom and he will be filing an
> ICLA and
> > has given me permission to commit the lines he owns in that one 
file.
> >
> > This is the revision of the file that will be donated by Tom/Adobe.
> >
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.javadata=02%7C01%7Caharui%40adobe.com%7Cbe81e78f1f7a49f52b5208d6e36a43f9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636946442897729801sdata=d0zcfjhW7DDgwG3Z8wvahl63X3e0ki6bqnH3S2213UI%3Dreserved=0
> >
> > Once this file goes in with the changes to keep the method names the
> same,
> > there will be more tweaks to the release tasks and then we can try
> cutting
> > a release.  I'm thinking we'll be at that point in early May, so now
> is the
> > time to get stuff in for the 0.9.6 release.
> >
> > Thanks,
> > -Alex
> >
> > On 3/8/19, 9:27 AM, "Alex Harui"  wrote:
> >
> > I would much rather have others find and fix issues themselves.
> That
> > way, more people than just me will know how to maintain the system.
> It
> > actually turns out that, IMO, a group of people can work on the
> release.
> > There are 14 steps.  Literally, 14 different people could execute
> one step
> > each.
> >
> > My 2 cents,
> > -Alex
> >
> > On 3/8/19, 2:13 AM, "Carlos Rovira" 
> wrote:
> >
> > Hi Alex,
> >
> > amazing work! congrats to reach to this point! :)
> >
> > I need to put my head on all of this, but count on me to be
> a RM.
> > I think
> > the best thing should be that you be the first RM to try
> your own
> > development at least for the first time, and then the rest
> of us
> > will
> > follow you on the next releases. With all this on place we
> 

Re: New article on how to create a desktop app with Apache Royale and ElectronJS

[Carlos Rovira]

Thanks for sharing Piotr!
Great it working for you too! :)

El mar., 28 may. 2019 a las 15:00, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Hi Antonis,
>
> I took some time and I have created this example using Moonshine Jewel
> Hello World. Basically I have created new project and added steps related
> to Electron and I was able to run it using console window. If you are
> interested - Example is here with instruction. [1][2]
> Currently for some reason I cannot download Nightly build of Royale cause
> Jenkins doesn't work, but I hope Alex launch it today.
>
> Judah,
>
> Great work!
>
> I bump into a small issue - When I copied content of main.js file it failed
> launch application initially due to some characters -> () = {
>
> [1] https://github.com/prominic/Royale-Examples/tree/master/ElectronRoyale
> [2]
>
> https://github.com/prominic/Royale-Examples/blob/master/ElectronRoyale/README.md
>
> Thanks,
> Piotr
>
>
>
> pon., 27 maj 2019 o 20:40 Antonis Kalodimos 
> napisał(a):
>
> > Yes i didn't send you the whole file i was the end part only
> > The whole part is from this page
> >
> >
> https://royale.codeoscopic.com/how-to-create-a-desktop-application-with-royale-and-electron/
> >  the same as in this page the HelloWorld.mxml and above
> > thetag im inserted the script showed in the same
> page.
> >
> > The first error i found during truing to compile is from this line showed
> > in the example
> >
> >  > this
> > http://ns.adobe.com/mxml/2009;
> >
> > after the build task know with  apache-royale-0.9.4-bin-js  usedfor
> > building i am receiving this in log  shoewd in terminal vscode window
> >
> > last lines
> > using source file:
> > c:\Works\NodeWorks\myElectron02\bin\js-debug\HelloWorld.js
> > The project 'HelloWorld' has been successfully compiled and optimized.
> > Error: File not found: org.apache.royale.events.utils.MouseEventConverter
> >
> > 90.8037847 seconds
> > The terminal process terminated with exit code: 3
> >
> > Terminal will be reused by tasks, press any key to close it.
> >
> >
> > Στις Δευ, 27 Μαΐ 2019 στις 9:08 μ.μ., ο/η Harbs 
> > έγραψε:
> >
> > > The XML is likely not well formed.
> > >
> > > Is the opening tag  or  ?
> > >
> > > > On May 27, 2019, at 8:47 PM, Antonis Kalodimos <
> > > antonis.kalodi...@gmail.com> wrote:
> > > >
> > > > Yes i had this tag
> > > > .
> > > > .
> > > > .
> > > >
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >
> > > > I found that i was trying to compile it with
> > > apache-royale-0.9.6-bin-js-swf
> > > > when i changed that with apache-royale-0.9.4-bin-js
> > > > problem resolved but nothing showed (with
> > apache-royale-0.9.6-bin-js-swf
> > > > the button and the text was showed.)
> > > >
> > > >
> > > >
> > > > Στις Δευ, 27 Μαΐ 2019 στις 8:39 μ.μ., ο/η Carlos Rovira <
> > > > carlosrov...@apache.org> έγραψε:
> > > >
> > > >> Hi Antonis,
> > > >>
> > > >> are you adding it in the HelloWorld.mxml file
> > > >> before ?
> > > >> The error seems like you are trying to add it in other part of the
> > file
> > > or
> > > >> in other different file.
> > > >>
> > > >> Thanks
> > > >>
> > > >>
> > > >>
> > > >> El lun., 27 may. 2019 a las 18:21, Antonis Kalodimos (<
> > > >> antonis.kalodi...@gmail.com>) escribió:
> > > >>
> > > >>> Trying to folow this tutorial have these compile errors after
> putting
> > > the
> > > >>>  tag
> > > >>> col: 1 Error: This tag is unexpected. It will be ignored.
> > > >>>
> > > >>> 
> > > >>> ^
> > > >>>
> > > >>> My code is the same as in the tutorial and it worked as expected
> > until
> > > >> the
> > > >>> step i n which fx:script tag need to be added
> > > >>>
> > > >>>
> > > >>>
> > > >>> Στις Δευ, 27 Μαΐ 2019 στις 6:39 μ.μ., ο/η Carlos Rovira <
> > > >>> carlosrov...@apache.org> έγραψε:
> > > >>>
> > >  Hi,
> > > 
> > >  new arcticle from Judah Frangipane is up!
> > > 
> > >  https://twitter.com/ApacheRoyale/status/1133025119075479552
> > > 
> > >  don't forget to share the new tweet please! :)
> > > 
> > >  and enjoy!!
> > > 
> > >  --
> > >  Carlos Rovira
> > >  http://about.me/carlosrovira
> > > 
> > > >>>
> > > >>
> > > >>
> > > >> --
> > > >> Carlos Rovira
> > > >> http://about.me/carlosrovira
> > > >>
> > >
> > >
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


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

Build failed in Jenkins: royale-asjs_MXTests #820

[Apache Royale CI Server]

See 


--
[...truncated 2.09 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

Re: New article on how to create a desktop app with Apache Royale and ElectronJS

[Piotr Zarzycki]

Hi Antonis,

I took some time and I have created this example using Moonshine Jewel
Hello World. Basically I have created new project and added steps related
to Electron and I was able to run it using console window. If you are
interested - Example is here with instruction. [1][2]
Currently for some reason I cannot download Nightly build of Royale cause
Jenkins doesn't work, but I hope Alex launch it today.

Judah,

Great work!

I bump into a small issue - When I copied content of main.js file it failed
launch application initially due to some characters -> () = {

[1] https://github.com/prominic/Royale-Examples/tree/master/ElectronRoyale
[2]
https://github.com/prominic/Royale-Examples/blob/master/ElectronRoyale/README.md

Thanks,
Piotr



pon., 27 maj 2019 o 20:40 Antonis Kalodimos 
napisał(a):

> Yes i didn't send you the whole file i was the end part only
> The whole part is from this page
>
> https://royale.codeoscopic.com/how-to-create-a-desktop-application-with-royale-and-electron/
>  the same as in this page the HelloWorld.mxml and above
> thetag im inserted the script showed in the same page.
>
> The first error i found during truing to compile is from this line showed
> in the example
>
>  this
> http://ns.adobe.com/mxml/2009;
>
> after the build task know with  apache-royale-0.9.4-bin-js  usedfor
> building i am receiving this in log  shoewd in terminal vscode window
>
> last lines
> using source file:
> c:\Works\NodeWorks\myElectron02\bin\js-debug\HelloWorld.js
> The project 'HelloWorld' has been successfully compiled and optimized.
> Error: File not found: org.apache.royale.events.utils.MouseEventConverter
>
> 90.8037847 seconds
> The terminal process terminated with exit code: 3
>
> Terminal will be reused by tasks, press any key to close it.
>
>
> Στις Δευ, 27 Μαΐ 2019 στις 9:08 μ.μ., ο/η Harbs 
> έγραψε:
>
> > The XML is likely not well formed.
> >
> > Is the opening tag  or  ?
> >
> > > On May 27, 2019, at 8:47 PM, Antonis Kalodimos <
> > antonis.kalodi...@gmail.com> wrote:
> > >
> > > Yes i had this tag
> > > .
> > > .
> > > .
> > >
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> > > I found that i was trying to compile it with
> > apache-royale-0.9.6-bin-js-swf
> > > when i changed that with apache-royale-0.9.4-bin-js
> > > problem resolved but nothing showed (with
> apache-royale-0.9.6-bin-js-swf
> > > the button and the text was showed.)
> > >
> > >
> > >
> > > Στις Δευ, 27 Μαΐ 2019 στις 8:39 μ.μ., ο/η Carlos Rovira <
> > > carlosrov...@apache.org> έγραψε:
> > >
> > >> Hi Antonis,
> > >>
> > >> are you adding it in the HelloWorld.mxml file
> > >> before ?
> > >> The error seems like you are trying to add it in other part of the
> file
> > or
> > >> in other different file.
> > >>
> > >> Thanks
> > >>
> > >>
> > >>
> > >> El lun., 27 may. 2019 a las 18:21, Antonis Kalodimos (<
> > >> antonis.kalodi...@gmail.com>) escribió:
> > >>
> > >>> Trying to folow this tutorial have these compile errors after putting
> > the
> > >>>  tag
> > >>> col: 1 Error: This tag is unexpected. It will be ignored.
> > >>>
> > >>> 
> > >>> ^
> > >>>
> > >>> My code is the same as in the tutorial and it worked as expected
> until
> > >> the
> > >>> step i n which fx:script tag need to be added
> > >>>
> > >>>
> > >>>
> > >>> Στις Δευ, 27 Μαΐ 2019 στις 6:39 μ.μ., ο/η Carlos Rovira <
> > >>> carlosrov...@apache.org> έγραψε:
> > >>>
> >  Hi,
> > 
> >  new arcticle from Judah Frangipane is up!
> > 
> >  https://twitter.com/ApacheRoyale/status/1133025119075479552
> > 
> >  don't forget to share the new tweet please! :)
> > 
> >  and enjoy!!
> > 
> >  --
> >  Carlos Rovira
> >  http://about.me/carlosrovira
> > 
> > >>>
> > >>
> > >>
> > >> --
> > >> Carlos Rovira
> > >> http://about.me/carlosrovira
> > >>
> >
> >
>


-- 

Piotr Zarzycki

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

Re: 0.9.6 Release

[Piotr Zarzycki]

Hi Alex,

What is happen with our Jenkins server - is it switched OFF for purpose ? I
see that it is happen every day. Today I'm not sure how it launch again.

Thanks,
Piotr

czw., 23 maj 2019 o 18:54 Alex Harui  napisał(a):

> It has turned out to be harder than expected to get the same binaries on
> Mac and Win.  I now have the identical binaries for royale-compiler and
> royale-typedefs Maven artifacts and am starting on royale-asjs.  I might
> get lucky and the changes that fixed royale-typedefs SWCs will magically
> get the royale-asjs SWCs to match.  Then we have to make the Ant artifacts
> match.
>
> There have been a lot of distractions in my non-work life which has also
> impeded progress.  I hope to make much progress this coming week and if
> we're lucky, I will be asking for a volunteer (or volunteers) to test drive
> all of this stuff and be the RM for 0.9.6.  I am not going to be the RM.
>
> -Alex
>
> On 5/23/19, 9:39 AM, "Piotr Zarzycki"  wrote:
>
> Hi Alex,
>
> It's been a while since you have started effort with automating build.
> Where are you with that ? Are we closer to started 0.9.6. Do you need
> any
> help with this ?
>
> Thanks,
> Piotr
>
> wt., 2 kwi 2019 o 19:30 Alex Harui 
> napisał(a):
>
> > Update:
> >
> > In order to make verification of binary release packages created on
> the
> > server easier, I have made changes to our build scripts and tools to
> try to
> > generate reproducible binaries.  I've seen two different builds
> compare on
> > my Mac.   The next challenge will be to see if the server can build a
> > package on Windows that will compare on Mac.
> >
> > One of the changes I needed to make is to JBurg.  The version of
> JBurg we
> > use generates method names including a hash that doesn't reproduce
> the same
> > name each time.  I have changes to JBurg ready, however JBurg is
> currently
> > under CPL which is category B.  We only need one file, we don't need
> or
> > want all of JBurg at this time.  The one JBurg file is jointly owned
> by
> > Adobe and Tom Harwood.  I've contact Tom and he will be filing an
> ICLA and
> > has given me permission to commit the lines he owns in that one file.
> >
> > This is the revision of the file that will be donated by Tom/Adobe.
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.javadata=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907528095sdata=1p0EhJm%2Be7CdkNlE5MHMEJ9EoPINgBGKVU6hlE8C0kQ%3Dreserved=0
> >
> > Once this file goes in with the changes to keep the method names the
> same,
> > there will be more tweaks to the release tasks and then we can try
> cutting
> > a release.  I'm thinking we'll be at that point in early May, so now
> is the
> > time to get stuff in for the 0.9.6 release.
> >
> > Thanks,
> > -Alex
> >
> > On 3/8/19, 9:27 AM, "Alex Harui"  wrote:
> >
> > I would much rather have others find and fix issues themselves.
> That
> > way, more people than just me will know how to maintain the system.
> It
> > actually turns out that, IMO, a group of people can work on the
> release.
> > There are 14 steps.  Literally, 14 different people could execute
> one step
> > each.
> >
> > My 2 cents,
> > -Alex
> >
> > On 3/8/19, 2:13 AM, "Carlos Rovira" 
> wrote:
> >
> > Hi Alex,
> >
> > amazing work! congrats to reach to this point! :)
> >
> > I need to put my head on all of this, but count on me to be
> a RM.
> > I think
> > the best thing should be that you be the first RM to try
> your own
> > development at least for the first time, and then the rest
> of us
> > will
> > follow you on the next releases. With all this on place we
> maybe
> > could
> > release once a month or every two months...
> >
> > Thanks for doing this :)
> >
> > Carlos
> >
> >
> > El vie., 8 mar. 2019 a las 1:55, Alex Harui
> > ()
> > escribió:
> >
> > > OK, I've now seen Jenkins perform the steps to build the
> release
> > > artifacts.  Folks interested in Docker-izing the steps are
> > welcome to look
> > > at the jobs on the "Royale Release" tab on the CI server.
> > >
> >
> 

Re: Language improvements

[Carlos Rovira]

Hi,

I think that we all agree in most of the things, and although we're
discussing some particularities on how to solve, my opinion is that those
particularities can be solved after merging Language improvements branch.
We all agree we need this Vector (and other improvements in this branch)?.
So, after that merge folks wanting to improve, let's say, Vector(for
example) even more with new choices can do that without problem and will
make it even better.

Are we ok with that?





El mar., 28 may. 2019 a las 11:07, Harbs () escribió:

>
> > On May 28, 2019, at 11:12 AM, Greg Dove  wrote:
> >
> >> "I personally have never used length checking in Vector. Nor was runtime
> >> type checking on Vectors important to me. "
> > length checking is automatic in flash. I don't know that you 'use' it...
> it
> > is just there.
>
> True. What I meant is that I never used fixed length Vectors.
>
> > In javascript I expect it would most often be switched off in all release
> > builds, but having it on by default provides another check of something
> > that could provide a vital clue to help people figuring out problems in
> > code.
> > So far each 'stronger typing' feature added in the last few months has
> > revealed potential issues or - most often - bad code that was working
> when
> > it should not
>
> Good points, and one that argues for the ability to have these checks
> while debugging and have the run-time code removed on release.
>
> > One thing about the mxml stuff is that it gets processed in a way that is
> > untyped.
>
>
> Agree. I do wish there was some way for MXML to be output “better” where
> minified vars could “just work” and types could be better inferred from the
> MXML files.



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

Re: Language improvements

[Harbs]

> On May 28, 2019, at 11:12 AM, Greg Dove  wrote:
> 
>> "I personally have never used length checking in Vector. Nor was runtime
>> type checking on Vectors important to me. "
> length checking is automatic in flash. I don't know that you 'use' it... it
> is just there.

True. What I meant is that I never used fixed length Vectors.

> In javascript I expect it would most often be switched off in all release
> builds, but having it on by default provides another check of something
> that could provide a vital clue to help people figuring out problems in
> code.
> So far each 'stronger typing' feature added in the last few months has
> revealed potential issues or - most often - bad code that was working when
> it should not

Good points, and one that argues for the ability to have these checks while 
debugging and have the run-time code removed on release.

> One thing about the mxml stuff is that it gets processed in a way that is
> untyped.


Agree. I do wish there was some way for MXML to be output “better” where 
minified vars could “just work” and types could be better inferred from the 
MXML files.

Re: Language improvements

[Harbs]

I should have documented the problems at the time. I don’t remember the 
details. :-(

I’m pretty sure it related to the fact that I wanted arrays to be strongly 
typed, but the signatures of where the arrays were coming from were just 
arrays. You can’t just assign arrays (or parts of arrays) to Vectors. Some of 
the issues might have been from arrays which originate in web apis too.

Sorry for being so vague…

Harbs

> On May 28, 2019, at 11:12 AM, Greg Dove  wrote:
> 
> "When I was porting a javascript library for use with Royale, array
> incompatibility with Vector was a pain point. "
> In what way? I'd be keen to understand more what the issues were.

Re: Language improvements

[Harbs]

I looked into this some time ago. Working from memory, non-typed arrays might 
have been even faster than TypedArrays. Why that would be, I can’t guess and I 
could be wrong about that.

I’d be interested in seeing some test results.

Thanks,
Harbs

> On May 28, 2019, at 10:39 AM, Greg Dove  wrote:
> 
> For the TypedArray stuff it really only makes sense as a fixed Vector, not
> as one with fixed=false. I already made some suggestions about these to
> Harbs. Harbs thought the benefits might be dubious because of how
> optimizations work in V8 etc, but I would be surprised if there was not at
> least some small advantage, so I will check and if yes, I will work on that
> regardless.

Re: Language improvements

[Greg Dove]

"The reason I mentioned my desire to have `int[]` and `MyFoo[]` in addition
to Vector was that I thought it might be another solution to this problem. "
I believe it is the better quality solution, yes. It is also one I would be
happy to use.

"I personally have never used length checking in Vector. Nor was runtime
type checking on Vectors important to me. "
length checking is automatic in flash. I don't know that you 'use' it... it
is just there.
In javascript I expect it would most often be switched off in all release
builds, but having it on by default provides another check of something
that could provide a vital clue to help people figuring out problems in
code.
So far each 'stronger typing' feature added in the last few months has
revealed potential issues or - most often - bad code that was working when
it should not
One thing about the mxml stuff is that it gets processed in a way that is
untyped.


"When I was porting a javascript library for use with Royale, array
incompatibility with Vector was a pain point. "
In what way? I'd be keen to understand more what the issues were.

"In short, I want the ability to type check my arrays at compile time and
have them completely compatible with generic arrays (something I’m missing
currently with Vector). I don’t want or need the extra weight.
To me, a good solution would be to have full runtime type checking in
Vector and be able to use “typed” arrays (not to be confused with
TypedArrays) to avoid the runtime weight.
I discussed in the past with Josh the concept of implementing “typed
arrays” in addition to Vectors. Maybe now would be a good time to make that
happen."
Yes this is how Haxe does it too. It would be my preferred 'solution' also

"I do like the concept of optimizing how certain vectors are output (such
as TypedArrays), but that might be something that can happen later."
I am pretty sure I could do this already in the current implementation, but
it would not fully conform because Vector allows switching back and forth
between fixed length and variable length, and I cannot magically transform
a reference to a TypedArray into a regular Array when that happens. It
would only work for numeric vectors that were instantiated with the length
defined and fixed argument as true and you can never change that. If the
instance was passed to other code that believed it was a Vector it has a
false impression of what it is.

"FWIW, most JS engines will automatically use a TypedArray under the hood
if you use an array where all the elements are integers, so there’s not
usually a practical advantage to writing that optimization explicitly. "
Yeah I have read up on the V8 stuff in particular in the past, it's
seriously helpful to all of us. But I would hope there is at least a small
advantage still because TypedArray knows its element type before anything
is added to 'infer' from and the bytes that it uses are pre-allocated. It
might be a small benefit only, but I will still at least check it out.


On Tue, May 28, 2019 at 8:56 AM Harbs  wrote:

> The reason I mentioned my desire to have `int[]` and `MyFoo[]` in addition
> to Vector was that I thought it might be another solution to this problem.
>
> I personally have never used length checking in Vector. Nor was runtime
> type checking on Vectors important to me.
>
> When I was porting a javascript library for use with Royale, array
> incompatibility with Vector was a pain point.
>
> In short, I want the ability to type check my arrays at compile time and
> have them completely compatible with generic arrays (something I’m missing
> currently with Vector). I don’t want or need the extra weight.
>
> To me, a good solution would be to have full runtime type checking in
> Vector and be able to use “typed” arrays (not to be confused with
> TypedArrays) to avoid the runtime weight.
>
> I discussed in the past with Josh the concept of implementing “typed
> arrays” in addition to Vectors. Maybe now would be a good time to make that
> happen.
>
> I do like the concept of optimizing how certain vectors are output (such
> as TypedArrays), but that might be something that can happen later.
>
> FWIW, most JS engines will automatically use a TypedArray under the hood
> if you use an array where all the elements are integers, so there’s not
> usually a practical advantage to writing that optimization explicitly.
>
> My $0.02,
> Harbs
>
> > On May 27, 2019, at 9:43 PM, Alex Harui 
> wrote:
> >
> > Hi Greg,
> >
> > I live outside of Seattle.  I'm in my house right now, and my cellphone
> says I have a 4G connection.  Many times a month, I take a ferry boat to
> Seattle.  There is a point during the ride where the connectivity is poor.
> Yesterday, I was trying to get work done on the ferry and was blocked from
> doing one step in the release automation because it would not load in
> time.  Many times, I'm trying to get one thing finished and get stymied by
> poor connectivity.  I hear this complaint from plenty of other 

Re: Language improvements

[Greg Dove]

Hi Alex,

I think there is probably a difference with patchy connections between
'using an app' (content) and 'installing an app' (download) whether its
mobile, desktop or web.
I suspect that most of the experience you describe is 'using an app'
whether it's git or anything else. And I do understand your frustration as
a user of anything in the scenario described.
I think it is particularly painful if you are doing something that is not
loading web app code from a local browser cache.
I accept that there is always a need for 'size' optimization in general and
there can be specific needs for sure.
What you can be sure of is that the problem with the network access is
going in one direction, and that is away from the 2KB size problem.
I see js apps in gzip sizes now that are not so dissimilar size to flex
apps from 10 years ago. The big difference of course is much more mobile
vs. desktop focus. As I said earlier in the thread, I believe the growth in
bandwidth will continue to outpace the growth in bytesize of web apps.
Perhaps not always their assets or other content, but in the apps
themselves.
Until the next big thing I guess... whatever that is.

But I'm obviously not getting my message through clearly on why I think it
is a bad idea to propagate different versions 'of the same thing'.
1. I am definitely in favor of options, including size based options for
those who need them. We are different in our thinking about priorities...
that's fine and doesn't matter as long as there are options for whoever
thinks whatever is more important.
2. I prefer options that do not have risks to Royale and its future
ecosystem. The possibility to 'break' language level classes and expose
them to others whose view of them remains unbroken is what drives my main
concern. The risk is unknowable at this point but it is also avoidable. I'm
guessing you either don't consider there are risks or you don't think they
are important (relative to other things that you consider more important).
Perhaps you think the risk is avoidable in ways I don't understand. If so,
I am curious to know what they are. But right now I can't think of them,
so...

FWIW I think about XML in exactly the same way as Vector here. It's
language, not application framework.

They are both part of the language layer.
As others have said, Vector and XML are like Date, Number etc. The fact
that that they are 'emulated' in local code should be something to be aware
of, but language is language. It either works as defined or it does not.
In the past we downloaded 'language support' in flash player via its
frequent updates. For Royale we need to download the selective non-native
language pieces we use that deliver that same compatible support along with
app itself.

As a hypothetical, if javascript did not have a Date implementation and
Royale had to (somehow) emulate that as well, I am curious to understand if
you think it would be sensible to encourage multiple non-conforming
implementations of Date (for whatever reason -  better size/performance for
example), given that it also is well specified. Perhaps you do think its
ok, but I would not, and of course Date is not really a problem in
javascript. But that's the same way I think of Vector, and I'm only using
it to illustrate that. If we permit non-conforming implementations, we
should warn people who make libraries not to do certain things (always keep
references of this non-conforming type as 'private' or only use for local
vars etc) otherwise they may expose language level features that will not
be reliable elsewhere, because the alternate 'emulation' of that language
class is baked into the library and can be different to the one used in
other libraries or in the main app.
I'm talking about public swc libraries, not private ones, but even in large
teams it could be important to consider. Providing warnings about these
risks itself seems cumbersome and also has negative connotations.

"My understanding from the words you've written is that you want everyone
to use your Vector implementation and have options on what code paths that
implementation actually takes, but I don't understand why from a technical
perspective."

I don't think of this as 'my' Vector implementation. I do however want
people to be able to use 'our' Vector implementation with confidence, which
is why I posted so much information in this thread and asked others to try
it. Outputting as Array is *not* an implementation of Vector... imo it is a
placeholder waiting for one. Because there is nothing to distinguish it
from a regular Array, at a very basic level it is a misrepresentation of
strong typing.
I'm not sure what you mean by 'technical perspective' here. There could be
some technical issues if there was a need to be able to resolve two or more
conflicting runtime representations of the same type (emulation class 1 in
public library 1, emulation class 2 in public library 2 and default Vector
implementaion in the main app, all with