Re: Language improvements

2019-05-28 Thread 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

Re: Language improvements

2019-05-28 Thread 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

Re: Language improvements

2019-05-28 Thread 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

Re: Language improvements

2019-05-28 Thread 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)?.

Re: Language improvements

2019-05-28 Thread 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

Re: Language improvements

2019-05-28 Thread 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

Royale_Release_Step_009 - Build # 5 - Failure!

2019-05-28 Thread 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.

Royale_Release_Step_009 - Build # 6 - Still Failing!

2019-05-28 Thread 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.

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

2019-05-28 Thread 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

Release Step 008 Succeeded

2019-05-28 Thread 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.

Build failed in Jenkins: royale-asjs_MXTests #821

2019-05-28 Thread 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

Release Step 007 Succeeded

2019-05-28 Thread 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

Re: 0.9.6 Release

2019-05-28 Thread 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

Build failed in Jenkins: royale-asjs_MXTests #820

2019-05-28 Thread Apache Royale CI Server
See -- [...truncated 2.09 MB...] [mxmlc] using source file:

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

2019-05-28 Thread 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

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

2019-05-28 Thread 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

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

2019-05-28 Thread 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

Release Step 001 Succeeded

2019-05-28 Thread 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_Release_Step_001a_If_Utils - Build # 13 - Failure!

2019-05-28 Thread 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.

Royale_Release_Step_001a_If_Utils - Build # 14 - Still Failing!

2019-05-28 Thread 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.

Release Step 001a Succeeded

2019-05-28 Thread 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.

Release Step 002 Succeeded

2019-05-28 Thread 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 003 Succeeded

2019-05-28 Thread 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

Release Step 004 Succeeded

2019-05-28 Thread 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.

Royale_Release_Step_001a_If_Utils - Build # 15 - Still Failing!

2019-05-28 Thread 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.

Release Step 002a Succeeded

2019-05-28 Thread Apache Royale CI Server
Continue on to Release Step 003

Release Step 005 Succeeded

2019-05-28 Thread 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 005a Succeeded

2019-05-28 Thread 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.

Re: Adding Jewel classes to Apache Royale AS3 reference

2019-05-28 Thread 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

Re: Adding Jewel classes to Apache Royale AS3 reference

2019-05-28 Thread 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

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

2019-05-28 Thread 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": {

Release Step 006 Succeeded

2019-05-28 Thread 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: Adding Jewel classes to Apache Royale AS3 reference

2019-05-28 Thread 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