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

[Apache Royale CI Server]

See 

Release Step 013 Succeeded

[Apache Royale CI Server]

1. Run ant -f releasesteps.xml Release_Step_013 -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_013_Sign 
-Drelease.version=0.9.6
This will PGP sign the source and convenience binary packages
4. Then run ant -f releasesteps.xml Release_Step_013_Upload 
-Drelease.version=0.9.6 -Drc=1
This will upload the signed artifacts to dist.apache.org.

Jenkins build is back to normal : royale-asjs_jsonly #3064

[Apache Royale CI Server]

See 

Royale_Release_Step_013 - Build # 11 - Failure!

[Apache Royale CI Server]

Royale_Release_Step_013 - Build # 11 - Failure:

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

Royale_Release_Step_013 - Build # 10 - Failure!

[Apache Royale CI Server]

Royale_Release_Step_013 - Build # 10 - Failure:

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

Release Step 012 Succeeded

[Apache Royale CI Server]

Folder 0.9.6 already exists.  Continue to next step

RE: Royale Commercial Support Page (was: Fwd: AIR and Royale)

[Frost, Andrew]

Hi

Please count us in! Let me know if you have a length in mind for the 
description, we could expand upon that..


* NAME: HARMAN Connected Services
* SHORT DESCRIPTION (if applies): Software services company with web 
development teams plus background in Adobe technologies
* LOGO (if applies) (PNG, background transparent, good resolution (at least 
above 800px): Can be downloaded from 
https://www.dropbox.com/s/72spasyd5o7f7ok/Harman%20Primary%20Corporate%20Logo%20CMYK.png?dl=0
* WEBSITE URL: https://services.harman.com
* CONTACT PERSON (in case of individual can be same as NAME): Andrew Frost
* EMAIL OF CONTACT: andrew.fr...@harman.com
* PHONE OF CONTACT: +447752 490699
* APACHE ROYALE CONTRIBUTOR: yes via PRs and potentially directly, pending our 
legal dept :-(


thanks

   Andrew

-Original Message-
From: Carlos Rovira [mailto:carlosrov...@apache.org] 
Sent: 07 June 2019 10:24
To: dev@royale.apache.org
Subject: [EXTERNAL] Royale Commercial Support Page (was: Fwd: AIR and Royale)

Hi,

I'll be creating a page on the website in the following days with a list of 
third party providers that offers commercial support for Apache Royale, in the 
lines we saw in the links shared by Dave Fisher as examples in other Apache 
products.

It could be companies or individuals.

Anyone that wants to be listed, please share here the following data:

* NAME
* SHORT DESCRIPTION (if applies)
* LOGO (if applies) (PNG, background transparent, good resolution (at least 
above 800px)
* WEBSITE URL
* CONTACT PERSON (in case of individual can be same as NAME)
* EMAIL OF CONTACT
* PHONE OF CONTACT
* APACHE ROYALE CONTRIBUTOR (if the company or individual has people 
contributing to this project, or if is an individual contributes to this
project)

thanks


-- Forwarded message -
De: Carlos Rovira 

If you consider this ok, I can create a thread so companies that want to be 
listed, can express they want to, and I can create a page in our site with the 
logos and urls and maybe more (contact person?, ...)

thanks



--
Carlos Rovira
https://clicktime.symantec.com/3K3p6aWscq5ynav4MdyiTSC7Vc?u=http%3A%2F%2Fabout.me%2Fcarlosrovira

Release Step 011 Succeeded

[Apache Royale CI Server]

>From the royale-asjs repo:
1. Run ant -f releasesteps.xml Release_Step_011 -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_011_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_011_Upload 
-Drelease.version=0.9.6
This will upload the signed artifacts to Maven Release Staging.  Verify that 
the compiler and typedefs artifacts are there along with the asjs artifacts, 
then hit the close to close the staging repo.

Release Step 010 Succeeded

[Apache Royale CI Server]

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

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

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.

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.

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.

Re: Embedded Assets (was Re: AIR and Royale)

[QA]

>I guess the tradeoff is in between firing off several http requests 
for small files vs embedding them is a less efficient format.


That was one advantage that a SWF had over traditional HTML page. One 
request instead of many. I looked at using link rel=preload but that is 
has low priority and is not supported in Firefox.


You can send a single resources zip down the line and unzip it with JS. 
If there is a SWF parser you could send that and then on page load add 
the resources to the page (get rid of the first flash).


A few places online also suggest using a stylesheet with background-url 
set to image resources and then the div display set to none. With base64 
data you could have one large resources css and then when that loads 
cache them.



On 6/6/19 5:12 PM, Carlos Rovira wrote:

ok Om thanks for sharing.
Do you have some url with some code to see an example of how they do it?
thanks

El jue., 6 jun. 2019 a las 19:05, OmPrakash Muppirala ()
escribió:


In recent applications using React/Webpack, I have seen defaults of using
base64 embedding of files less than 10k in size.

I guess the tradeoff is in between firing off several http requests for
small files vs embedding them is a less efficient format.

I think a similar strategy would work for Royale.

Thanks,
Om

On Thu, Jun 6, 2019, 3:32 AM Carlos Rovira 
wrote:


Hi,

I think in the case of HTML, does not have sense to me the concept of

Embed

like in Flex. Maybe of SWF target or others (don't know if WebAsm could
benefit from something like this)
Maybe for HTML use something like Embed metadata, could just copy the
assets to the resources folder to be available, since like Alex said, a
request per asset is needed and making other kind of big file seems

strange

in this case (maybe not). Although we have solved the copying of assets

in

different ways through compiler for libraries and ANT/MAVEN automation in
Application.

for me this could be something to investigate in the future, but with low
priority, since I think we still have bigger fish to fry

just my 2...


El mié., 5 jun. 2019 a las 18:07, Alex Harui (
Regarding embedded assets in Royale:

There is no embedded asset support at this time because it is not

obvious

to me it will be worth it.  We need a volunteer to devise a strategy

that

works and implement it.

In Flex/Flash, my understanding is that folks embedded assets to save

on

server requests for assets like images.  That makes sense because,

since

a

SWF is a compressed binary and most assets are compressed binaries, you

can

essentially append the assets to the SWF.

However, for Royale in the browser, every implementation of "embedding"
I've seen seems to Base64 encode the asset, converting it to text and
increasing the number of bytes.  And the resulting Base64 bytes may
deteriorate the gzip compression of the .html file.

Flash also had frames in the SWF and assets could be embedded on later
frames allowing a download progress bar to show up before all of the

rest

of the SWF is downloaded.  I don't know what the equivalent for that is
without Flash.

I believe another advantage of embedding in Flash was that the asset

was

ready to be instantiated and placed on the display list right away.

I'm

not clear that an embedded Base64 image can be used in an  tag and
prevent "popping" given that Royale generates the  tags

dynamically.

So, we need a volunteer to create some examples of how to use browser
embedding in dynamically generated  tags so we can see if there

will

be any benefit or not.  And if not, possibly explore other options,

such

as

delivering all assets in one true binary blob somehow.

HTH,
-Alex

On 6/5/19, 7:05 AM, "Frost, Andrew"  wrote:

 Yes, me :-)

 I'm pushing Royale internally, I think it has a lot of promise -
although I still do find it a little frustrating at times internally!

In

terms of what support you can give, the sorts of things you're already
doing are great, but yes it might mean we lean a little more on this
mailing list if we're facing tricky issues.

 We have one sales case in particular at the moment which has the
potential to be very big, we're hoping they move forwards with a proof

of

concept project which would take a small part of their app and port

this

to

Royale. A few issues we've found so far from investigations:
 - their flex code is embedding icons that are contained within a

SWF.

Royale compiler didn't seem to like this, not sure whether it's just

syntax

or whether we need to pull all the assets out (not a big job, we can
automate that..)
 - they have binding using functions e.g.
text="{localizationHelper.getString('fieldName')}", which caused an

issue

when generating the JavaScript code as the string-within-a-string

seemed

to

upset the parser. We can look at this later perhaps though..
 - when we got it compiling, the main thing was with responsiveness
i.e. trying to get the app to resize and for all the 

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.

Re: Compiler Build Failing on Windows

[Alex Harui]

IIRC, FLASHPLAYER_DEBUGGER has to point to an actual .exe file, not just a 
folder.

If our documentation need to be more clear, please suggest changes.

Thanks,
-Alex

On 6/7/19, 2:20 AM, "Shiffy"  wrote:

Its PLAYERGLOBAL_HOME


From: Harbs
Sent: Friday, June 7, 2019 12:17 PM
To: dev@royale.apache.org
Subject: Re: Compiler Build Failing on Windows

Is it PLAYERGLOBAL or PLAYERGLOBAL_HOME?

> On Jun 7, 2019, at 11:50 AM, Shiffy  wrote:
> 
> Thanks everyone for helping me out here.
> 
> These are my environment variables.
> 
> AIR_HOME ..\github\adobe\frameworks\AIRSDK_Compiler
> PLAYERGLOBAL ..\github\adobe\frameworks\libs\player
> FLASHPLAYER_DEBUGGER ..\github\adobe\flash
> 
> 
> From: Yishay Weiss
> Sent: Friday, June 7, 2019 8:45 AM
> To: dev@royale.apache.org
> Subject: RE: Compiler Build Failing on Windows
> 
> I haven’t had problems building the compiler with Ant. Shiffy, can you 
share the values of the env vars Alex wrote down?
> 
> 
> 
> AIR_HOME
> PLAYERGLOBAL_HOME
> FLASHPLAYER_DEBUGGER
> 
> 
> 
> 
> 
> From: Piotr Zarzycki 
> Sent: Thursday, June 6, 2019 1:40:17 PM
> To: dev@royale.apache.org
> Subject: Re: Compiler Build Failing on Windows
> 
> I believe the most important thing right now is to getting back our 
nightly
> build and see whether there it doesn't occur. If it doesn't you may have
> your answer to the issue without doing anything on your local machine.
> 
> czw., 6 cze 2019 o 12:36 Carlos Rovira  
napisał(a):
> 
>> I have pendent to check build with Env vars, although can't say where I
>> could try since that requieres some hours to pursue that task.
>> I think we should all try to do this, since in doing that we can finally
>> refine the process of build that is the biggest problem in Royale along
>> with releases.
>> Getting Royale to build without any issue for any new comers is the most
>> important thing along with getting releases monthly without much effort.
>> (And of course continue with documentation)
>> 
>> 
>> 
>> El mié., 5 jun. 2019 a las 17:53, Alex Harui ()
>> escribió:
>> 
>>> As discussed recently on some other thread, environment variables matter
>>> and the documentation may not be up-to-date.
>>> 
>>> We build both SWF or JS-Only packages based on environment variables.
>>> Either you have the Adobe stuff for SWF and environment variables
>> pointing
>>> to them or not.  If you only have some of the Adobe environment 
variables
>>> but not others, you'll probably confuse the builds.
>>> 
>>> AIR_HOME
>>> PLAYERGLOBAL_HOME
>>> FLASHPLAYER_DEBUGGER
>>> 
>>> Either set all 3 or don't set any of the 3.
>>> 
>>> HTH,
>>> -Alex
>>> 
>>> On 6/5/19, 7:27 AM, "Piotr Zarzycki"  wrote:
>>> 
>>>Carlos,
>>> 
>>>I think it is ANT build. Yesterday I tried locally and had the same
>>> issue.
>>>I was going to report it here as well.
>>> 
>>>Thanks,
>>>Piotr
>>> 
>>>śr., 5 cze 2019 o 16:00 Carlos Rovira 
>>> napisał(a):
>>> 
 Hi
 
 can you provide more info about what method are you using to build?
>>> ANT?
 Maven? and provide the steps you use, also if you have set up some
>>> env
 vars?
 thanks
 
 El mié., 5 jun. 2019 a las 12:43, Shiffy ()
>>> escribió:
 
> I’m trying to build the compiler on Windows and it keeps failing
>>> in the
> tests.
> 
> Here’s one example of a failed test that I’m getting:
> 
>>> 
>> https://pastebin.com/TpQynEmF
> 
> The test results are hard to read, but one difference I see
>>> between the
> expected results and the actual results is that it expects
>> extends
>>> Object
> and it’s extending flash.display::Sprite.
> 
> Any ideas on what’s wrong?
> 
 
 
 --
 Carlos Rovira
 
>>> 
>> http://about.me/carlosrovira
 
>>> 
>>> 
>>>--
>>> 
>>>Piotr Zarzycki
>>> 
>>>Patreon: *
>>> 
>> https://www.patreon.com/piotrzarzycki
>>><
>>> 
>> https://www.patreon.com/piotrzarzycki
 *
>>> 
>>> 
>>> 
>> 
>> --
>> Carlos Rovira
>> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C2cd23d8c43444725b40908d6eb2950b4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636954960060896473sdata=bN9XPWFQDeOVhtpG6YXIzqlitv9bFM%2F6rAlqacEQpmU%3Dreserved=0
>> 
> 
> 
> --
> 
> Piotr Zarzycki
> 
> 

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.

Re: Royale Commercial Support Page (was: Fwd: AIR and Royale)

[Andrew Wetmore]

This is s great idea

On Fri, Jun 7, 2019, 6:24 AM Carlos Rovira,  wrote:

> Hi,
>
> I'll be creating a page on the website in the following days with a list of
> third party providers that offers commercial support for Apache Royale, in
> the lines we saw in the links shared by Dave Fisher as examples in other
> Apache products.
>
> It could be companies or individuals.
>
> Anyone that wants to be listed, please share here the following data:
>
> * NAME
> * SHORT DESCRIPTION (if applies)
> * LOGO (if applies) (PNG, background transparent, good resolution (at least
> above 800px)
> * WEBSITE URL
> * CONTACT PERSON (in case of individual can be same as NAME)
> * EMAIL OF CONTACT
> * PHONE OF CONTACT
> * APACHE ROYALE CONTRIBUTOR (if the company or individual has people
> contributing to this project, or if is an individual contributes to this
> project)
>
> thanks
>
>
> -- Forwarded message -
> De: Carlos Rovira 
>
> If you consider this ok, I can create a thread so companies that want to be
> listed, can express they want to, and I can create a page in our site with
> the logos and urls and maybe more (contact person?, ...)
>
> thanks
>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>

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

[Piotr Zarzycki]

Does downgrading Firefox may fix that problem?

On Wed, Jun 5, 2019, 2:22 PM Piotr Zarzycki 
wrote:

> What we actually are doing with Selenium? What important they are doing ?
>
> wt., 4 cze 2019 o 15:07 Piotr Zarzycki 
> napisał(a):
>
>> I doubt that - how it may be connected to his work. I checked Jenkins
>> configuration and I don't see anything new.
>>
>> On Tue, Jun 4, 2019, 3:04 PM Carlos Rovira 
>> wrote:
>>
>>> Maybe Alex could bring more light on this. Even could be a side effect of
>>> his release branch development,
>>>
>>> El mar., 4 jun. 2019 a las 14:01, Piotr Zarzycki (<
>>> piotrzarzyck...@gmail.com>)
>>> escribió:
>>>
>>> > I have spent some time on that and no luck with figure out what is
>>> > happening. Selenium driver cannot connect for some reason with Firefox
>>> on
>>> > port:
>>> >
>>> >   [java] org.openqa.selenium.firefox.NotConnectedException: Unable to
>>> > connect to host 127.0.0.1 on port 7055 after 45000 ms. Firefox console
>>> > output:
>>> >
>>> >
>>> > How to properly check whether port is unavailable? I've seen some
>>> > stuff on SOF but it doesn't display for me anything.
>>> >
>>> >
>>> > Thanks,
>>> >
>>> > Piotr
>>> >
>>> >
>>> > pon., 3 cze 2019 o 14:16 Carlos Rovira 
>>> > napisał(a):
>>> >
>>> > > Could be something related to selenium?
>>> > >
>>> > >
>>> > >
>>> >
>>> C:\Users\apacheroyale\AppData\Local\Temp\2\anonymous8220624574578606825webdriver-profile\extensions\webdriver-staging
>>> > >  [java] 1559535801478   addons.xpi  DEBUG   Existing
>>> add-on
>>> > > formautof...@mozilla.org in app-system-defaults
>>> > >  [java] 1559535801478   addons.xpi  DEBUG   Existing
>>> add-on
>>> > > fxmoni...@mozilla.org in app-system-defaults
>>> > >  [java] 1559535801478   addons.xpi  DEBUG   Existing
>>> add-on
>>> > > screensh...@mozilla.org in app-system-defaults
>>> > >  [java] 1559535801478   addons.xpi  DEBUG   Existing
>>> add-on
>>> > > webcompat-repor...@mozilla.org in app-system-defaults
>>> > >  [java] 1559535801478   addons.xpi  DEBUG   Existing
>>> add-on
>>> > > webcom...@mozilla.org in app-system-defaults
>>> > >  [java] 1559535801479   addons.xpi  DEBUG
>>>  scanForChanges
>>> > > changed:
>>> > > false, state: {}
>>> > >  [java] JavaScript error:
>>> > > resource://gre/modules/addons/XPIProvider.jsm, line 2706: TypeError:
>>> > > addon is null
>>> > >  [java] 1559535816710   addons.productaddonsINFO
>>> sending
>>> > > request
>>> > > to:
>>> > >
>>> >
>>> https://aus5.mozilla.org/update/3/GMP/67.0/20190516215225/WINNT_x86_64-msvc-x64/en-US/release/Windows_NT%2010.0.0.0.14393.2999%20(x64)/default/default/update.xml
>>> > >  [java] 1559535816783   addons.productaddonsINFO
>>> Completed
>>> > > downloading document
>>> > >  [java] 1559535817196   addons.productaddonsINFO
>>> > > downloadXHR File
>>> > > download. status=200
>>> > >  [java] 1559535817226   addons.productaddonsINFO
>>> > Downloaded
>>> > > file
>>> > > will be saved to
>>> C:\Users\APACHE~1\AppData\Local\Temp\2\tmpaddon-e8ec0
>>> > >  [java] 1559535817846   addons.productaddonsINFO
>>> > > downloadXHR File
>>> > > download. status=200
>>> > >  [java] 1559535817848   addons.productaddonsINFO
>>> > Downloaded
>>> > > file
>>> > > will be saved to
>>> > > C:\Users\APACHE~1\AppData\Local\Temp\2\tmpaddon-cebd63
>>> > >  [java]
>>> > >  [java] at
>>> > >
>>> > >
>>> >
>>> org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:112)
>>> > >  [java] ... 7 more
>>> > >  [java] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
>>> -Xms384m
>>> > > -Xmx1g
>>> > > BUILD FAILEDc:\jenkins\workspace\royale-asjs_jsonly\build.xml:1249:
>>> > > Java returned: 1
>>> > >
>>> > > Total time: 18 minutes 35 seconds
>>> > > Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx1g
>>> > > Build step 'Invoke Ant' marked build as failure
>>> > > Archiving artifacts
>>> > > Sending e-mails to: dev@royale.apache.org
>>> > > Finished: FAILURE
>>> > >
>>> > >
>>> > >
>>> > > El lun., 3 jun. 2019 a las 14:13, Carlos Rovira (<
>>> > carlosrov...@apache.org
>>> > > >)
>>> > > escribió:
>>> > >
>>> > > > HI Piotr,
>>> > > >
>>> > > > I can confirm that I build all from scratch with unit test
>>> included and
>>> > > > all goes ok.
>>> > > >
>>> > > > El lun., 3 jun. 2019 a las 14:03, Carlos Rovira (<
>>> > > carlosrov...@apache.org>)
>>> > > > escribió:
>>> > > >
>>> > > >> going to check again with unit test
>>> > > >> report soon
>>> > > >>
>>> > > >> El lun., 3 jun. 2019 a las 13:51, Piotr Zarzycki (<
>>> > > >> piotrzarzyck...@gmail.com>) escribió:
>>> > > >>
>>> > > >>> It's been 2 days since it happening, so this is not coincidence
>>> ->
>>> > > >>>
>>> > > >>>
>>> > >
>>> >
>>> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/
>>> > > >>>
>>> > > >>> pon., 

Build failed in Jenkins: royale-asjs_jsonly #3062

[Apache Royale CI Server]

See 


--
[...truncated 2.12 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: 

[mxmlc] using source file: 

Re: Embedded Assets (was Re: AIR and Royale)

[Carlos Rovira]

Hi Andrew,

El vie., 7 jun. 2019 a las 0:39, Andrew Wetmore ()
escribió:

> @carlos.rov...@gmail.com  I think the
> "flex-equivalents" page should go just below the "components" page in the
> ToC.
>

Don't see "Components" page, do you mean "Component Sets" ?


> If you told me how to add things to the ToC, I don't remember it!
>

yeah! TOC is in "_data/toc.json"

notice that there's a relation between urls and folder names, so if you
want flex-equivalents in the main TOC you need to move it to root folder,
or if you nest in a folder TOC expect a main node called in the same way.
You can see how is done in other nodes and copy how it's done.


> And, really, I think both Component Sets and Flex Equivalents should be
> under a User Interface heading, as the source files are.
>

The problem with that is that we don't support 3 nesting in TOC, but I
think that is good. Useful docs use to be 2 levels and simplify as much as
possible the path a user must to follow to reach useful documentation.
For that reason Component Sets needs to be on root and nest all sets that
will be populating as we create it. That will be a huge aumount of info
that seems to be easy to navigate for a coming user, since he wants go to a
set and he goes directly to the branch.

In the other hand I think is good to have docs about how Royale and Flex
share concepts and things, but I always said that Royale is new software
and we should try to avoid populate compilations in many places to give
Royale its own entity. So I prefer to put all Flex comparisons in a
concrete zone, for people that comes from Flex world and want to learn all
about similarities. IOW, we changed the name from FlexJS to Royale since we
want us to create a brand that was seen as something new with its own
personality and future and avoid as much as possible be weighed down by the
weight of another technology that is going through bad days.

If we can to concentrate as much as posible Royale Flex related docs in one
place I think that would be great for Royale in global.





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

Royale Commercial Support Page (was: Fwd: AIR and Royale)

[Carlos Rovira]

Hi,

I'll be creating a page on the website in the following days with a list of
third party providers that offers commercial support for Apache Royale, in
the lines we saw in the links shared by Dave Fisher as examples in other
Apache products.

It could be companies or individuals.

Anyone that wants to be listed, please share here the following data:

* NAME
* SHORT DESCRIPTION (if applies)
* LOGO (if applies) (PNG, background transparent, good resolution (at least
above 800px)
* WEBSITE URL
* CONTACT PERSON (in case of individual can be same as NAME)
* EMAIL OF CONTACT
* PHONE OF CONTACT
* APACHE ROYALE CONTRIBUTOR (if the company or individual has people
contributing to this project, or if is an individual contributes to this
project)

thanks


-- Forwarded message -
De: Carlos Rovira 

If you consider this ok, I can create a thread so companies that want to be
listed, can express they want to, and I can create a page in our site with
the logos and urls and maybe more (contact person?, ...)

thanks



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

RE: Compiler Build Failing on Windows

[Shiffy]

Its PLAYERGLOBAL_HOME


From: Harbs
Sent: Friday, June 7, 2019 12:17 PM
To: dev@royale.apache.org
Subject: Re: Compiler Build Failing on Windows

Is it PLAYERGLOBAL or PLAYERGLOBAL_HOME?

> On Jun 7, 2019, at 11:50 AM, Shiffy  wrote:
> 
> Thanks everyone for helping me out here.
> 
> These are my environment variables.
> 
> AIR_HOME ..\github\adobe\frameworks\AIRSDK_Compiler
> PLAYERGLOBAL ..\github\adobe\frameworks\libs\player
> FLASHPLAYER_DEBUGGER ..\github\adobe\flash
> 
> 
> From: Yishay Weiss
> Sent: Friday, June 7, 2019 8:45 AM
> To: dev@royale.apache.org
> Subject: RE: Compiler Build Failing on Windows
> 
> I haven’t had problems building the compiler with Ant. Shiffy, can you share 
> the values of the env vars Alex wrote down?
> 
> 
> 
> AIR_HOME
> PLAYERGLOBAL_HOME
> FLASHPLAYER_DEBUGGER
> 
> 
> 
> 
> 
> From: Piotr Zarzycki 
> Sent: Thursday, June 6, 2019 1:40:17 PM
> To: dev@royale.apache.org
> Subject: Re: Compiler Build Failing on Windows
> 
> I believe the most important thing right now is to getting back our nightly
> build and see whether there it doesn't occur. If it doesn't you may have
> your answer to the issue without doing anything on your local machine.
> 
> czw., 6 cze 2019 o 12:36 Carlos Rovira  napisał(a):
> 
>> I have pendent to check build with Env vars, although can't say where I
>> could try since that requieres some hours to pursue that task.
>> I think we should all try to do this, since in doing that we can finally
>> refine the process of build that is the biggest problem in Royale along
>> with releases.
>> Getting Royale to build without any issue for any new comers is the most
>> important thing along with getting releases monthly without much effort.
>> (And of course continue with documentation)
>> 
>> 
>> 
>> El mié., 5 jun. 2019 a las 17:53, Alex Harui ()
>> escribió:
>> 
>>> As discussed recently on some other thread, environment variables matter
>>> and the documentation may not be up-to-date.
>>> 
>>> We build both SWF or JS-Only packages based on environment variables.
>>> Either you have the Adobe stuff for SWF and environment variables
>> pointing
>>> to them or not.  If you only have some of the Adobe environment variables
>>> but not others, you'll probably confuse the builds.
>>> 
>>> AIR_HOME
>>> PLAYERGLOBAL_HOME
>>> FLASHPLAYER_DEBUGGER
>>> 
>>> Either set all 3 or don't set any of the 3.
>>> 
>>> HTH,
>>> -Alex
>>> 
>>> On 6/5/19, 7:27 AM, "Piotr Zarzycki"  wrote:
>>> 
>>>Carlos,
>>> 
>>>I think it is ANT build. Yesterday I tried locally and had the same
>>> issue.
>>>I was going to report it here as well.
>>> 
>>>Thanks,
>>>Piotr
>>> 
>>>śr., 5 cze 2019 o 16:00 Carlos Rovira 
>>> napisał(a):
>>> 
 Hi
 
 can you provide more info about what method are you using to build?
>>> ANT?
 Maven? and provide the steps you use, also if you have set up some
>>> env
 vars?
 thanks
 
 El mié., 5 jun. 2019 a las 12:43, Shiffy ()
>>> escribió:
 
> I’m trying to build the compiler on Windows and it keeps failing
>>> in the
> tests.
> 
> Here’s one example of a failed test that I’m getting:
> 
>>> 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpastebin.com%2FTpQynEmFdata=02%7C01%7Caharui%40adobe.com%7C0c7d3e7f051245540c5508d6e9c1fbc1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636953416690581144sdata=R9R5myGACz%2BUaexnDobnVD%2FMvf1J%2FCjXeaSlNI5GrOA%3Dreserved=0
> 
> The test results are hard to read, but one difference I see
>>> between the
> expected results and the actual results is that it expects
>> extends
>>> Object
> and it’s extending flash.display::Sprite.
> 
> Any ideas on what’s wrong?
> 
 
 
 --
 Carlos Rovira
 
>>> 
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C0c7d3e7f051245540c5508d6e9c1fbc1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636953416690581144sdata=F%2By0%2BMDEJg0wYdAsOTHGIeWGbaCGuzRfKPAFLJh6JMI%3Dreserved=0
 
>>> 
>>> 
>>>--
>>> 
>>>Piotr Zarzycki
>>> 
>>>Patreon: *
>>> 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C0c7d3e7f051245540c5508d6e9c1fbc1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636953416690581144sdata=mGRcOuyal9mZruQc%2FPG39mGoHPvyVbWciHoGzELiGsA%3Dreserved=0
>>><
>>> 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C0c7d3e7f051245540c5508d6e9c1fbc1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636953416690581144sdata=mGRcOuyal9mZruQc%2FPG39mGoHPvyVbWciHoGzELiGsA%3Dreserved=0
 *
>>> 
>>> 
>>> 
>> 
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>> 
> 
> 
> --
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> 

Re: Compiler Build Failing on Windows

[Harbs]

Is it PLAYERGLOBAL or PLAYERGLOBAL_HOME?

> On Jun 7, 2019, at 11:50 AM, Shiffy  wrote:
> 
> Thanks everyone for helping me out here.
> 
> These are my environment variables.
> 
> AIR_HOME ..\github\adobe\frameworks\AIRSDK_Compiler
> PLAYERGLOBAL ..\github\adobe\frameworks\libs\player
> FLASHPLAYER_DEBUGGER ..\github\adobe\flash
> 
> 
> From: Yishay Weiss
> Sent: Friday, June 7, 2019 8:45 AM
> To: dev@royale.apache.org
> Subject: RE: Compiler Build Failing on Windows
> 
> I haven’t had problems building the compiler with Ant. Shiffy, can you share 
> the values of the env vars Alex wrote down?
> 
> 
> 
> AIR_HOME
> PLAYERGLOBAL_HOME
> FLASHPLAYER_DEBUGGER
> 
> 
> 
> 
> 
> From: Piotr Zarzycki 
> Sent: Thursday, June 6, 2019 1:40:17 PM
> To: dev@royale.apache.org
> Subject: Re: Compiler Build Failing on Windows
> 
> I believe the most important thing right now is to getting back our nightly
> build and see whether there it doesn't occur. If it doesn't you may have
> your answer to the issue without doing anything on your local machine.
> 
> czw., 6 cze 2019 o 12:36 Carlos Rovira  napisał(a):
> 
>> I have pendent to check build with Env vars, although can't say where I
>> could try since that requieres some hours to pursue that task.
>> I think we should all try to do this, since in doing that we can finally
>> refine the process of build that is the biggest problem in Royale along
>> with releases.
>> Getting Royale to build without any issue for any new comers is the most
>> important thing along with getting releases monthly without much effort.
>> (And of course continue with documentation)
>> 
>> 
>> 
>> El mié., 5 jun. 2019 a las 17:53, Alex Harui ()
>> escribió:
>> 
>>> As discussed recently on some other thread, environment variables matter
>>> and the documentation may not be up-to-date.
>>> 
>>> We build both SWF or JS-Only packages based on environment variables.
>>> Either you have the Adobe stuff for SWF and environment variables
>> pointing
>>> to them or not.  If you only have some of the Adobe environment variables
>>> but not others, you'll probably confuse the builds.
>>> 
>>> AIR_HOME
>>> PLAYERGLOBAL_HOME
>>> FLASHPLAYER_DEBUGGER
>>> 
>>> Either set all 3 or don't set any of the 3.
>>> 
>>> HTH,
>>> -Alex
>>> 
>>> On 6/5/19, 7:27 AM, "Piotr Zarzycki"  wrote:
>>> 
>>>Carlos,
>>> 
>>>I think it is ANT build. Yesterday I tried locally and had the same
>>> issue.
>>>I was going to report it here as well.
>>> 
>>>Thanks,
>>>Piotr
>>> 
>>>śr., 5 cze 2019 o 16:00 Carlos Rovira 
>>> napisał(a):
>>> 
 Hi
 
 can you provide more info about what method are you using to build?
>>> ANT?
 Maven? and provide the steps you use, also if you have set up some
>>> env
 vars?
 thanks
 
 El mié., 5 jun. 2019 a las 12:43, Shiffy ()
>>> escribió:
 
> I’m trying to build the compiler on Windows and it keeps failing
>>> in the
> tests.
> 
> Here’s one example of a failed test that I’m getting:
> 
>>> 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpastebin.com%2FTpQynEmFdata=02%7C01%7Caharui%40adobe.com%7C0c7d3e7f051245540c5508d6e9c1fbc1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636953416690581144sdata=R9R5myGACz%2BUaexnDobnVD%2FMvf1J%2FCjXeaSlNI5GrOA%3Dreserved=0
> 
> The test results are hard to read, but one difference I see
>>> between the
> expected results and the actual results is that it expects
>> extends
>>> Object
> and it’s extending flash.display::Sprite.
> 
> Any ideas on what’s wrong?
> 
 
 
 --
 Carlos Rovira
 
>>> 
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C0c7d3e7f051245540c5508d6e9c1fbc1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636953416690581144sdata=F%2By0%2BMDEJg0wYdAsOTHGIeWGbaCGuzRfKPAFLJh6JMI%3Dreserved=0
 
>>> 
>>> 
>>>--
>>> 
>>>Piotr Zarzycki
>>> 
>>>Patreon: *
>>> 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C0c7d3e7f051245540c5508d6e9c1fbc1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636953416690581144sdata=mGRcOuyal9mZruQc%2FPG39mGoHPvyVbWciHoGzELiGsA%3Dreserved=0
>>><
>>> 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C0c7d3e7f051245540c5508d6e9c1fbc1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636953416690581144sdata=mGRcOuyal9mZruQc%2FPG39mGoHPvyVbWciHoGzELiGsA%3Dreserved=0
 *
>>> 
>>> 
>>> 
>> 
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>> 
> 
> 
> --
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
> 

Re: Language improvements

[Alex Harui]

Hi Greg,

I guess I don't understand your assertion that we can't use Vector in library 
code unless it is Vector-as-Array.  My guess is that you are forgetting how 
PAYG applies to all future additions to the Basic components (including your 
proposed Vector implementation).  If someone needs any new API, it will 
hopefully be added in a PAYG fashion, such as a bead or utility method, and 
those who need it will use it and pay for the cost and if the best way to 
implement that is via a more robust Vector implementation that is totally fine.

But for the particular use case in UIBase's Strand that essentially everybody 
needs, we need to find the smallest, fastest implementation, and I believe we 
don't need runtime type-checking in that implementation because most people 
will not need it.  If someone needs runtime type-checking on the Strand it can 
be added.  That is PAYG.

I doubt that essentially everyone will need to grab the entire beads Vector as 
a Vector so hopefully folks who need that will implement that as a separate 
utility method or bead and can use your Vector implementation.

I can't predict the future and don't want to speculate.  We've also said DAYG 
(do as you go) in many emails.  It isn't worth speculating on what other 
scenarios might come up that require a more robust Vector in UIBase.  We'll 
cross that bridge when we come to it.  Some volunteer might have implemented a 
better approach to Vector in the interim, thanks in part to you leaving options 
in the compiler around Vector so they can more easily see where to add other 
implementations.

And thanks for the tests as well.  Those will definitely be helpful.

Thanks,
-Alex

On 6/6/19, 2:02 PM, "Greg Dove"  wrote:

Hi Alex, it seems I do need to make one more post after all.
I do feel like I have shared all this information before, but I will make
'one more entry' in case I did not do that with clarity:


On Wed, Jun 5, 2019 at 6:36 PM Alex Harui  wrote:

> Your summary of my opinion is not correct.
>
> If Vector-as-array is what the current develop branch output is, I am
> unable to understand how that output is incorrect or poses any risks for
> anyone who knows they will not need runtime type-checking or runtime
> fixed-length checking.  And thus, it should remain an option.  For sure, 
it
> was good enough for at least two production apps.
>
> I said previously that I don't consider that single case to be a
validation for a more general case, it is just using index access and one
push, iirc. And it really offers no value for runtime safety in the swf
version because the runtime safety for the push call was already guarded by
the signature of the enclosing method. It has already been addressed in the
branch in ways we already discussed at length.
I'd guess that Harbs' experience might validate Vector-as-Array more,
because it sounds like he was using Vector (and therefore Vector-as-Array)
much more than that, iiuc, but Harbs also seemed willing to consider other
options.
While I personally don't think that example justifies it as a feature, I'm
not interested in using it as any justification to oppose it. Like I said,
I will add it back.

I consider that specific example (as it is currently in develop) 'safe' in
the swc *because* it abides by the following:
'Don't use any emulation classes in library code unless your emulation
class is Array, and if it is Array, don't expose the Vector type on any
public or protected api surface because it will be a misleading
representation of the type to the user of that api'
The Vector instance being substituted with Array is a private instance and
is never exposed via public or protected access, so it is 'safe'

If someone (anyone), at some point, released the same swc after adding
public function getMyBeadVector():Vector.IBead {
 return _beads; //share the private instance
}

I consider it not to be 'safe'.
(I'm not using angle brackets above because they mess up some readers it
seems)

At that point it gives someone else a potential problem, because it is
really returning an Array, instead of a distinctive Vector type, and can
only be 'safe-ish' if the user of the swc (it might be another library or
application) knows its limitations or happens to be applying the same
optimization to their own code (and accepting whatever risks they do with
that). It may not be obvious to the user of the swc that the instance is an
Array because their IDE tells them it is a Vector, but it can behave
differently to how they expect a Vector to behave. They might end up adding
code to offset the unusual behaviour, or doing things which break things
later if a more conformant Vector is swapped in. Using Array here is just a
specific example of the more general emulation