Build failed in Jenkins: royale-asjs_jsonly #3058

[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: 

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 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 009 Succeeded

[Apache Royale CI Server]

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

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.

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.

Royale_Release_Step_002 - Build # 34 - Failure!

[Apache Royale CI Server]

Royale_Release_Step_002 - Build # 34 - Failure:

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

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.

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.

Embedded Assets (was Re: AIR and Royale)

[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 internal elements to then 
resize. We may use the MX emulation classes for this but it still looked like 
more support is needed - although we only looked briefly at this.

Once those issues are sorted though, we would have one big task (to 
recreate a very advanced data grid control that they'd developed in Flex/Flash) 
and a lot of the rest - around the AS3 logic - should fall into place! I'm 
hoping we can convince them to go with this solution..


thanks

   Andrew



-Original Message-
From: Harbs [mailto:harbs.li...@gmail.com] 
Sent: 04 June 2019 14:41
To: dev@royale.apache.org
Subject: [EXTERNAL] Re: AIR and Royale

Well to start with: Does anyone know anyone working for them?

I’d like to hear from them what it would take for them to push Royale more.

> On Jun 4, 2019, at 4:10 PM, Carlos Rovira  wrote:
> 
> Hi,
> 
> what's the kind of support you're thinking ?
> 
> 
> 
> El mar., 4 jun. 2019 a las 9:36, Piotr Zarzycki 
> ()
> escribió:
> 
>> Hi Harbs,
>> 
>> I was exactly think the same about that, so I'm keeping finger 
>> crossed to that effort.
>> 
>> Thanks,
>> Piotr
>> 
>> wt., 4 cze 2019 o 09:34 Harbs  napisał(a):
>> 
>>> I just heard about this announcement.[1]
>>> 
>>> I went over to the Harman site and was reading this page.[2]
>>> 
>>> I was particularly struck by this statement:
>>> 
>>> HARMAN’s offerings also include consultancy, support and migration 
>>> services for companies looking to move their applications away from 
>>> Flash technologies over to HTML5 via solutions such as Angular, 
>>> Apache Royale
>> and
>>> other JavaScript based frameworks.
>>> 
>>> 
>>> Considering that they mention Royale explicitly as the number 2
>> framework,
>>> I’m guessing they will be pushing Royale to a certain degree. We 
>>> should probably look to support that effort.
>>> 
>>> 

Re: AIR and Royale

[Piotr Zarzycki]

Hi Dave,

If I understand from those page not only companies can be listed but also
individuals - Am I correct?

Thanks,
Piotr


On Wed, Jun 5, 2019, 5:53 PM Dave Fisher  wrote:

> This is fine as long as it is done in a vendor neutral manner with clear
> instruction on how to ask to be added. Also, there should be clarity that
> no vendor is “endorsed”.
>
> Examples:
> https://www.openoffice.org/bizdev/consultants.html
> https://wiki.apache.org/cassandra/ThirdPartySupport
>
> https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+Service+Providers
> https://wiki.apache.org/hadoop/Distributions%20and%20Commercial%20Support
>
> https://cwiki.apache.org/confluence/display/WICKET/Companies+that+provide+services
>
> Regards,
> Dave
>
> > On Jun 5, 2019, at 7:06 AM, Carlos Rovira 
> wrote:
> >
> > Hi,
> >
> > I think one thing we can do is create some page on website where we can
> > list companies that can give services around Royale (consultancy,
> > development, etc...). I think that could be good for Royale.
> > Don't know if that is a problem with Apache. Only giving a list of
> posible
> > companies should be ok.
> > Other than that I can't think where we can help
> >
> > 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
> >
> >
> >
> > El mar., 4 jun. 2019 a las 15:40, Harbs ()
> escribió:
> >
> >> Well to start with: Does anyone know anyone working for them?
> >>
> >> I’d like to hear from them what it would take for them to push Royale
> more.
> >>
> >>> On Jun 4, 2019, at 4:10 PM, Carlos Rovira 
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>> what's the kind of support you're thinking ?
> >>>
> >>>
> >>>
> >>> El mar., 4 jun. 2019 a las 9:36, Piotr Zarzycki (<
> >> piotrzarzyck...@gmail.com>)
> >>> escribió:
> >>>
>  Hi Harbs,
> 
>  I was exactly think the same about that, so I'm keeping finger crossed
> >> to
>  that effort.
> 
>  Thanks,
>  Piotr
> 
>  wt., 4 cze 2019 o 09:34 Harbs  napisał(a):
> 
> > I just heard about this announcement.[1]
> >
> > I went over to the Harman site and was reading this page.[2]
> >
> > I was particularly struck by this statement:
> >
> > HARMAN’s offerings also include consultancy, support and migration
> > services for companies looking to move their applications away from
> >> Flash
> > technologies over to HTML5 via solutions such as Angular, Apache
> Royale
>  and
> > other JavaScript based frameworks.
> >
> >
> > Considering that they mention Royale explicitly as the number 2
>  framework,
> > I’m guessing they will be pushing Royale to a certain degree. We
> should
> > probably look to support that effort.
> >
> > [1]https://theblog.adobe.com/the-future-of-adobe-air/ <
> > https://theblog.adobe.com/the-future-of-adobe-air/>
> > [2]https://services.harman.com/partners/adobe <
> > https://services.harman.com/partners/adobe>
> 
> 
> 
>  --
> 
>  Piotr Zarzycki
> 
>  Patreon: *https://www.patreon.com/piotrzarzycki
>  *
> 
> >>>
> >>>
> >>> --
> >>> Carlos Rovira
> >>> http://about.me/carlosrovira
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
>
>

Re: AIR and Royale

[Dave Fisher]

This is fine as long as it is done in a vendor neutral manner with clear 
instruction on how to ask to be added. Also, there should be clarity that no 
vendor is “endorsed”.

Examples:
https://www.openoffice.org/bizdev/consultants.html
https://wiki.apache.org/cassandra/ThirdPartySupport
https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+Service+Providers
https://wiki.apache.org/hadoop/Distributions%20and%20Commercial%20Support
https://cwiki.apache.org/confluence/display/WICKET/Companies+that+provide+services

Regards,
Dave

> On Jun 5, 2019, at 7:06 AM, Carlos Rovira  wrote:
> 
> Hi,
> 
> I think one thing we can do is create some page on website where we can
> list companies that can give services around Royale (consultancy,
> development, etc...). I think that could be good for Royale.
> Don't know if that is a problem with Apache. Only giving a list of posible
> companies should be ok.
> Other than that I can't think where we can help
> 
> 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
> 
> 
> 
> El mar., 4 jun. 2019 a las 15:40, Harbs () escribió:
> 
>> Well to start with: Does anyone know anyone working for them?
>> 
>> I’d like to hear from them what it would take for them to push Royale more.
>> 
>>> On Jun 4, 2019, at 4:10 PM, Carlos Rovira 
>> wrote:
>>> 
>>> Hi,
>>> 
>>> what's the kind of support you're thinking ?
>>> 
>>> 
>>> 
>>> El mar., 4 jun. 2019 a las 9:36, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>)
>>> escribió:
>>> 
 Hi Harbs,
 
 I was exactly think the same about that, so I'm keeping finger crossed
>> to
 that effort.
 
 Thanks,
 Piotr
 
 wt., 4 cze 2019 o 09:34 Harbs  napisał(a):
 
> I just heard about this announcement.[1]
> 
> I went over to the Harman site and was reading this page.[2]
> 
> I was particularly struck by this statement:
> 
> HARMAN’s offerings also include consultancy, support and migration
> services for companies looking to move their applications away from
>> Flash
> technologies over to HTML5 via solutions such as Angular, Apache Royale
 and
> other JavaScript based frameworks.
> 
> 
> Considering that they mention Royale explicitly as the number 2
 framework,
> I’m guessing they will be pushing Royale to a certain degree. We should
> probably look to support that effort.
> 
> [1]https://theblog.adobe.com/the-future-of-adobe-air/ <
> https://theblog.adobe.com/the-future-of-adobe-air/>
> [2]https://services.harman.com/partners/adobe <
> https://services.harman.com/partners/adobe>
 
 
 
 --
 
 Piotr Zarzycki
 
 Patreon: *https://www.patreon.com/piotrzarzycki
 *
 
>>> 
>>> 
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>> 
>> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: Compiler Build Failing on Windows

[Alex Harui]

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

*

Re: Compiler Build Failing on Windows

[Piotr Zarzycki]

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
*

Re: AIR and Royale

[Carlos Rovira]

Hi,

I think one thing we can do is create some page on website where we can
list companies that can give services around Royale (consultancy,
development, etc...). I think that could be good for Royale.
Don't know if that is a problem with Apache. Only giving a list of posible
companies should be ok.
Other than that I can't think where we can help

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



El mar., 4 jun. 2019 a las 15:40, Harbs () escribió:

> Well to start with: Does anyone know anyone working for them?
>
> I’d like to hear from them what it would take for them to push Royale more.
>
> > On Jun 4, 2019, at 4:10 PM, Carlos Rovira 
> wrote:
> >
> > Hi,
> >
> > what's the kind of support you're thinking ?
> >
> >
> >
> > El mar., 4 jun. 2019 a las 9:36, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> > escribió:
> >
> >> Hi Harbs,
> >>
> >> I was exactly think the same about that, so I'm keeping finger crossed
> to
> >> that effort.
> >>
> >> Thanks,
> >> Piotr
> >>
> >> wt., 4 cze 2019 o 09:34 Harbs  napisał(a):
> >>
> >>> I just heard about this announcement.[1]
> >>>
> >>> I went over to the Harman site and was reading this page.[2]
> >>>
> >>> I was particularly struck by this statement:
> >>>
> >>> HARMAN’s offerings also include consultancy, support and migration
> >>> services for companies looking to move their applications away from
> Flash
> >>> technologies over to HTML5 via solutions such as Angular, Apache Royale
> >> and
> >>> other JavaScript based frameworks.
> >>>
> >>>
> >>> Considering that they mention Royale explicitly as the number 2
> >> framework,
> >>> I’m guessing they will be pushing Royale to a certain degree. We should
> >>> probably look to support that effort.
> >>>
> >>> [1]https://theblog.adobe.com/the-future-of-adobe-air/ <
> >>> https://theblog.adobe.com/the-future-of-adobe-air/>
> >>> [2]https://services.harman.com/partners/adobe <
> >>> https://services.harman.com/partners/adobe>
> >>
> >>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon: *https://www.patreon.com/piotrzarzycki
> >> *
> >>
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
>
>

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

Re: AIR and Royale

[Frost, Andrew]

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 internal elements to then resize. We 
may use the MX emulation classes for this but it still looked like more support 
is needed - although we only looked briefly at this.

Once those issues are sorted though, we would have one big task (to recreate a 
very advanced data grid control that they'd developed in Flex/Flash) and a lot 
of the rest - around the AS3 logic - should fall into place! I'm hoping we can 
convince them to go with this solution..


thanks

   Andrew



-Original Message-
From: Harbs [mailto:harbs.li...@gmail.com] 
Sent: 04 June 2019 14:41
To: dev@royale.apache.org
Subject: [EXTERNAL] Re: AIR and Royale

Well to start with: Does anyone know anyone working for them?

I’d like to hear from them what it would take for them to push Royale more.

> On Jun 4, 2019, at 4:10 PM, Carlos Rovira  wrote:
> 
> Hi,
> 
> what's the kind of support you're thinking ?
> 
> 
> 
> El mar., 4 jun. 2019 a las 9:36, Piotr Zarzycki 
> ()
> escribió:
> 
>> Hi Harbs,
>> 
>> I was exactly think the same about that, so I'm keeping finger 
>> crossed to that effort.
>> 
>> Thanks,
>> Piotr
>> 
>> wt., 4 cze 2019 o 09:34 Harbs  napisał(a):
>> 
>>> I just heard about this announcement.[1]
>>> 
>>> I went over to the Harman site and was reading this page.[2]
>>> 
>>> I was particularly struck by this statement:
>>> 
>>> HARMAN’s offerings also include consultancy, support and migration 
>>> services for companies looking to move their applications away from 
>>> Flash technologies over to HTML5 via solutions such as Angular, 
>>> Apache Royale
>> and
>>> other JavaScript based frameworks.
>>> 
>>> 
>>> Considering that they mention Royale explicitly as the number 2
>> framework,
>>> I’m guessing they will be pushing Royale to a certain degree. We 
>>> should probably look to support that effort.
>>> 
>>> [1]https://clicktime.symantec.com/3L9wbF4uCYccj7EQCUBeXbp7Vc?u=https
>>> %3A%2F%2Ftheblog.adobe.com%2Fthe-future-of-adobe-air%2F < 
>>> https://clicktime.symantec.com/3L9wbF4uCYccj7EQCUBeXbp7Vc?u=https%3A
>>> %2F%2Ftheblog.adobe.com%2Fthe-future-of-adobe-air%2F>
>>> [2]https://clicktime.symantec.com/36DC33RH3RXctPTGAK4XztY7Vc?u=https
>>> %3A%2F%2Fservices.harman.com%2Fpartners%2Fadobe < 
>>> https://clicktime.symantec.com/36DC33RH3RXctPTGAK4XztY7Vc?u=https%3A
>>> %2F%2Fservices.harman.com%2Fpartners%2Fadobe>
>> 
>> 
>> 
>> --
>> 
>> Piotr Zarzycki
>> 
>> Patreon: 
>> *https://clicktime.symantec.com/32dvoAS1WTaQP1E2yQmx5pn7Vc?u=https%3A
>> %2F%2Fwww.patreon.com%2Fpiotrzarzycki
>> > %2F%2Fwww.patreon.com%2Fpiotrzarzycki>*
>> 
> 
> 
> --
> Carlos Rovira
> https://clicktime.symantec.com/3Peb7VMJWFagYLtTD2HSBGD7Vc?u=http%3A%2F
> %2Fabout.me%2Fcarlosrovira

Re: Compiler Build Failing on Windows

[Carlos Rovira]

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

Build failed in Jenkins: royale-asjs_jsonly #3056

[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: Build failed in Jenkins: royale-asjs_jsonly #3027

[Piotr Zarzycki]

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., 3 cze 2019 o 13:50 Piotr Zarzycki <
>> piotrzarzyck...@gmail.com>
>> > > >>> napisał(a):
>> > > >>>
>> > > >>> > Did you run all the unit stests ?
>> > > >>> >
>> > > >>> > pon., 3 cze 2019 o 13:45 Carlos Rovira > >
>> > > >>> > napisał(a):
>> > > >>> >
>> > 

Compiler Build Failing on Windows

[Shiffy]

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?

Re: Language improvements

[Alex Harui]

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.

If you are specifically referring to the use of Vector in the Strand, it 
occurred to me that someone could add another option to inject a type-check 
before every push on the Vector-as-Array.  I think that would allow us to 
continue to use Vector in the Strand at a cost much less than 2K.  And allow 
many others to get type-checking on push as well.  Or, as we discussed earlier, 
we can just stop using Vector in the Strand.

If you are saying that the risk and harm to the community will come when 
someone tries to add a bead to the strand at runtime that was instantiated in a 
way that was not testable at development time, then I guess we will have to 
agree to disagree on how important that is.  IMO, that runtime checking should 
be PAYG, and I would much rather that we spend time devising a scheme to allow 
folks to opt-in to runtime checking than tell folks that they must carry around 
extra code just-in-case someone else needs runtime checking.  It could be 
something as brute force as specifying files in a compiler option where the 
compiler will replace "goog.DEBUG" with "true".  Specific to the strand, yet 
another option could just be a bead that watches for beadAdded events and 
checks for IBead.  Could be we find a way to replace Vector-as-Array code in 
libraries with the Vector implementation you've written.

Or maybe, we should spend more time getting the SWF versions of the framework 
running well enough to have RoyaleUnit or some test automation run your app in 
the Flash/AIR runtimes so lots more things get checked (missing interface 
members, other type-checks, etc).

Regardless, it is still great that you've created a runtime-checking 
implementation of Vector for those who need it.

We do not need to reach a collaborative decision that is A or B.  Why should we 
think we know what our users really need?  We provide options/choices so the 
users can decide for themselves.  And invite someone else to come up with even 
a better solution or solutions.

My 2 cents,
-Alex

On 6/3/19, 11:04 PM, "Greg Dove"  wrote:

Hi Alex, this will be my last message in this thread.

"The whole point of giving choices is to avoid having to spend so many
emails trying to reach a decision.  "
Alex, I really don't understand your stance. The focus of the recent
discussion has been on the choices themselves... concerns about their
potential risks, along with ideas for improvements and code quality.
It sounds like you are saying that we can't talk about improving the
choices we already had, because if they exist that is all that matters.
As far as I understand, the point of these email discussions is to reach
the best quality collaborative decisions.
I don't enjoy the process myself. It's inefficient. But we have an
obligation to be collaborative (I think?). Expressing something along the
lines of 'just do it and move on' does not seem to be that.
I don't care about any of these things in terms of how it affects me
personally, I have only pursued the topic in relation to what I think will
help Royale be successful.

The only way I can interpret your replies thus far is:
More options for optimization are always better, even if they might present
possible risks that could harm the community. We deal with those risks by
issuing warnings.
Specifically, in this case, a library developer being able to dictate
certain optimization(s) that should be used by (and any associated risks
that should be accepted by) the application developer is not unacceptable.

-Your approach to mitigation of the above risks will be for us to warn
people not to do the specific things that could cause the problems in the
first place (from your comment about tools, risks, and documentation).
Something like:
'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'

Is that a fair summary?

It should be not surprise to you that I personally think the above is
confusing and avoidable, because I consider that there are (and will be)
better options that achieve the same optimization results. But I understand
that you don't, and I can accept that. So I will make one last attempt to
find something that I think is middle ground...

Vector-as-Array is just a special case of the emulationClass