royale-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alina Kazi" <alina.k...@d-bz.com>
Subject RE: Substitutes in Apache Royale
Date Fri, 23 Feb 2018 11:15:33 GMT
Thank you Piotr and Alex.

Is that results in a working Royale SDK with SWF Support?

For Reference: 

https://www.dropbox.com/s/cj1bfaqgjpyd3bs/installAdobeSDKsxml.png?dl=0

 

Regards,

Alina Kazi

From: Piotr Zarzycki [mailto:piotrzarzycki21@gmail.com] 
Sent: Friday, February 23, 2018 3:00 PM
To: users@royale.apache.org
Subject: Re: Substitutes in Apache Royale

 

Alina,

 

Link to the nightly build machine where you can download royale [1]. Lin to the InstallAdobeSDKs.xml
and repository [2]

 

[1] http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/

[2] https://github.com/apache/royale-asjs/blob/develop/InstallAdobeSDKs.xml

 

Thanks, Piotr

 

2018-02-23 10:28 GMT+01:00 Alina Kazi <alina.kazi@d-bz.com>:

Hi Alex,

 

Still facing similar issue. 

Can you please share link for repo or build machine royale-asjs folder.

 

Thanks,

Alina

From: Alex Harui [mailto:aharui@adobe.com] 
Sent: Friday, February 23, 2018 12:47 PM


To: users@royale.apache.org
Subject: Re: Substitutes in Apache Royale

 

Hi Alina,

 

That's a pretty strange result.  I just tried it on my Windows machine without any problem.
 I'm wondering if something got corrupted or there is a code-page issue.

 

Try setting the environment variable

JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF8

 

If that doesn't help, try comparing the files in the royale-asjs folder with the ones on our
repo or build machine.

 

HTH,

-Alex

 

From: Alina Kazi <alina.kazi@d-bz.com>
Reply-To: "users@royale.apache.org" <users@royale.apache.org>
Date: Thursday, February 22, 2018 at 9:21 PM
To: "users@royale.apache.org" <users@royale.apache.org>
Subject: RE: Substitutes in Apache Royale

 

Issue - ran in the package's royale-asjs folder: ant –f InstallAdobeSDKs.xml

 

https://paper.dropbox.com/doc/Error-ant-f-InstallAdobeSDKs.xml-mIQ4MigH799EdiZ341l7k?_tk=share_copylink
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaper.dropbox.com%2Fdoc%2FError-ant-f-InstallAdobeSDKs.xml-mIQ4MigH799EdiZ341l7k%3F_tk%3Dshare_copylink&data=02%7C01%7Caharui%40adobe.com%7C4b416955dccc4c69504808d57a7efb17%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636549608168968520&sdata=AEHhsqj5zJDyXNXZKCwUa26iGJQnttV2KRABlgtxsj0%3D&reserved=0>


 

Thanks,

Alina

From: Alex Harui [mailto:aharui@adobe.com] 
Sent: Tuesday, February 20, 2018 11:30 PM
To: users@royale.apache.org
Subject: Re: Substitutes in Apache Royale

 

In fact, I went and tried it just now to build a Flex Hello World.

 

I had Apache Flex 4.16.0 installed in /Users/aharui/ApacheFlex4.16.0.  Then I:

 

- took the apache-royale-0.9.1-bin-js-swf package from [1]  (you must use the bin-js-swf and
not just bin-js).

- unzipped the package

- ran in the package's royale-asjs folder: ant –f InstallAdobeSDKs.xml

 

That results in a working Royale SDK with SWF Support.

 

Then I ran from the royale-asjs folder:

 

  bin/mxmlc <path to app's .mxml file> -load-config=/Users/aharui/ApacheFlex4.16.0/frameworks/flex-config.xml

 

The compile finished successfully.  I think I'm going to work on the API report now and deal
with the * selector after.  If you can get a SWF build via this technique, this is the technique
you will use to generate the API report.

 

Thanks,

-Alex

 

[1] http://royale.apache.org/download/

 

From: Alex Harui <aharui@adobe.com>
Reply-To: "users@royale.apache.org" <users@royale.apache.org>
Date: Monday, February 19, 2018 at 11:46 PM
To: "users@royale.apache.org" <users@royale.apache.org>
Subject: Re: Substitutes in Apache Royale

 

Sorry, just realized I referenced the JS compiler.  Please try using bin/compc and bin/mxmlc.
 You won't need the –targets parameter, just the load-config option.

 

HTH,

-Alex

 

From: Alex Harui <aharui@adobe.com>
Reply-To: "users@royale.apache.org" <users@royale.apache.org>
Date: Monday, February 19, 2018 at 11:14 PM
To: "users@royale.apache.org" <users@royale.apache.org>
Subject: Re: Substitutes in Apache Royale

 

Hi Alina,

 

Piotr might be better at helping you use Moonshine.  The IDEs sort of expect that the libraries/SWCs
that your code needs is in the same folder as the compiler.  That's why it might be easier
to work from the command line.

 

I remembered this morning that the Royale SWF Compiler doesn't have embedded font support.
 However the goal isn't so much to make a runnable SWF but to have the compilation and linking
complete so we can determine the full set of Flex APIs used in your app.

 

If your code has two projects, then we will want you to compile both projects with the Royale
compiler and get two API reports.  The Library project would be compiled with js/bin/compc
and the main app would be compiled with js/bin/mxmlc.

 

I think you will want to use the compiler option:

   -load-config="path to a Flex SDK flex-config.xml" 

and also use

  –compiler.targets=SWF

 

HTH,

-Alex

 

 

From: Alina Kazi <alina.kazi@d-bz.com>
Reply-To: "users@royale.apache.org" <users@royale.apache.org>
Date: Monday, February 19, 2018 at 10:10 PM
To: "users@royale.apache.org" <users@royale.apache.org>
Subject: RE: Substitutes in Apache Royale

 

Hi Alex,

Our Flex Application(Main Project) is dependent on Flex Library Project , I tookoriginal code
(Library Project) without porting it, Compiling it using Royale Compiler's SWF compiler (apache-royale-0.9.1-bin-js-swf
or apache-royale-0.9.0-bin-js-swf)



 

Moonshine IDE (1.9.0) Console :

Loading configuration: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml

: 

: C:\Users\aleena\Documents\SHMALIB\defaults Error: unable to open 'C:\Users\aleena\AppData\Roaming\npm\node_modules\apache-royale\royale-js\frameworks\royale-config.xml'.

: defaults (line: -1)

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(35): col: 0 Error: unable to open
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\mx-manifest.xml'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 35)

: 

:       </namespace>

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: unable to open
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\player\11.0\playerglobal.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

:     </external-library-path>

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: unable to open
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\rpc.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

:     </external-library-path>

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: unable to open
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\osmf.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

:     </external-library-path>

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: unable to open
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\spark.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

:     </external-library-path>

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: unable to open
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\apache.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

:     </external-library-path>

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: unable to open
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\flatspark.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

:     </external-library-path>

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: unable to open
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\framework.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

:     </external-library-path>

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: unable to open
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\spark_dmv.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

:     </external-library-path>

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: unable to open
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\sparkskins.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

:     </external-library-path>

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: unable to open
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\textLayout.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

:     </external-library-path>

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: unable to open
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\experimental.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

:     </external-library-path>

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: unable to open
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\advancedgrids.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

:     </external-library-path>

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: unable to open
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\authoringsupport.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

:     </external-library-path>

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: unable to open
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\flash-integration.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

:     </external-library-path>

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: unable to open
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\mx\mx.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

:     </external-library-path>

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(64): col: 0 Error: unable to open
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\locale\en_US'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 64)

: 

:     </library-path>

 

Regards,

Alina

From: Alex Harui [mailto:aharui@adobe.com] 
Sent: Monday, February 19, 2018 12:35 PM
To: users@royale.apache.org
Subject: Re: Substitutes in Apache Royale

 

Hi Alina,

 

What I'm asking is that you take your original code without porting it at all and run the
Royale Compiler's SWF compiler.  It should be able to produce the same SWF you are deploying
now.  It might catch errors that the Flex MXMLC compiler does not catch.  We need a successful
SWF output so we know the compiler visited all APIs.  Once you can get a SWF out, then later
I will provide you with an updated Royale SWF compiler that will also output an API usage
report.

 

Thanks,

-Alex

 

From: Alina Kazi <alina.kazi@d-bz.com>
Reply-To: "users@royale.apache.org" <users@royale.apache.org>
Date: Sunday, February 18, 2018 at 10:37 PM
To: "users@royale.apache.org" <users@royale.apache.org>
Subject: RE: Substitutes in Apache Royale

 

Hi Alex,

 

Sure, 

I’m compiling the code with the royale compiler. Porting basic components that are available
in Royale.

 

Thanks

Alina

 

From: Alex Harui [mailto:aharui@adobe.com] 
Sent: Monday, February 19, 2018 11:16 AM
To: users@royale.apache.org
Subject: Re: Substitutes in Apache Royale

 

Hi Alina,

 

While I work on the compiler API report feature, you could start now trying to get your code
to compile with the royale compiler from the command line.  I think you can run the bin/mxmlc
from the Royale releases with the same options you use with Flex MXMLC.

 

Give it a try and let us know.

-Alex

 

From: Alina Kazi <alina.kazi@d-bz.com>
Reply-To: "users@royale.apache.org" <users@royale.apache.org>
Date: Sunday, February 18, 2018 at 8:29 PM
To: "users@royale.apache.org" <users@royale.apache.org>
Subject: RE: Substitutes in Apache Royale

 

Hi Alex,

 

I’ll be waiting for your response.

 

Thanks,

Alina

 

 

From: Alex Harui [mailto:aharui@adobe.com] 
Sent: Friday, February 16, 2018 2:02 AM
To: users@royale.apache.org
Subject: Re: Substitutes in Apache Royale

 

Hi Alina,

 

I can't guarantee that you will be in production in six months, but I believe we can help
you get to the point where every screen shows up and fills with data and we are fixing bugs
in corner cases.   We might also be chasing down memory leaks and things like that.    My
strategy for lots of things is to do the big things first and polish it later.  For example,
I recently pushed some basic Virtual Item Renderer support for Royale, but I'm pretty sure
it will have bugs in corner cases, like deleting things when scrolled to the bottom.  But
most apps start at the top and it will get you going and we'll fix those corner cases later.

 

I want to finish up some infrastructural things in Royale over the next couple of weeks, then
I will adjust the compiler to generate an API report.  Once we see what that looks like, I
 should be able to help take the sample code you provided and make it work in Royale.  So
maybe in a month or so, you'll see more activity around your code.  Right now I need to clean
up a few things so we can be more efficient working with you.

 

You won't need an IDE to generate the API report.  If you know what compiler settings you
are using for your Flex app, you can just run a Royale compiler from the command-line with
the same arguments.  I believe that we are likely to make compiling your Flex app with the
Royale compiler one of the steps in migrating. The Royale compiler will catch some syntax
issues that the Flex compiler does not.

 

More later,

-Alex

 

From: Alina Kazi <alina.kazi@d-bz.com>
Reply-To: "users@royale.apache.org" <users@royale.apache.org>
Date: Thursday, February 15, 2018 at 2:13 AM
To: "users@royale.apache.org" <users@royale.apache.org>
Subject: RE: Substitutes in Apache Royale

 

Hi Alex,

Thank you so much. You gave me hope that I can achieve my target on time and at least I am
working in right direction.

At most places I'm using getItemAt(0) to access the element in ArrayCollection.

At some places myArrayCollection[0].propertyname  to access it

 

If you will modify the Royale compiler, I will definitely try compiling my Flex app with the
Royale compiler and generate a report of APIs used.

Currently I am using Visual Studio Code and apache royale 0.9.0 release is installed.I will
need your guidance which IDE and apache royale release should I use to generate that report.

 

Thanks,

Alina Kazi

From: Alex Harui [mailto:aharui@adobe.com] 
Sent: Thursday, February 15, 2018 1:40 PM
To: users@royale.apache.org
Subject: Re: Substitutes in Apache Royale

 

Hi Alina,

 

Other than ArrayCollection, that looks right.  There will be sorting classes eventually.

 

I think there are two buckets of things that you are going to need:

 

Things we haven't written yet:

  - DividedBox/Container (mostly done)

 - Menu/MenuBar

 - VariableRowHeight

 - Editable DataGrids

 - Sorting?

 

Things we have written, but aren't packaged in a way that makes migration easy:

 - TitleWindow

 - Canvas

 - ArrayCollection

 

For ArrayCollection, do you use array indexing (myArrayCollection[0]) or do you access it
as getItemAt(0)?

 

You have so many files to port, it is tempting to create a Spark-ish and MX-ish component
set.  They wouldn't be fully backward compatible but would try to implement the most commonly
used APIs.  I'm wondering what percentage of Flex APIs you actually used in your app.  If
I modify the Royale compiler, could you try compiling your Flex app with the Royale compiler
and generate a report of APIs used?

 

Thanks,

-Alex

 

From: Alina Kazi <alina.kazi@d-bz.com>
Reply-To: "users@royale.apache.org" <users@royale.apache.org>
Date: Wednesday, February 14, 2018 at 11:06 PM
To: "users@royale.apache.org" <users@royale.apache.org>
Subject: Substitutes in Apache Royale

 

Hi,

 

I have replaced few imports in Apache Royale Project after comparison in terms of functionality.

As you all are more familiar to Flex and Apache Royale. 

Are these correct substitutes?

import org.apache.royale.html.Alert; //instead of import mx.controls.Alert;

import org.apache.royale.events.CloseEvent; // instead of import mx.events.CloseEvent;

import org.apache.royale.net.events.FaultEvent; // instead of import mx.rpc.events.FaultEvent;

import org.apache.royale.net.events.ResultEvent; //instead of import mx.rpc.events.ResultEvent;

import mx.collections.ArrayCollection; //very similar to org.apache.royale.collections.TreeData

import mx.collections.Sort; // No Alternate found

import mx.collections.SortField;// No Alternate found

import mx.managers.PopUpManager; //org.apache.royale.core.IPopUp or .IPopUpHost

import org.apache.royale.utils.StringUtil;// instead of import mx.utils.StringUtil;

 

Reference: http://apacheflexbuild.cloudapp.net:8080/job/Royale_ASDoc_Example/lastSuccessfulBuild/artifact/examples/royale/ASDoc/bin/js-debug/index.html
<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheflexbuild.cloudapp.net%3A8080%2Fjob%2FRoyale_ASDoc_Example%2FlastSuccessfulBuild%2Fartifact%2Fexamples%2Froyale%2FASDoc%2Fbin%2Fjs-debug%2Findex.html&data=02%7C01%7Caharui%40adobe.com%7C2a0f4a052bf44496feaf08d574445542%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636542759199500428&sdata=A9xjrAppjUqWDkvAJTgSHhOOW3ZlkZPPZTD5%2BG4eexw%3D&reserved=0>


 

Thanks,

Alina Kazi

 





 

-- 

Piotr Zarzycki 

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


Mime
View raw message