subject:"Re\: Migrating Enterprise Flex Application"

Alex, are you able to view the details in the error page that I have
attached?



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

Error.PNG
  

Please see the attached error that shows the javascript error.



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-10-08 Thread Alex Harui

The zip file didn't work for me.  I'm not sure how well MenuExample and 
AccordionExample were tested before the release.

-Alex

On 10/8/18, 8:40 PM, "chembali"  wrote:

Will get to this as soon as I can. Here is another issue that I am having. I
am trying to take a look at some of the samples shipped with 0.9.3 release.
I am seeing issues while running some of the examples. Please see the
attached zip containing the screenshot showing the error while running the
MenuExample. I got the same error while running AccordionExample as well.
What would be the likely cause of this?

Error.zip


  



--
Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7Cd8b4f17612c34a8944f708d62d9900f1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636746532500815121sdata=0GNGs96MBe9R6VLAgBCaVqebLWp60YvEMnM7FwMGNc0%3Dreserved=0

Re: Migrating Enterprise Flex Application

Will get to this as soon as I can. Here is another issue that I am having. I
am trying to take a look at some of the samples shipped with 0.9.3 release.
I am seeing issues while running some of the examples. Please see the
attached zip containing the screenshot showing the error while running the
MenuExample. I got the same error while running AccordionExample as well.
What would be the likely cause of this?

Error.zip
  



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-10-08 Thread Alex Harui

If you create a simple test case, I will see what the Compiler is thinking.

Thanks,
-Alex

On 10/8/18, 1:23 AM, "chembali"  wrote:

I always get the compile error, but many times it goes ahead and creates the
js distribution and the component that I am trying to use works fine. But
many times it does not work as expected even though the js distribution gets
built successfully.



--
Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C03dbe0d284bc4923af2b08d62cf74ab9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636745837956777867sdata=szxLSYQBwGguj4YI1RjcK4LZagYxzDqGlWL%2F04rN42s%3Dreserved=0

Re: Migrating Enterprise Flex Application

I always get the compile error, but many times it goes ahead and creates the
js distribution and the component that I am trying to use works fine. But
many times it does not work as expected even though the js distribution gets
built successfully.



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-10-05 Thread Alex Harui

Sorry, I thought we had a -js-source-path option.  

I think package paths in SWCs did work in Flex.  I haven't tried it in Royale, 
so I'm wondering if you've seen it work and it isn't working in this one case.

-Alex

On 10/4/18, 10:13 PM, "chembali"  wrote:

I am trying the package paths for swc for the first time. I use it quite a
lot in the Flex world. A bit confused about the -js-source-path option. I
don't see that option in mxmlc. Am I missing something?



--
Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7Cae92c5cb03f84c861e5208d62a8155ec%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636743132325036935sdata=ZrRDePbFK5U05QC3cQxYMUUjBdsFEy5tSiqwSxcmDPg%3Dreserved=0

Re: Migrating Enterprise Flex Application

I am trying the package paths for swc for the first time. I use it quite a
lot in the Flex world. A bit confused about the -js-source-path option. I
don't see that option in mxmlc. Am I missing something?



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

I am using the package paths for the first time. I use it quite a lot in the
Flex world. Bit confused about your -js-source-path. I don't see this option
in the mxmlc compiler. Am I missing something?



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-10-04 Thread Alex Harui

AdvancedTableDataGrid is normally in a SWC?  I wonder if the Royale compiler 
supports package paths instead of URIs for SWCs.  Are package paths for SWC 
components working elsewhere?You might need to use the 
-js-source-path+=com/infogix/iitap/component/flexuiplatform/controls/datagrid 
option if -js-source-path is being used elsewhere.

HTH,
-Alex 

On 10/4/18, 3:52 AM, "chembali"  wrote:

Here is another js compiler error that I am trying to resolve. My mxml
contains the following fragment.

https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Caharui%40adobe.com%7C258354eea0dc4c867ec508d629e77503%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636742471419542228sdata=61N4fppdUKBn9IxBvQiEnuaW4GkeCvHmQcmA%2Bu1p2qc%3Dreserved=0;
 xmlns:mx="library://ns.apache.org/royale/mx"
 xmlns:js="library://ns.apache.org/royale/basic"
 xmlns:html="library://ns.apache.org/royale/html"
 xmlns:j="library://ns.apache.org/royale/jewel"


xmlns:datagrid="com.infogix.iitap.component.flexuiplatform.controls.datagrid.*"
 className="IVPSchedulerView"
>



I get the error 

" Error: This tag is unexpected. It will be ignored.
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C258354eea0dc4c867ec508d629e77503%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636742471419542228sdata=ZC45waLahDAktmqXnQrY%2BdtGhy7LoFGMOMU3Jd0cttc%3Dreserved=0

Re: Migrating Enterprise Flex Application

Here is another js compiler error that I am trying to resolve. My mxml
contains the following fragment.

http://ns.adobe.com/mxml/2009;
 xmlns:mx="library://ns.apache.org/royale/mx"
 xmlns:js="library://ns.apache.org/royale/basic"
 xmlns:html="library://ns.apache.org/royale/html"
 xmlns:j="library://ns.apache.org/royale/jewel"

xmlns:datagrid="com.infogix.iitap.component.flexuiplatform.controls.datagrid.*"
 className="IVPSchedulerView"
>



I get the error 

" Error: This tag is unexpected. It will be ignored.
http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

Thank you. I will give it a try commenting out resource bundle usage.



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-10-03 Thread Alex Harui

Hi,

Royale doesn't currently support resource bundles.  It is on my list of things 
to investigate to see how hard it will be to support it.  The main challenge is 
that resource bundles are pre-compiled ABC code and we really want the raw 
strings.

Royale does have a different, lightweight sub-system for handling localized 
strings.You can see an example in manualtests/LocaleTest.

If you want to wait to see if we can support resource bundles, I think if you 
comment out all [ResourceBundle] metadata in your code you can get past this 
error (of course, at runtime the calls to get resources won't work).

HTH,
-Alex

On 10/3/18, 1:47 AM, "chembali"  wrote:

I am trying to compile a simple mxml file to js using mxmlc. Here is the 
mxml
fie.


https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Caharui%40adobe.com%7C6c38f435f91f4c05d6bd08d6290ce66c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741532705018239sdata=dAKAtP75BA66FMIKjFZM1fB3Kx%2BkoMeTipbrveFgbCA%3Dreserved=0;

xmlns:ss="com.infogix.iitap.component.scheduler.view.*"

xmlns:uipanel="com.infogix.iitap.component.flexuiplatform.controls.panel.*"

xmlns:uicore="com.infogix.iitap.component.flexuiplatform.core.*"

xmlns:uiactions="com.infogix.iitap.component.flexuiplatform.core.action.*"

xmlns:sactions="com.infogix.iitap.component.scheduler.action.*"
 title="scheduler"
 recordCount="2"
 helpUrl="ContextHelp/manage_scheduler_c.htm"
>























 



Here is the commnd that I am using to compile.

C:\devenv\GitHub\apache-royale-0.9.3\royale-asjs\js\bin\mxmlc

-load-config=C:\devenv\ivp\deflex\Components\IVPSolution\build/resources/flex/royale-config.xml
-compiler.locale=en_US
-compiler.source-path=C:\devenv\ivp\deflex\Components\Scheduler\src-flexui

-compiler.source-path=C:\devenv\ivp\deflex\Components\Scheduler/res-flexui/locale/{locale}

-compiler.js-library-path+=C:\devenv\ivp\deflex\solution-build\deflex\flexuiplatformroyale.swc

-compiler.js-library-path+=C:\devenv\ivp\deflex\solution-build\deflex\flexuiplatform-asset.swc

-compiler.js-library-path+=C:\devenv\ivp\deflex\solution-build\deflex\rulesmgmtroyale.swc

-compiler.js-library-path+=C:\devenv\ivp\deflex\solution-build\deflex\schedulerroyale.swc

-compiler.js-library-path+=C:\devenv\ivp\deflex\solution-build\deflex\baseroyale.swc

-output=C:\devenv\ivp\deflex\components\IVPSolution\build\flex\SchedulerListApp.swf
--

C:\devenv\ivp\deflex\Components\Scheduler\src-flexui\com\infogix\iitap\component\scheduler\view\SchedulerListView.mxml

The file containing compile output with the error message is attached. Can
you help me in understanding the error message and resolving it? The mxml
used to have the reference to the the Resource File ( in the compile error
). But I deleted the reference hoping that the compile would be success. But
no luck. The components used in the mxml file has been compiled to swc
library containing the js output and used in the compile command. Thank you
for your help. 

compileErr.compileErr


  







--
Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C6c38f435f91f4c05d6bd08d6290ce66c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741532705018239sdata=%2BCyQv7PztXB16giJiYHfMKwZT4z21kNLMgxxSGMcPJc%3Dreserved=0

Re: Migrating Enterprise Flex Application

2018-10-03 Thread Harbs

Without seeing your source, I’d guess the problem is related to the locale you 
are feeding into the compiler.

> On Oct 3, 2018, at 11:47 AM, chembali  wrote:
> 
> I am trying to compile a simple mxml file to js using mxmlc. Here is the mxml
> fie.
> 
> 
>  xmlns:fx="http://ns.adobe.com/mxml/2009;
> 
> xmlns:ss="com.infogix.iitap.component.scheduler.view.*"
> 
> xmlns:uipanel="com.infogix.iitap.component.flexuiplatform.controls.panel.*"
> 
> xmlns:uicore="com.infogix.iitap.component.flexuiplatform.core.*"
> 
> xmlns:uiactions="com.infogix.iitap.component.flexuiplatform.core.action.*"
> 
> xmlns:sactions="com.infogix.iitap.component.scheduler.action.*"
> title="scheduler"
> recordCount="2"
> helpUrl="ContextHelp/manage_scheduler_c.htm"
>> 
> 
>
>
>
> 
>
>
>
> 
>
>
>
> 
>
>
>
>
>
>
>isEnabled="true" />
>
>
>
> 
> 
> 
> 
> Here is the commnd that I am using to compile.
> 
> C:\devenv\GitHub\apache-royale-0.9.3\royale-asjs\js\bin\mxmlc
> -load-config=C:\devenv\ivp\deflex\Components\IVPSolution\build/resources/flex/royale-config.xml
> -compiler.locale=en_US
> -compiler.source-path=C:\devenv\ivp\deflex\Components\Scheduler\src-flexui
> -compiler.source-path=C:\devenv\ivp\deflex\Components\Scheduler/res-flexui/locale/{locale}
> -compiler.js-library-path+=C:\devenv\ivp\deflex\solution-build\deflex\flexuiplatformroyale.swc
> -compiler.js-library-path+=C:\devenv\ivp\deflex\solution-build\deflex\flexuiplatform-asset.swc
> -compiler.js-library-path+=C:\devenv\ivp\deflex\solution-build\deflex\rulesmgmtroyale.swc
> -compiler.js-library-path+=C:\devenv\ivp\deflex\solution-build\deflex\schedulerroyale.swc
> -compiler.js-library-path+=C:\devenv\ivp\deflex\solution-build\deflex\baseroyale.swc
> -output=C:\devenv\ivp\deflex\components\IVPSolution\build\flex\SchedulerListApp.swf
> --
> C:\devenv\ivp\deflex\Components\Scheduler\src-flexui\com\infogix\iitap\component\scheduler\view\SchedulerListView.mxml
> 
> The file containing compile output with the error message is attached. Can
> you help me in understanding the error message and resolving it? The mxml
> used to have the reference to the the Resource File ( in the compile error
> ). But I deleted the reference hoping that the compile would be success. But
> no luck. The components used in the mxml file has been compiled to swc
> library containing the js output and used in the compile command. Thank you
> for your help. 
> 
> compileErr.compileErr
> 
>   
> 
> 
> 
> 
> 
> 
> 
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-10-03 Thread chembali

I am trying to compile a simple mxml file to js using mxmlc. Here is the mxml
fie.


http://ns.adobe.com/mxml/2009;

xmlns:ss="com.infogix.iitap.component.scheduler.view.*"

xmlns:uipanel="com.infogix.iitap.component.flexuiplatform.controls.panel.*"

xmlns:uicore="com.infogix.iitap.component.flexuiplatform.core.*"

xmlns:uiactions="com.infogix.iitap.component.flexuiplatform.core.action.*"

xmlns:sactions="com.infogix.iitap.component.scheduler.action.*"
 title="scheduler"
 recordCount="2"
 helpUrl="ContextHelp/manage_scheduler_c.htm"
>























 



Here is the commnd that I am using to compile.

C:\devenv\GitHub\apache-royale-0.9.3\royale-asjs\js\bin\mxmlc
-load-config=C:\devenv\ivp\deflex\Components\IVPSolution\build/resources/flex/royale-config.xml
-compiler.locale=en_US
-compiler.source-path=C:\devenv\ivp\deflex\Components\Scheduler\src-flexui
-compiler.source-path=C:\devenv\ivp\deflex\Components\Scheduler/res-flexui/locale/{locale}
-compiler.js-library-path+=C:\devenv\ivp\deflex\solution-build\deflex\flexuiplatformroyale.swc
-compiler.js-library-path+=C:\devenv\ivp\deflex\solution-build\deflex\flexuiplatform-asset.swc
-compiler.js-library-path+=C:\devenv\ivp\deflex\solution-build\deflex\rulesmgmtroyale.swc
-compiler.js-library-path+=C:\devenv\ivp\deflex\solution-build\deflex\schedulerroyale.swc
-compiler.js-library-path+=C:\devenv\ivp\deflex\solution-build\deflex\baseroyale.swc
-output=C:\devenv\ivp\deflex\components\IVPSolution\build\flex\SchedulerListApp.swf
--
C:\devenv\ivp\deflex\Components\Scheduler\src-flexui\com\infogix\iitap\component\scheduler\view\SchedulerListView.mxml

The file containing compile output with the error message is attached. Can
you help me in understanding the error message and resolving it? The mxml
used to have the reference to the the Resource File ( in the compile error
). But I deleted the reference hoping that the compile would be success. But
no luck. The components used in the mxml file has been compiled to swc
library containing the js output and used in the compile command. Thank you
for your help. 

compileErr.compileErr

  







--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-08-09 Thread Carlos Rovira

If you check the APIs AS3 doc you'll see there's about 9 methods in the
interface while in the Royale version of the class we have only about 3 of
them.

for example:
https://help.adobe.com/es_ES/FlashPlatform/reference/actionscript/3/flash/utils/IDataOutput.html

2018-08-08 20:16 GMT+02:00 Harbs :

> What is missing?
>
> > On Aug 8, 2018, at 8:28 PM, Carlos Rovira 
> wrote:
> >
> > Hi,
> >
> > just notice that current versions of IDataInput and IDataOutput are
> > incomplete. The rest of missed methods should be added and as well added
> to
> > implementor classes
> >
> > just my 2ctns
> >
> > 2018-08-08 9:29 GMT+02:00 Alex Harui :
> >
> >> In the develop branch, there is an IDataInput/IDataOutput in the Network
> >> SWC.  I will try to cherry pick that into feature/MXRoyale after I
> finish
> >> up another thing I'm currently working on.  You could probably get the
> >> nightly from the develop branch and use that Network.swc.
> >>
> >> HTH,
> >> -Alex
> >>
> >> On 8/7/18, 11:44 PM, "chembali"  wrote:
> >>
> >>My current code uses IDataInput/iDataOutput classes in Flash util.
> What
> >>classes can I use to replace them? I saw IBinaryDataOutput in Royale,
> >> but it
> >>does not have the writeObject() and readObject() apis.
> >>
> >>
> >>
> >>--
> >>Sent from: https://na01.safelinks.protection.outlook.com/?url=
> >> http%3A%2F%2Fapache-royale-development.20373.n8.nabble.
> >> com%2Fdata=02%7C01%7Caharui%40adobe.com%
> >> 7C0673e721af074e9eb88508d5fcfa5b3f%7Cfa7b1b5a7b34438794aed2c178de
> >> cee1%7C0%7C1%7C636693074577954430sdata=UVE28CmyyV975aj%
> >> 2FaFaSQaxXaY30Ifd3fUx1of8ZLpM%3Dreserved=0
> >>
> >>
> >>
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
>
>


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

Re: Migrating Enterprise Flex Application

2018-08-08 Thread Harbs

What is missing?

> On Aug 8, 2018, at 8:28 PM, Carlos Rovira  wrote:
> 
> Hi,
> 
> just notice that current versions of IDataInput and IDataOutput are
> incomplete. The rest of missed methods should be added and as well added to
> implementor classes
> 
> just my 2ctns
> 
> 2018-08-08 9:29 GMT+02:00 Alex Harui :
> 
>> In the develop branch, there is an IDataInput/IDataOutput in the Network
>> SWC.  I will try to cherry pick that into feature/MXRoyale after I finish
>> up another thing I'm currently working on.  You could probably get the
>> nightly from the develop branch and use that Network.swc.
>> 
>> HTH,
>> -Alex
>> 
>> On 8/7/18, 11:44 PM, "chembali"  wrote:
>> 
>>My current code uses IDataInput/iDataOutput classes in Flash util. What
>>classes can I use to replace them? I saw IBinaryDataOutput in Royale,
>> but it
>>does not have the writeObject() and readObject() apis.
>> 
>> 
>> 
>>--
>>Sent from: https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fapache-royale-development.20373.n8.nabble.
>> com%2Fdata=02%7C01%7Caharui%40adobe.com%
>> 7C0673e721af074e9eb88508d5fcfa5b3f%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C1%7C636693074577954430sdata=UVE28CmyyV975aj%
>> 2FaFaSQaxXaY30Ifd3fUx1of8ZLpM%3Dreserved=0
>> 
>> 
>> 
> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: Migrating Enterprise Flex Application

2018-08-08 Thread Carlos Rovira

Hi,

just notice that current versions of IDataInput and IDataOutput are
incomplete. The rest of missed methods should be added and as well added to
implementor classes

just my 2ctns

2018-08-08 9:29 GMT+02:00 Alex Harui :

> In the develop branch, there is an IDataInput/IDataOutput in the Network
> SWC.  I will try to cherry pick that into feature/MXRoyale after I finish
> up another thing I'm currently working on.  You could probably get the
> nightly from the develop branch and use that Network.swc.
>
> HTH,
> -Alex
>
> On 8/7/18, 11:44 PM, "chembali"  wrote:
>
> My current code uses IDataInput/iDataOutput classes in Flash util. What
> classes can I use to replace them? I saw IBinaryDataOutput in Royale,
> but it
> does not have the writeObject() and readObject() apis.
>
>
>
> --
> Sent from: https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fapache-royale-development.20373.n8.nabble.
> com%2Fdata=02%7C01%7Caharui%40adobe.com%
> 7C0673e721af074e9eb88508d5fcfa5b3f%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C1%7C636693074577954430sdata=UVE28CmyyV975aj%
> 2FaFaSQaxXaY30Ifd3fUx1of8ZLpM%3Dreserved=0
>
>
>


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

Re: Migrating Enterprise Flex Application

2018-08-08 Thread Alex Harui

In the develop branch, there is an IDataInput/IDataOutput in the Network SWC.  
I will try to cherry pick that into feature/MXRoyale after I finish up another 
thing I'm currently working on.  You could probably get the nightly from the 
develop branch and use that Network.swc.

HTH,
-Alex

On 8/7/18, 11:44 PM, "chembali"  wrote:

My current code uses IDataInput/iDataOutput classes in Flash util. What
classes can I use to replace them? I saw IBinaryDataOutput in Royale, but it
does not have the writeObject() and readObject() apis.



--
Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C0673e721af074e9eb88508d5fcfa5b3f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636693074577954430sdata=UVE28CmyyV975aj%2FaFaSQaxXaY30Ifd3fUx1of8ZLpM%3Dreserved=0

Re: Migrating Enterprise Flex Application

2018-08-08 Thread chembali

My current code uses IDataInput/iDataOutput classes in Flash util. What
classes can I use to replace them? I saw IBinaryDataOutput in Royale, but it
does not have the writeObject() and readObject() apis.



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-08-06 Thread Alex Harui

I pushed changes that should eliminate the ResourceBundle errors and report 
better info on the NPE.

HTH,
-Alex

On 8/6/18, 12:14 AM, "Alex Harui"  wrote:

Any committer can clean up the resource bundle issues.  I won't have time 
tonight.

More interesting is the null pointer exception.  You may have to 
temporarily comment out some of your MXML in order to determine what is causing 
that exception.

Thanks,
-Alex

On 8/5/18, 11:42 PM, "chembali"  wrote:

Tried with the latest build. The earlier error is gone. Getting another
resource bundle error now. Do you have to comment out more code?

Using Royale Compiler codebase:
C:\devenv\GitHub\apache-royale-0.9.3\royale-asjs
\js\bin\..\..
Using Royale SDK: C:\devenv\GitHub\apache-royale-0.9.3\royale-asjs\
MXMLJSC

-sdk-js-lib=C:\devenv\GitHub\apache-royale-0.9.3\royale-asjs\\frameworks\js\Roya
le\generated-sources
-compiler.source-path=C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src
C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src/BlazeDsExample.mxml
Loading configuration:
C:\devenv\GitHub\apache-royale-0.9.3\royale-asjs\framewor
ks\royale-config.xml

scanning for overrides: IFlexModuleFactory
scanning for overrides: IEventDispatcher
scanning for overrides: IChildList
scanning for overrides: ISystemManager
scanning for overrides: SystemManagerBase
scanning for overrides: SystemManager
scanning for overrides: IRenderedObject
scanning for overrides: IChild
scanning for overrides: IStrand
scanning for overrides: IUIBase
scanning for overrides: IFlexDisplayObject
scanning for overrides: IUIComponent
scanning for overrides: IBead
scanning for overrides: IParent
scanning for overrides: IFlexInfo
scanning for overrides: IPopUpHost
scanning for overrides: IContainer
scanning for overrides: IContainerBaseStrandChildrenHost
scanning for overrides: IContentViewHost
scanning for overrides: ILayoutParent
scanning for overrides: ILayoutView
scanning for overrides: IMXMLDocument
scanning for overrides: IDataRenderer
scanning for overrides: HTMLElementWrapper
scanning for overrides: ILayoutChild
scanning for overrides: IParentIUIBase
scanning for overrides: IRoyaleElement
scanning for overrides: IStrandWithModel
scanning for overrides: IStrandWithModelView
scanning for overrides: IStyleableObject
scanning for overrides: UIBase
scanning for overrides: IStatesObject
scanning for overrides: IFlexModule
scanning for overrides: IInvalidating
scanning for overrides: IVisualElement
scanning for overrides: UIComponent
scanning for overrides: MethodQueueElement
scanning for overrides: IFocusManagerContainer
scanning for overrides: Container
scanning for overrides: Application
scanning for overrides: EventDispatcher
scanning for overrides: IStyleManager2
scanning for overrides: StyleManagerImpl
scanning for overrides: StyleEventDispatcher
scanning for overrides: CSSClass
scanning for overrides: CSSFactory
scanning for overrides: CSSDataType
scanning for overrides: ContainerBaseStrandChildren
scanning for overrides: ContainerContentArea
scanning for overrides: DataBindingBase
scanning for overrides: ApplicationDataBinding
scanning for overrides: EdgeData
scanning for overrides: IValuesImpl
scanning for overrides: IBorderPaddingMarginValuesImpl
scanning for overrides: ICSSImpl
scanning for overrides: AllCSSValuesImpl
scanning for overrides: CSSClass
scanning for overrides: CSSFactory
scanning for overrides: CSSDataType
scanning for overrides: CallLaterBead
scanning for overrides: IBeadController
scanning for overrides: IBeadLayout
scanning for overrides: IBeadModel
scanning for overrides: IBeadView
scanning for overrides: ILayoutHost
scanning for overrides: IMeasurementBead
scanning for overrides: IStatesImpl
scanning for overrides: StageProxy
scanning for overrides: TextLineMetrics
scanning for overrides: ValuesManager
scanning for overrides: MouseEventConverter
scanning for overrides: IRoyaleEvent
scanning for overrides: Event
scanning for overrides: IBrowserEvent
scanning for overrides: KeyboardEvent
scanning for overrides: MouseEvent
scanning for overrides: ValueChangeEvent
scanning for overrides: ValueEvent
scanning for overrides: Rectangle
scanning for overrides: MXMLDataInterpreter

Re: Migrating Enterprise Flex Application

2018-08-06 Thread Alex Harui

Any committer can clean up the resource bundle issues.  I won't have time 
tonight.

More interesting is the null pointer exception.  You may have to temporarily 
comment out some of your MXML in order to determine what is causing that 
exception.

Thanks,
-Alex

On 8/5/18, 11:42 PM, "chembali"  wrote:

Tried with the latest build. The earlier error is gone. Getting another
resource bundle error now. Do you have to comment out more code?

Using Royale Compiler codebase:
C:\devenv\GitHub\apache-royale-0.9.3\royale-asjs
\js\bin\..\..
Using Royale SDK: C:\devenv\GitHub\apache-royale-0.9.3\royale-asjs\
MXMLJSC

-sdk-js-lib=C:\devenv\GitHub\apache-royale-0.9.3\royale-asjs\\frameworks\js\Roya
le\generated-sources
-compiler.source-path=C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src
C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src/BlazeDsExample.mxml
Loading configuration:
C:\devenv\GitHub\apache-royale-0.9.3\royale-asjs\framewor
ks\royale-config.xml

scanning for overrides: IFlexModuleFactory
scanning for overrides: IEventDispatcher
scanning for overrides: IChildList
scanning for overrides: ISystemManager
scanning for overrides: SystemManagerBase
scanning for overrides: SystemManager
scanning for overrides: IRenderedObject
scanning for overrides: IChild
scanning for overrides: IStrand
scanning for overrides: IUIBase
scanning for overrides: IFlexDisplayObject
scanning for overrides: IUIComponent
scanning for overrides: IBead
scanning for overrides: IParent
scanning for overrides: IFlexInfo
scanning for overrides: IPopUpHost
scanning for overrides: IContainer
scanning for overrides: IContainerBaseStrandChildrenHost
scanning for overrides: IContentViewHost
scanning for overrides: ILayoutParent
scanning for overrides: ILayoutView
scanning for overrides: IMXMLDocument
scanning for overrides: IDataRenderer
scanning for overrides: HTMLElementWrapper
scanning for overrides: ILayoutChild
scanning for overrides: IParentIUIBase
scanning for overrides: IRoyaleElement
scanning for overrides: IStrandWithModel
scanning for overrides: IStrandWithModelView
scanning for overrides: IStyleableObject
scanning for overrides: UIBase
scanning for overrides: IStatesObject
scanning for overrides: IFlexModule
scanning for overrides: IInvalidating
scanning for overrides: IVisualElement
scanning for overrides: UIComponent
scanning for overrides: MethodQueueElement
scanning for overrides: IFocusManagerContainer
scanning for overrides: Container
scanning for overrides: Application
scanning for overrides: EventDispatcher
scanning for overrides: IStyleManager2
scanning for overrides: StyleManagerImpl
scanning for overrides: StyleEventDispatcher
scanning for overrides: CSSClass
scanning for overrides: CSSFactory
scanning for overrides: CSSDataType
scanning for overrides: ContainerBaseStrandChildren
scanning for overrides: ContainerContentArea
scanning for overrides: DataBindingBase
scanning for overrides: ApplicationDataBinding
scanning for overrides: EdgeData
scanning for overrides: IValuesImpl
scanning for overrides: IBorderPaddingMarginValuesImpl
scanning for overrides: ICSSImpl
scanning for overrides: AllCSSValuesImpl
scanning for overrides: CSSClass
scanning for overrides: CSSFactory
scanning for overrides: CSSDataType
scanning for overrides: CallLaterBead
scanning for overrides: IBeadController
scanning for overrides: IBeadLayout
scanning for overrides: IBeadModel
scanning for overrides: IBeadView
scanning for overrides: ILayoutHost
scanning for overrides: IMeasurementBead
scanning for overrides: IStatesImpl
scanning for overrides: StageProxy
scanning for overrides: TextLineMetrics
scanning for overrides: ValuesManager
scanning for overrides: MouseEventConverter
scanning for overrides: IRoyaleEvent
scanning for overrides: Event
scanning for overrides: IBrowserEvent
scanning for overrides: KeyboardEvent
scanning for overrides: MouseEvent
scanning for overrides: ValueChangeEvent
scanning for overrides: ValueEvent
scanning for overrides: Rectangle
scanning for overrides: MXMLDataInterpreter
scanning for overrides: IChartSeries
scanning for overrides: ColumnSeries
scanning for overrides: ColumnSeries
scanning for overrides: GroupBase
scanning for overrides: ContainerBase
scanning for overrides: DataContainerBase
scanning for overrides: IStrandWithPresentationModel
scanning for overrides: DataContainer
scanning for overrides: List
scanning for overrides: IChart
scanning for overrides: ChartBase
scanning for overrides: ChartBase
scanning for overrides: BarChart
scanning for overrides: CategoryAxis

Re: Migrating Enterprise Flex Application

2018-08-06 Thread chembali

Tried with the latest build. The earlier error is gone. Getting another
resource bundle error now. Do you have to comment out more code?

Using Royale Compiler codebase:
C:\devenv\GitHub\apache-royale-0.9.3\royale-asjs
\js\bin\..\..
Using Royale SDK: C:\devenv\GitHub\apache-royale-0.9.3\royale-asjs\
MXMLJSC
-sdk-js-lib=C:\devenv\GitHub\apache-royale-0.9.3\royale-asjs\\frameworks\js\Roya
le\generated-sources
-compiler.source-path=C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src
C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src/BlazeDsExample.mxml
Loading configuration:
C:\devenv\GitHub\apache-royale-0.9.3\royale-asjs\framewor
ks\royale-config.xml

scanning for overrides: IFlexModuleFactory
scanning for overrides: IEventDispatcher
scanning for overrides: IChildList
scanning for overrides: ISystemManager
scanning for overrides: SystemManagerBase
scanning for overrides: SystemManager
scanning for overrides: IRenderedObject
scanning for overrides: IChild
scanning for overrides: IStrand
scanning for overrides: IUIBase
scanning for overrides: IFlexDisplayObject
scanning for overrides: IUIComponent
scanning for overrides: IBead
scanning for overrides: IParent
scanning for overrides: IFlexInfo
scanning for overrides: IPopUpHost
scanning for overrides: IContainer
scanning for overrides: IContainerBaseStrandChildrenHost
scanning for overrides: IContentViewHost
scanning for overrides: ILayoutParent
scanning for overrides: ILayoutView
scanning for overrides: IMXMLDocument
scanning for overrides: IDataRenderer
scanning for overrides: HTMLElementWrapper
scanning for overrides: ILayoutChild
scanning for overrides: IParentIUIBase
scanning for overrides: IRoyaleElement
scanning for overrides: IStrandWithModel
scanning for overrides: IStrandWithModelView
scanning for overrides: IStyleableObject
scanning for overrides: UIBase
scanning for overrides: IStatesObject
scanning for overrides: IFlexModule
scanning for overrides: IInvalidating
scanning for overrides: IVisualElement
scanning for overrides: UIComponent
scanning for overrides: MethodQueueElement
scanning for overrides: IFocusManagerContainer
scanning for overrides: Container
scanning for overrides: Application
scanning for overrides: EventDispatcher
scanning for overrides: IStyleManager2
scanning for overrides: StyleManagerImpl
scanning for overrides: StyleEventDispatcher
scanning for overrides: CSSClass
scanning for overrides: CSSFactory
scanning for overrides: CSSDataType
scanning for overrides: ContainerBaseStrandChildren
scanning for overrides: ContainerContentArea
scanning for overrides: DataBindingBase
scanning for overrides: ApplicationDataBinding
scanning for overrides: EdgeData
scanning for overrides: IValuesImpl
scanning for overrides: IBorderPaddingMarginValuesImpl
scanning for overrides: ICSSImpl
scanning for overrides: AllCSSValuesImpl
scanning for overrides: CSSClass
scanning for overrides: CSSFactory
scanning for overrides: CSSDataType
scanning for overrides: CallLaterBead
scanning for overrides: IBeadController
scanning for overrides: IBeadLayout
scanning for overrides: IBeadModel
scanning for overrides: IBeadView
scanning for overrides: ILayoutHost
scanning for overrides: IMeasurementBead
scanning for overrides: IStatesImpl
scanning for overrides: StageProxy
scanning for overrides: TextLineMetrics
scanning for overrides: ValuesManager
scanning for overrides: MouseEventConverter
scanning for overrides: IRoyaleEvent
scanning for overrides: Event
scanning for overrides: IBrowserEvent
scanning for overrides: KeyboardEvent
scanning for overrides: MouseEvent
scanning for overrides: ValueChangeEvent
scanning for overrides: ValueEvent
scanning for overrides: Rectangle
scanning for overrides: MXMLDataInterpreter
scanning for overrides: IChartSeries
scanning for overrides: ColumnSeries
scanning for overrides: ColumnSeries
scanning for overrides: GroupBase
scanning for overrides: ContainerBase
scanning for overrides: DataContainerBase
scanning for overrides: IStrandWithPresentationModel
scanning for overrides: DataContainer
scanning for overrides: List
scanning for overrides: IChart
scanning for overrides: ChartBase
scanning for overrides: ChartBase
scanning for overrides: BarChart
scanning for overrides: CategoryAxis
scanning for overrides: ListCollectionView
scanning for overrides: ArrayCollection
scanning for overrides: LayoutBase
scanning for overrides: BoxLayout
scanning for overrides: ApplicationLayout
scanning for overrides: Box
scanning for overrides: VBox
scanning for overrides: ToolTipBead
scanning for overrides: ToolTipBead
scanning for overrides: Button
scanning for overrides: ContainerLayout
scanning for overrides: EdgeMetrics
scanning for overrides: AllCSSStyles
scanning for overrides: FlexCSSStyles
scanning for overrides: FlexGlobals
scanning for overrides: ScrollPolicy
scanning for overrides: IGraphicShape
scanning for overrides: GraphicShape
scanning for overrides: ICompoundGraphic
scanning for overrides: CompoundGraphic
scanning for overrides:

Re: Migrating Enterprise Flex Application

2018-08-03 Thread Alex Harui

ResourceBundles should be commented out, but we missed that one.  I just 
commented it out and pushed the change.  Should be in the nightly build for the 
MXRoyale branch.

This kind of bug wouldn't matter if you use Ant or Maven.  Just use the one you 
prefer.

HTH,
-Alex

On 8/3/18, 2:00 AM, "chembali"  wrote:

Tried js/bin/mxmlc. Getting the following error now.


C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src>C:\devenv\GitHub\royale-asjs/j
s/bin/mxmlc
-compiler.source-path=C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\
src C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src/BlazeDsExample.mxml
Using Royale Compiler codebase: C:\devenv\GitHub\royale-asjs\js\bin\..\..
Using Royale SDK: C:\devenv\GitHub\royale-asjs
MXMLJSC

-sdk-js-lib=C:\devenv\GitHub\royale-asjs\frameworks\js\Royale\generated-sources
-compiler.source-path=C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src
C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src/BlazeDsExample.mxml
Error: Unable to resolve resource bundle 'rpc'


4.925945806 seconds.

Any ideas?



--
Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7Ce4ce53cb24ff46ca02c908d5f91f8608%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636688836157078382sdata=gwEW1x26lq8h%2Ff18BPS6IPShWj6QOYchM3zvaGDa7TU%3Dreserved=0

Re: Migrating Enterprise Flex Application

2018-08-03 Thread chembali

Thank you Carlos for the input. I am trying to migrate a sample BlazeDS
application ( which is working fine in Flex ) to Royale in order to identify
the steps/changes needed. Here is my orginal mxml that is working in Flex.


http://www.adobe.com/2006/mxml; layout="absolute">














  


I have changed the mx name space to
xmlns:mx="library://ns.apache.org/royale/mx in the above mxml. I want to use
the Royale JS compiler and compile the above mxml and identify the changes
required to get this sample app working in Royale. I hope you understand
what I am trying to accomplish here.





--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-08-03 Thread Carlos Rovira

Hi,

I don't have experience with using mxmlc directly, don't know your reasons,
but if you want to just build your project, maybe you can consider Maven
since I think abstracts you from that complexity. Check this link:

Build Apache Royale with Maven


If you follow the maven way you have the AMF RemoteObject projects examples
described here :

https://github.com/apache/royale-asjs/wiki/Apache-Royale-communication-with-AMF-and-RemoteObject

Bonus link to set up the environment quickly in Mac OS

Mac OS X Development Environment In 5'!



Hope that helps

Best

Carlos



2018-08-03 11:00 GMT+02:00 chembali :

> Tried js/bin/mxmlc. Getting the following error now.
>
> C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src>C:\devenv\
> GitHub\royale-asjs/j
> s/bin/mxmlc
> -compiler.source-path=C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\
> src C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src/BlazeDsExample.mxml
> Using Royale Compiler codebase: C:\devenv\GitHub\royale-asjs\js\bin\..\..
> Using Royale SDK: C:\devenv\GitHub\royale-asjs
> MXMLJSC
> -sdk-js-lib=C:\devenv\GitHub\royale-asjs\frameworks\js\
> Royale\generated-sources
> -compiler.source-path=C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src
> C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src/BlazeDsExample.mxml
> Error: Unable to resolve resource bundle 'rpc'
>
>
> 4.925945806 seconds.
>
> Any ideas?
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>



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

Re: Migrating Enterprise Flex Application

2018-08-03 Thread chembali

Tried js/bin/mxmlc. Getting the following error now.

C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src>C:\devenv\GitHub\royale-asjs/j
s/bin/mxmlc
-compiler.source-path=C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\
src C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src/BlazeDsExample.mxml
Using Royale Compiler codebase: C:\devenv\GitHub\royale-asjs\js\bin\..\..
Using Royale SDK: C:\devenv\GitHub\royale-asjs
MXMLJSC
-sdk-js-lib=C:\devenv\GitHub\royale-asjs\frameworks\js\Royale\generated-sources
-compiler.source-path=C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src
C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src/BlazeDsExample.mxml
Error: Unable to resolve resource bundle 'rpc'


4.925945806 seconds.

Any ideas?



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-31 Thread Alex Harui

Use js/bin/mxmlc insead of bin/mxmlc.

HTH,
-Alex

On 7/31/18, 4:00 AM, "chembali"  wrote:

I tried to run the Royale mxmlc compiler using the below command and it
errors out.


C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src>C:\devenv\GitHub\royale-asjs/b
in/mxmlc
-compiler.source-path=C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src
 -include-sources+=C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src\com 
C:\dev
env\BlazeDSRemoteObjects\BlazeDsExample\src/BlazeDsExample.mxml

Using Royale codebase: C:\devenv\GitHub\royale-asjs\js\bin\..\..
Using Royale SDK: C:\devenv\GitHub\royale-asjs
Unknown tag:compiler.targets
Loading configuration:
C:\devenv\GitHub\royale-asjs\frameworks\royale-config.xml


C:\devenv\GitHub\royale-asjs\frameworks\royale-config.xml(33): col: 0 Error:
unk
nown configuration variable 'compiler.targets'.
C:\devenv\GitHub\royale-asjs\frameworks\royale-config.xml (line: 33)

  


I have the following entry in the royale-config.xml line 33. Any ideas?


  
  JSRoyale




--
Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7Cd3b03ba63e984988b88608d5f6d4db24%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636686316438465559sdata=e6CXv04UakebtKNZL2lHw%2FDpgosU8kze1ugiZjXeXco%3Dreserved=0

Re: Migrating Enterprise Flex Application

2018-07-31 Thread chembali

I tried to run the Royale mxmlc compiler using the below command and it
errors out.

C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src>C:\devenv\GitHub\royale-asjs/b
in/mxmlc
-compiler.source-path=C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src
 -include-sources+=C:\devenv\BlazeDSRemoteObjects\BlazeDsExample\src\com 
C:\dev
env\BlazeDSRemoteObjects\BlazeDsExample\src/BlazeDsExample.mxml

Using Royale codebase: C:\devenv\GitHub\royale-asjs\js\bin\..\..
Using Royale SDK: C:\devenv\GitHub\royale-asjs
Unknown tag:compiler.targets
Loading configuration:
C:\devenv\GitHub\royale-asjs\frameworks\royale-config.xml


C:\devenv\GitHub\royale-asjs\frameworks\royale-config.xml(33): col: 0 Error:
unk
nown configuration variable 'compiler.targets'.
C:\devenv\GitHub\royale-asjs\frameworks\royale-config.xml (line: 33)

  


I have the following entry in the royale-config.xml line 33. Any ideas?


  
  JSRoyale




--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-24 Thread Alex Harui

There is org.apache.royale.utils.ObjectMap instead of Dictionary, but it may 
not work correctly on IE11.

There is org.apache.royale.reflection.getQualifiedClassName and 
getQualifiedSuperclassName

There is org.apache.royale.textLayout instead of flashx.textLayout.

There is org.apache.royale.utils.BinaryData instead of ByteArray.  There is an 
IDataInput/iDataOutput but I think it needs refactoring.

If you don't want to port your flash.xml to E4x, you could write an emulation 
for it.

HTH,
-Alex

On 7/24/18, 5:07 AM, "Alina Kazi"  wrote:

Hi chembali,

Like org.apache.royale.utils.Timer  instead of flash.utils.Timer  ,
org.apache.royale.utils.Proxy instead of flash.utils.Proxy are API's
available in different Projects(like Core)
You can use them, If these classes fulfill your requirement  otherwise make
mx emulations for them.

You can use E4x instead of flash.xml

Thanks,
Alina Kazi

-Original Message-
From: chembali [mailto:chemb...@hotmail.com] 
Sent: Tuesday, July 24, 2018 3:09 PM
To: dev@royale.apache.org
    Subject: Re: Migrating Enterprise Flex Application

How do I migrate the flash.util, flash.xml, flashx.text etc APIs in my
existing application?



--
Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7Ca2127a412f674c94167a08d5f15e115f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636680308701005597sdata=4tyutKcCpsdLZRjAdB%2FI%2FRYCh08JCi9o3i0QtsfsHZ0%3Dreserved=0

RE: Migrating Enterprise Flex Application

2018-07-24 Thread Alina Kazi

Hi chembali,

Like org.apache.royale.utils.Timer  instead of flash.utils.Timer  ,
org.apache.royale.utils.Proxy instead of flash.utils.Proxy are API's
available in different Projects(like Core)
You can use them, If these classes fulfill your requirement  otherwise make
mx emulations for them.

You can use E4x instead of flash.xml

Thanks,
Alina Kazi

-Original Message-
From: chembali [mailto:chemb...@hotmail.com] 
Sent: Tuesday, July 24, 2018 3:09 PM
To: dev@royale.apache.org
Subject: Re: Migrating Enterprise Flex Application

How do I migrate the flash.util, flash.xml, flashx.text etc APIs in my
existing application?



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-24 Thread chembali

How do I migrate the flash.util, flash.xml, flashx.text etc APIs in my
existing application?



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-23 Thread chembali

I have generated API reports for another Flex application that I am trying to
migrate to Royale. Please see the attached reports.

reportFlexACRRepository.txt

  
reportFlexDataMart.txt

  
reportFlexDataWarehouse.txt

  
reportFlexDimension.txt

  
reportFlexIVPAuditTrail.txt

  
reportFlexIVPBase.txt

  
reportFlexIVProcess.txt

  
reportFlexIVPSolution.txt

  
reportFlexIVPSystem.txt

  
reportFlexReportFramework.txt

  
reportFlexSourceSystem.txt

  
reportFlexVisualization.txt

  

Can you please come up with the latest list of components/APIs need to be
emulated?



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-23 Thread Alex Harui

Please comment out parts of your build script to build only one SWC. The
output you posted seems to be running builds for multiple SWCs in parallel.

Thanks,
-Alex

On 7/23/18, 12:23 AM, "chembali" wrote:

I just tried to run my application gradle script to build. I modified the
FLEX_HOME in the script to point to the ROYALE install home. I have the
ROYALE installed under C:\devenv\GitHub folder. The output is attached.
RoyaleCompileOutput.txt

The application gradle scripts actually call the flex ANT tasks to do the
compile. Can you spot any mistakes that I am doing here? I noticed one thing
in the output. For e.g. after the execution of following command, the
C:\devenv\ii\trunk\components\Dashboards\build\flex\dashboards-asset.sw
c is not getting generated.

Execute:Java13CommandLauncher: Executing 'C:\java\java8\jre\bin\java.exe'
with a
rguments:
'-Droyalelib=C:/devenv/GitHub/royale-asjs'
'-classpath'
'C:\devenv\GitHub\royale-asjs\js\lib\jsc.jar'
'org.apache.royale.compiler.clients.COMPJSC'
'-compiler.incremental=true'
'+royalelib=C:/devenv/GitHub/royale-asjs/frameworks/'
'-compiler.locale='

'-output=C:\devenv\ii\trunk\components\Dashboards\build\flex\dashboards-asset.sw
c'

The ' characters around the executable and arguments are
not part of the command.

--
Sent from:
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7Cf4465a4069d446e0bd2208d5f06d1e30%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636679273804354416sdata=LB6iTI86DCPZn7bU6pMTXHn5o5xekxtkqsQjXpxaKpY%3Dreserved=0

Re: Migrating Enterprise Flex Application

2018-07-23 Thread chembali

I just tried to run my application gradle script to build. I modified the
FLEX_HOME in the script to point to the ROYALE install home. I have the
ROYALE installed under C:\devenv\GitHub folder. The output is attached. 
RoyaleCompileOutput.txt

  

The application gradle scripts actually call the flex ANT tasks to do the
compile. Can you spot any mistakes that I am doing here? I noticed one thing
in the output. For e.g. after the execution of following command, the
C:\devenv\ii\trunk\components\Dashboards\build\flex\dashboards-asset.sw
c is not getting generated. 

Execute:Java13CommandLauncher: Executing 'C:\java\java8\jre\bin\java.exe'
with a
rguments:
'-Droyalelib=C:/devenv/GitHub/royale-asjs'
'-classpath'
'C:\devenv\GitHub\royale-asjs\js\lib\jsc.jar'
'org.apache.royale.compiler.clients.COMPJSC'
'-compiler.incremental=true'
'+royalelib=C:/devenv/GitHub/royale-asjs/frameworks/'
'-compiler.locale='
'-output=C:\devenv\ii\trunk\components\Dashboards\build\flex\dashboards-asset.sw
c'

The ' characters around the executable and arguments are
not part of the command.



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-22 Thread Alex Harui

Hi Carlos,

IMO, Jewel has lots of cool new components, but the Emulation Components don't 
need a Drawer view, they need a DataGridView.  Fitting Jewel views for 
Button/CheckBox/TextInput onto Emulation Components will probably work.  The 
real test would be trying something like DataGrid.

My 2 cents,
-Alex

On 7/22/18, 2:11 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" 
 wrote:

Hi Alex,

I think Jewel has now several components, so my perception is that we don't
need to wait much more. I mean we have around 15 Jewel components?... I
think it's time so we can see what things are still needed.

Just my opinion, but don't want to make anyone precipitate if don't think
is the time...

Thanks

Carlos



2018-07-19 19:21 GMT+02:00 Alex Harui :

> Hi Carlos,
>
> Until Jewel has more of the views for existing Flex controls, it isn't
> worth trying to re-use Jewel view beads in the emulation components.  Once
> you have more of them working, then we'll simply try them and fix bugs.
>
> -Alex
>
> On 7/19/18, 6:42 AM, "carlos.rov...@gmail.com on behalf of Carlos
> Rovira" 
> wrote:
>
> Hi Alex,
>
> about trying to use Jewel as view part, I think we should trace a
> plan. I
> still have work in my TODO list, for example I think my next stop is
> Jewel
> DateFiels and Jewel DropDownList/ComboBox... but I still want to try
> the
> "exploded" component route. So using StyledUIBase in MXML adding beads
> I
> can get a Jewel Button, a Jewel Slider and so on...
>
> But as well although I think I'll not use emulation components on our
> App,
> I think will be good if I must have some rules into account to make
> Jewel
> visualization reusable.
>
> For this I think we should create a thread, and maybe a example 
project
> where we could work together and make the convergence of code 
possible.
>
> I think one problem is that if we expect from others to code what we
> have
> in mind, that will never happen, since I think although we share a
> "macro"
> view perspective, in the "micro" view we all have, as normal, 
different
> ways of approach, so the only way I see is to join forces in
> integrating
> things, more over where you have a huge knowledge of things happening
> in
> emulation, while I have the same on things happening on Jewel.
>
> Thoughts?
>
>
>
>
> Carlos
>
>
>
>
> 2018-07-19 9:35 GMT+02:00 Alex Harui :
>
> > I think you can look at mx.controls.DateField and
> > mx.controls.NumericStepper.  The key piece is their entries in the
> > defaults.css in the MXRoyale project.  That dictates which beads are
> used.
> > If a bead has a package name starting with mx, then it is probably a
> > subclass of an org.apache.royale bead.
> >
> > I hope to finish up MenuBar shortly and then try to write up a wiki
> page
> > or something about what it takes to get these emulation components 
to
> > function.
> >
> > HTH,
> > -Alex
> >
> > On 7/18/18, 9:24 PM, "chembali"  wrote:
> >
> > Very helpful posts indeed. Can you tell me a couple of classic
> > emulation
> > examples that I can look at? I am hoping to take a look at them
> and
> > understand the pattern.
> >
> >
> >
> > --
> > Sent from: https://na01.safelinks.protection.outlook.com/?url=
> > http%3A%2F%2Fapache-royale-development.20373.n8.nabble.
> > com%2Fdata=02%7C01%7Caharui%40adobe.com%
> > 7C5260d6e737744f16b63008d5ed2f80af%7Cfa7b1b5a7b34438794aed2c178de
> > cee1%7C0%7C1%7C636675710635107707sdata=
> jDCl3Gak0jGgzFIzHcgiDs0rfFzsjJ
> > q3e6PgCn5Sy8g%3Dreserved=0
> >
> >
> >
>
>
> --
> Carlos Rovira
> https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%
> 7C01%7Caharui%40adobe.com%7C09c8f82f80be4a9fafa908d5ed7d80cb%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636676045646662630sdata=
> kT0BJi8rrYpP7DPz1z0Se5tTGNSofmduvvVD6IcmPtk%3Dreserved=0
>
>
>


-- 
Carlos Rovira

https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Ca7d16ed43a3846ca053008d5f017a899%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636678906761736958sdata=XkcaoPYP0qGLKaC7VHC5mlBAqW%2BXzNHfIRQ%2FaFnYIUo%3Dreserved=0

Re: Migrating Enterprise Flex Application

2018-07-22 Thread Carlos Rovira

Hi Alex,

I think Jewel has now several components, so my perception is that we don't
need to wait much more. I mean we have around 15 Jewel components?... I
think it's time so we can see what things are still needed.

Just my opinion, but don't want to make anyone precipitate if don't think
is the time...

Thanks

Carlos



2018-07-19 19:21 GMT+02:00 Alex Harui :

> Hi Carlos,
>
> Until Jewel has more of the views for existing Flex controls, it isn't
> worth trying to re-use Jewel view beads in the emulation components.  Once
> you have more of them working, then we'll simply try them and fix bugs.
>
> -Alex
>
> On 7/19/18, 6:42 AM, "carlos.rov...@gmail.com on behalf of Carlos
> Rovira" 
> wrote:
>
> Hi Alex,
>
> about trying to use Jewel as view part, I think we should trace a
> plan. I
> still have work in my TODO list, for example I think my next stop is
> Jewel
> DateFiels and Jewel DropDownList/ComboBox... but I still want to try
> the
> "exploded" component route. So using StyledUIBase in MXML adding beads
> I
> can get a Jewel Button, a Jewel Slider and so on...
>
> But as well although I think I'll not use emulation components on our
> App,
> I think will be good if I must have some rules into account to make
> Jewel
> visualization reusable.
>
> For this I think we should create a thread, and maybe a example project
> where we could work together and make the convergence of code possible.
>
> I think one problem is that if we expect from others to code what we
> have
> in mind, that will never happen, since I think although we share a
> "macro"
> view perspective, in the "micro" view we all have, as normal, different
> ways of approach, so the only way I see is to join forces in
> integrating
> things, more over where you have a huge knowledge of things happening
> in
> emulation, while I have the same on things happening on Jewel.
>
> Thoughts?
>
>
>
>
> Carlos
>
>
>
>
> 2018-07-19 9:35 GMT+02:00 Alex Harui :
>
> > I think you can look at mx.controls.DateField and
> > mx.controls.NumericStepper.  The key piece is their entries in the
> > defaults.css in the MXRoyale project.  That dictates which beads are
> used.
> > If a bead has a package name starting with mx, then it is probably a
> > subclass of an org.apache.royale bead.
> >
> > I hope to finish up MenuBar shortly and then try to write up a wiki
> page
> > or something about what it takes to get these emulation components to
> > function.
> >
> > HTH,
> > -Alex
> >
> > On 7/18/18, 9:24 PM, "chembali"  wrote:
> >
> > Very helpful posts indeed. Can you tell me a couple of classic
> > emulation
> > examples that I can look at? I am hoping to take a look at them
> and
> > understand the pattern.
> >
> >
> >
> > --
> > Sent from: https://na01.safelinks.protection.outlook.com/?url=
> > http%3A%2F%2Fapache-royale-development.20373.n8.nabble.
> > com%2Fdata=02%7C01%7Caharui%40adobe.com%
> > 7C5260d6e737744f16b63008d5ed2f80af%7Cfa7b1b5a7b34438794aed2c178de
> > cee1%7C0%7C1%7C636675710635107707sdata=
> jDCl3Gak0jGgzFIzHcgiDs0rfFzsjJ
> > q3e6PgCn5Sy8g%3Dreserved=0
> >
> >
> >
>
>
> --
> Carlos Rovira
> https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%
> 7C01%7Caharui%40adobe.com%7C09c8f82f80be4a9fafa908d5ed7d80cb%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636676045646662630sdata=
> kT0BJi8rrYpP7DPz1z0Se5tTGNSofmduvvVD6IcmPtk%3Dreserved=0
>
>
>


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

Re: Migrating Enterprise Flex Application

2018-07-21 Thread Alex Harui

I forgot that I'd already written something up:  
https://github.com/apache/royale-asjs/wiki/emulation-components#getting-an-emulation-component-to-run

I'm not sure how to provide more detail, so feel free to ask more questions.

HTH,
-Alex

On 7/19/18, 12:36 AM, "Alex Harui"  wrote:

I think you can look at mx.controls.DateField and 
mx.controls.NumericStepper.  The key piece is their entries in the defaults.css 
in the MXRoyale project.  That dictates which beads are used.  If a bead has a 
package name starting with mx, then it is probably a subclass of an 
org.apache.royale bead.

I hope to finish up MenuBar shortly and then try to write up a wiki page or 
something about what it takes to get these emulation components to function.

HTH,
-Alex

On 7/18/18, 9:24 PM, "chembali"  wrote:

Very helpful posts indeed. Can you tell me a couple of classic emulation
examples that I can look at? I am hoping to take a look at them and
understand the pattern.



--
Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C5260d6e737744f16b63008d5ed2f80af%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636675710635107707sdata=jDCl3Gak0jGgzFIzHcgiDs0rfFzsjJq3e6PgCn5Sy8g%3Dreserved=0

Re: Migrating Enterprise Flex Application

2018-07-20 Thread Alex Harui

The process of building your application in Royale should be the same as in
Flex. You should be able to build the SWCs in the same order. I don't think
we have anyone trying to use Gradle right now, but I think it should work, and
I would be interested in making it work if it doesn't. So try Gradle and tell
us what errors you run into and we'll see what needs to be tweaked.

Royale's COMPC will build a SWC that contains both a library.swf (for the
compiler to understand what classes are in the SWC) and a pile of JS files.
Those SWCs are used just like Flex SWCs and at the end, when you use MXMLC to
build the main app, all of the JS files packaged in the SWCs will be added to
the output JS.

HTH,
-Alex

On 7/20/18, 2:00 AM, "chembali" wrote:

My application consists of a number of components. Each of these components
has got a UI portion which is in Flex. For e.g I have got components like
FlexUIPlatform, Directory, ProcessModel etc. Here FlexUIPlatform is the
lowest in the hierarchy and does not have any dependency on other components
for building. Directory component uses FlexUIPlatform and has a dependency
on FlexUIPlatform for component build. Our current build process ( Gradle )
builds the FlexUIPlatform first using the compc compiler and creates the
.swc library. This swc library is used in the build of the Directory
component. The build process generates the Directory.swc library. The
FlexUIPlatform.swc and Directory.swc are used in the build of the
ProcessModel component and so on.

Now my goal is to get my application ( all components ) compiled in the
Royale environment. Here is my question. Should I try to use Royale compc
and compile my components one by one? Would this create a swc library (
containing .js classes? ) if successful? Can I use/link the generated swc
during the building of the higher level component? I hope my questions make
sense.

--
Sent from:
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7Cdcddc35d449f4ca4d47a08d5ee1f4bf1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636676740543817299sdata=F2tfg3Dclz4hVndvCq8sr9ifQE7Ih2JFfDaamQA6eeM%3Dreserved=0

Re: Migrating Enterprise Flex Application

2018-07-20 Thread chembali

My application consists of a number of components. Each of these components
has got a UI portion which is in Flex. For e.g I have got components like
FlexUIPlatform, Directory, ProcessModel etc. Here FlexUIPlatform is the
lowest in the hierarchy and does not have any dependency on other components
for building. Directory component uses FlexUIPlatform and has a dependency
on FlexUIPlatform for component build. Our current build process ( Gradle )
builds the FlexUIPlatform first using the compc compiler and creates the
.swc library. This swc library is used in the build of the Directory
component. The build process generates the Directory.swc library. The
FlexUIPlatform.swc and Directory.swc are used in the build of the
ProcessModel component and so on. 

Now my goal is to get my application ( all components ) compiled in the
Royale environment. Here is my question. Should I try to use Royale compc
and compile my components one by one? Would this create a swc library (
containing .js classes? ) if successful? Can I use/link the generated swc
during the building of the higher level component? I hope my questions make
sense.



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-19 Thread Alex Harui

Hi Carlos,

Until Jewel has more of the views for existing Flex controls, it isn't worth 
trying to re-use Jewel view beads in the emulation components.  Once you have 
more of them working, then we'll simply try them and fix bugs.

-Alex

On 7/19/18, 6:42 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" 
 wrote:

Hi Alex,

about trying to use Jewel as view part, I think we should trace a plan. I
still have work in my TODO list, for example I think my next stop is Jewel
DateFiels and Jewel DropDownList/ComboBox... but I still want to try the
"exploded" component route. So using StyledUIBase in MXML adding beads I
can get a Jewel Button, a Jewel Slider and so on...

But as well although I think I'll not use emulation components on our App,
I think will be good if I must have some rules into account to make Jewel
visualization reusable.

For this I think we should create a thread, and maybe a example project
where we could work together and make the convergence of code possible.

I think one problem is that if we expect from others to code what we have
in mind, that will never happen, since I think although we share a "macro"
view perspective, in the "micro" view we all have, as normal, different
ways of approach, so the only way I see is to join forces in integrating
things, more over where you have a huge knowledge of things happening in
emulation, while I have the same on things happening on Jewel.

Thoughts?

Carlos

2018-07-19 9:35 GMT+02:00 Alex Harui :

> I think you can look at mx.controls.DateField and
> mx.controls.NumericStepper.  The key piece is their entries in the
> defaults.css in the MXRoyale project.  That dictates which beads are used.
> If a bead has a package name starting with mx, then it is probably a
> subclass of an org.apache.royale bead.
>
> I hope to finish up MenuBar shortly and then try to write up a wiki page
> or something about what it takes to get these emulation components to
> function.
>
> HTH,
> -Alex
>
> On 7/18/18, 9:24 PM, "chembali"  wrote:
>
> Very helpful posts indeed. Can you tell me a couple of classic
> emulation
> examples that I can look at? I am hoping to take a look at them and
> understand the pattern.
>
>
>
> --
> Sent from: https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fapache-royale-development.20373.n8.nabble.
> com%2Fdata=02%7C01%7Caharui%40adobe.com%
> 7C5260d6e737744f16b63008d5ed2f80af%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C1%7C636675710635107707sdata=jDCl3Gak0jGgzFIzHcgiDs0rfFzsjJ
> q3e6PgCn5Sy8g%3Dreserved=0
>
>
>

-- 
Carlos Rovira

https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C09c8f82f80be4a9fafa908d5ed7d80cb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636676045646662630sdata=kT0BJi8rrYpP7DPz1z0Se5tTGNSofmduvvVD6IcmPtk%3Dreserved=0

Re: Migrating Enterprise Flex Application

2018-07-19 Thread Carlos Rovira

Hi Alex,

about trying to use Jewel as view part, I think we should trace a plan. I
still have work in my TODO list, for example I think my next stop is Jewel
DateFiels and Jewel DropDownList/ComboBox... but I still want to try the
"exploded" component route. So using StyledUIBase in MXML adding beads I
can get a Jewel Button, a Jewel Slider and so on...

But as well although I think I'll not use emulation components on our App,
I think will be good if I must have some rules into account to make Jewel
visualization reusable.

For this I think we should create a thread, and maybe a example project
where we could work together and make the convergence of code possible.

I think one problem is that if we expect from others to code what we have
in mind, that will never happen, since I think although we share a "macro"
view perspective, in the "micro" view we all have, as normal, different
ways of approach, so the only way I see is to join forces in integrating
things, more over where you have a huge knowledge of things happening in
emulation, while I have the same on things happening on Jewel.

Thoughts?

Carlos

2018-07-19 9:35 GMT+02:00 Alex Harui :

> I think you can look at mx.controls.DateField and
> mx.controls.NumericStepper.  The key piece is their entries in the
> defaults.css in the MXRoyale project.  That dictates which beads are used.
> If a bead has a package name starting with mx, then it is probably a
> subclass of an org.apache.royale bead.
>
> I hope to finish up MenuBar shortly and then try to write up a wiki page
> or something about what it takes to get these emulation components to
> function.
>
> HTH,
> -Alex
>
> On 7/18/18, 9:24 PM, "chembali"  wrote:
>
> Very helpful posts indeed. Can you tell me a couple of classic
> emulation
> examples that I can look at? I am hoping to take a look at them and
> understand the pattern.
>
>
>
> --
> Sent from: https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fapache-royale-development.20373.n8.nabble.
> com%2Fdata=02%7C01%7Caharui%40adobe.com%
> 7C5260d6e737744f16b63008d5ed2f80af%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C1%7C636675710635107707sdata=jDCl3Gak0jGgzFIzHcgiDs0rfFzsjJ
> q3e6PgCn5Sy8g%3Dreserved=0
>
>
>

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

Re: Migrating Enterprise Flex Application

2018-07-19 Thread Piotr Zarzycki

Not sure what do you want to do. mxmlc is being used for the application
and compc to create library swc. What do you want to compile?

Thanks,
Piotr

On Thu, Jul 19, 2018, 2:17 PM chembali  wrote:

> Great. I will take a look. I am starting to get the application
> compiledusing
> royale js. Should I use compc or mxmlc? Can you provide a sample command
> for
> me to get started?
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>

Re: Migrating Enterprise Flex Application

2018-07-19 Thread chembali

Great. I will take a look. I am starting to get the application compiledusing
royale js. Should I use compc or mxmlc? Can you provide a sample command for
me to get started? 



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-19 Thread Alex Harui

I think you can look at mx.controls.DateField and mx.controls.NumericStepper.  
The key piece is their entries in the defaults.css in the MXRoyale project.  
That dictates which beads are used.  If a bead has a package name starting with 
mx, then it is probably a subclass of an org.apache.royale bead.

I hope to finish up MenuBar shortly and then try to write up a wiki page or 
something about what it takes to get these emulation components to function.

HTH,
-Alex

On 7/18/18, 9:24 PM, "chembali"  wrote:

Very helpful posts indeed. Can you tell me a couple of classic emulation
examples that I can look at? I am hoping to take a look at them and
understand the pattern.



--
Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C5260d6e737744f16b63008d5ed2f80af%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636675710635107707sdata=jDCl3Gak0jGgzFIzHcgiDs0rfFzsjJq3e6PgCn5Sy8g%3Dreserved=0

Re: Migrating Enterprise Flex Application

2018-07-18 Thread chembali

Very helpful posts indeed. Can you tell me a couple of classic emulation
examples that I can look at? I am hoping to take a look at them and
understand the pattern.



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-18 Thread Alex Harui

Top-posting to try to respond to all other posts in one email...

The goal of the emulation components is to emulate enough of Flex such that a
migrated app can go into production. Words like "functional" and "subset" can
be misleading. Spark Button has over 200 APIs. The API Reports are showing
that folks are only using 20 or 30 APIs. Those 20 or 30 APIs may not work
exactly as they do in Flex, but the goal is to make them work well enough so
that the migrated app can replace the current Flex app and the managers/users
will be happy. An example of what I mean is something I was working on
yesterday: In the Flex MenuBar, once you click on a MenuBar item, the menu
pops open, but if you then move the mouse to hover over another MenuBar item,
that item's menu will open (without clicking). This "scrubbing" functionality
is not being emulated at this time. A volunteer can always write the code to
do it, but I've chosen to skip it for now because scrubbing is of little use on
mobile devices and I'm not sure that scrubbing is essential to the success of
these apps.

I suspect we will never emulate all 200 APIs of Spark Button mainly because
nobody is using them (or 'must have' them). The API reports mainly prioritize
which APIs to emulate first. Apache projects like Royale rely on volunteer
contributions from folks with limited time, so we want to devise a development
methodology that leverages that. By allowing folks to take on smaller tasks
like "emulate this one API from Flex" that is hopefully more manageable than
asking if there are volunteers to emulate 200 APIs. If Royale becomes the
choice for lots of folks migrating from Flex, the set of APIs in Spark Button
will grow as needed, on-demand, by contributions from these volunteers.

We will help anyone learn how to make emulation components work. It isn't
hard, it is tedious at times. I will try to write up more about how to do it.

The key thing about the emulation functionality is that it reuses beads from
Basic and Express, and potentially Jewel. This is one of the major payoffs of
using composition and beads. If there is a Basic DateField or MenuBar, those
same beads can be re-used in the emulation components. Sometimes as-is,
sometimes by subclassing. The current pain point is that re-using the beads is
exposing lots of places where the Basic beads make assumptions about the
classes in their strands. So the hard part will be teaching folks how to make
the right decisions in re-using beads.

I think at this point that Basic has a bead for just about all of the key Flex
functionality, so the effort to getting the emulation components to run isn't
so much a challenge of writing new functionality as it is about re-using the
existing functionality. The current emulation components that work well enough
to pass our smoke tests don't size the same as Flex and don't have a nice
default look yet. I've deferred working on the visuals to see if there will be
reusable view beads from Jewel, and also because I think more of our volunteers
are comfortable tweaking visuals than re-purposing beads.

Regarding 3rd party libraries, IMO, replacing those is not a problem unique to
Royale. You would have to come up with a replacement for those libraries even
if you didn't use Royale. If those libraries do not have much reliance on
Flash then it may be possible to get the ActionScript source and have it "just
work". Once you choose a replacement library, we can show you how to integrate
it into your Royale app, and it should be much less changing of your code than
rewriting your entire app without Royale.

I said something like this before, but if you think about how much energy goes
into every line of code you write, once you get your code working, it is best
if you don't have to touch it again, so relying on the shared code below your
code should be the lower cost and most importantly, lower risk option.

My 2 cents,
-Alex

On 7/18/18, 4:54 AM, "yishayw" wrote:

To be more precise, they will have a subset of the functionality. The API
reports are supposed to help us find the relevant subset.

--
Sent from:
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C15793c03b3694bfc09a108d5eca537f5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636675116702561539sdata=ngMi2ZZgmK%2FmhOkOv9f%2B6qYxx3JtD2J0gJLMb%2BA27ak%3Dreserved=0

Re: Migrating Enterprise Flex Application

2018-07-18 Thread Douglas McCarroll

> Cairngorm.swc
> CairngormEnterprise.swc

> I understand the Flex programming model but don't have any
> hands on experience.

Some years ago I worked with Cairngorm and another Flex framework named
Mate, and was also looking into other frameworks such as PureMVC. At this
point I don't remember them in detail, but I can make a few comments which
may be helpful, or may be obvious.

Each of these frameworks does at least two things: It defines a system for
organizing your code and it provides infrastructure code which enables this
approach.

If you switch from one framework to another, e.g. from Cairngorm to PureMVC
you'll need to understand the way each framework works, then rearrange your
code so that it works within the new framework. Probably the hardest bit
will be learning/understanding the two frameworks. Once you do, modifying
your code shouldn't be too difficult. You'll need to make some changes but
most of your existing code will still be usable as written.

IIRC, PureMVC had a good reputation. As their website brags (
http://puremvc.org/) it's been ported to a whole bunch of languages.

Some would argue that one doesn't need to use a framework, or can create a
simple framework oneself. I liked using frameworks because they defined a
standard way of doing things, which eliminated the need for teams to agree
on how they would organize their code (or, worse yet, allow their code to
devolve into a disorganized mess). But I also felt that Cairngorm, as
least, had more levels of abstraction than I could understand the need for.

Douglas

RE: Migrating Enterprise Flex Application

2018-07-18 Thread yishayw

To be more precise, they will have a subset of the functionality. The API
reports are supposed to help us find the relevant subset.



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-18 Thread yishayw

chembali wrote
> I tried to get an emulation component working. I
> struggled.

I think once you set up your IDE to work with Royale a lot of the struggles
go away. I would encourage you to do that first, with our help, and then
judge your productivity.



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

RE: Migrating Enterprise Flex Application

2018-07-18 Thread Olaf Krueger

>The goal as I understand it is have components that are functional...

Oh wow! 
In that case, I was definitely wrong!!

Sorry and thanks, Yishay!

Olaf



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

RE: Migrating Enterprise Flex Application

2018-07-18 Thread Yishay Weiss

From: Olaf Krueger<mailto:m...@olafkrueger.net>
Sent: Wednesday, July 18, 2018 2:06 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: Migrating Enterprise Flex Application

>As I understand, the only goal of the emulation components is that you will
>be able to compile your app in order to ease the migration process.
>Those emulation components aren't a replacement for mx or spark components
>and will probably never be. Of course... I could be wrong ;-)

The goal as I understand it is have components that are functional, i.e. a full 
replacement. They probably won’t look exactly the same as their flash 
counterparts, but they should serve the same purpose.

Re: Migrating Enterprise Flex Application

2018-07-18 Thread Olaf Krueger

Hi,

>Is it realistic to count on you guys to deliver the emulation components 

Just to make sure that you got it right:
As I understand, the only goal of the emulation components is that you will
be able to compile your app in order to ease the migration process.
Those emulation components aren't a replacement for mx or spark components
and will probably never be. Of course... I could be wrong ;-)


>Cairngorm.swc 

I am pretty sure that Cairngorm itself depends on Flex/Flash.
Maybe it's a good idea to go through the Cairngorm source code in order to
get an idea of it.
As Harbs already mentioned PureMVC is another MVC framework which was
written in pure AS3 without any dependencies. Because of this, it compiles
just out of the box.
If it turns out that Cairngorm also has no dependencies, give it a try and
compile it.
Otherwise, you can try to replace those dependencies.

Regarding the other libs:
Maybe you want to extract all required classes/components from each
particular lib.
Then you can think about their particular replacements.

Apart from that, maybe it is also worth to think about a renewal of the
entire UI or parts of it instead of trying to find perfectly matching
counterparts for the current UI which could feel a bit outdated.

Hmmm... not sure if this post is really helpful ;-)
Olaf








--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-18 Thread Harbs

Some comments:

> AlivePDF.swc

You’re probably going to need some HTML-compatible library for this. Take a 
look at PDFKit https://github.com/devongovett/pdfkit 

> Cairngorm.swc
> CairngormEnterprise.swc

I’ve never used Cairngorm. I do use PureMVC and simply copying the source files 
into my project worked perfectly.

> diagrammer.swc

This seems like data visualization. You’re going to want to analyze whether it 
makes sense to migrate that code, or use some JS library.

> drumbeatinsight.swc

I don’t know what this is, but it looks like Jude’s project.

> granite.swc

Would BlazeDS be a good replacement for this?

> kap-layouts-1.6.2.swc

Don’t know what this is.

> MaskedTextInput.swc

Is this different than the Spark one? You can probably use a Royale TextInput 
with a Password bead.

> multicolumnform.swc

I’m guessing you can just lay everything out without this.

> svg-1.6.2.swc
I don’t know what this is, but Royale has pretty good SVG support.

> flex-iframe-1.4.6.swc

Royale has a “WebBrowser” component which can load iframes.

> ObjectHandles-1.0.0013.swc
Don’t know what this is.

> On Jul 18, 2018, at 9:36 AM, chembali  wrote:
> 
> I believe I have convinced the management to go with Apache Royale as part
> the Deflexing effort of our Flex applications. The first project is going to
> be very important and they are going to monitor it closely. 
> 
> I want to be realistic and figure out the best approach and I need your help
> on this. I am an enterprise java developer with working knowledge of the UI
> technologies. I understand the Flex programming model but don't have any
> hands on experience. I tried to get an emulation component working. I
> struggled. I was able to get the emulation working by cut/paste/edit with
> the Royale class implementation but this may not be the best approach.
> 
> I now realise that my developer and I don't have the necessary skillset to
> get the emulation components implemented in a timely manner. This is a huge
> risk. How can I mitigate this risk? Is it realistic to count on you guys to
> deliver the emulation components ( not sure )? Can I go with the Apache
> Royale native APIs ( Jewel, Basic, Express etc ) for the mx/spark components
> that are not emulated?
> 
> Also the 3rd party APIs used in my application are
> 
> AlivePDF.swc
> Cairngorm.swc
> CairngormEnterprise.swc
> diagrammer.swc
> drumbeatinsight.swc
> granite.swc
> kap-layouts-1.6.2.swc
> MaskedTextInput.swc
> multicolumnform.swc
> svg-1.6.2.swc
> flex-iframe-1.4.6.swc
> ObjectHandles-1.0.0013.swc
> 
> Any experience/recommendation in handling the 3rd party libraries? 
> I am working on the Prototype for the Management currently. But I was
> thinking of trying to get the Application ( all components ) compiled using
> the royale-asjs by adding stub for the missing mx/spark components. Any
> other recommendations? Again thanks a bunch for your help on this.
> 
> 
> 
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-18 Thread Piotr Zarzycki

I believe the Jewel it may be your right choice once you will be able to
build your application.

The thing is that having emulation components for all your app parts you
may need to at the end start to replace it one by one by Jewel or third
party things.

I would recognize what you are missing at first place. Once you finish
basic POC for management, try to work on building whole app.

I would start comment out all places which are using external libraries
from your list. Than start building - if it's failing because some
component is missing you need simply wrote that component. - See on the
branch with emulation - there are plenty of components as an example
written by Alina.

Once you reach the point of building for app with commented out libraries,
that would be the place where you can think about third party replacement
for them. There is also a chance that you poses some more skills in the
process and write some missing part on your own.

Migration is a long way... That's the reality.

One more thing - we are all here wanted to help, have in mind that is
volunteer project, so it sometimes takes time to get the response. Only
fraction of us working here for a full time with that stuff.

Harbs was the one of the person who was patience with his product in case
of migration and I believe it was worth.

All the best!
Piotr

On Wed, Jul 18, 2018, 8:36 AM chembali  wrote:

> I believe I have convinced the management to go with Apache Royale as part
> the Deflexing effort of our Flex applications. The first project is going
> to
> be very important and they are going to monitor it closely.
>
> I want to be realistic and figure out the best approach and I need your
> help
> on this. I am an enterprise java developer with working knowledge of the UI
> technologies. I understand the Flex programming model but don't have any
> hands on experience. I tried to get an emulation component working. I
> struggled. I was able to get the emulation working by cut/paste/edit with
> the Royale class implementation but this may not be the best approach.
>
> I now realise that my developer and I don't have the necessary skillset to
> get the emulation components implemented in a timely manner. This is a huge
> risk. How can I mitigate this risk? Is it realistic to count on you guys to
> deliver the emulation components ( not sure )? Can I go with the Apache
> Royale native APIs ( Jewel, Basic, Express etc ) for the mx/spark
> components
> that are not emulated?
>
> Also the 3rd party APIs used in my application are
>
> AlivePDF.swc
> Cairngorm.swc
> CairngormEnterprise.swc
> diagrammer.swc
> drumbeatinsight.swc
> granite.swc
> kap-layouts-1.6.2.swc
> MaskedTextInput.swc
> multicolumnform.swc
> svg-1.6.2.swc
> flex-iframe-1.4.6.swc
> ObjectHandles-1.0.0013.swc
>
> Any experience/recommendation in handling the 3rd party libraries?
> I am working on the Prototype for the Management currently. But I was
> thinking of trying to get the Application ( all components ) compiled using
> the royale-asjs by adding stub for the missing mx/spark components. Any
> other recommendations? Again thanks a bunch for your help on this.
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>

Re: Migrating Enterprise Flex Application

2018-07-18 Thread chembali

I believe I have convinced the management to go with Apache Royale as part
the Deflexing effort of our Flex applications. The first project is going to
be very important and they are going to monitor it closely. 

I want to be realistic and figure out the best approach and I need your help
on this. I am an enterprise java developer with working knowledge of the UI
technologies. I understand the Flex programming model but don't have any
hands on experience. I tried to get an emulation component working. I
struggled. I was able to get the emulation working by cut/paste/edit with
the Royale class implementation but this may not be the best approach.

I now realise that my developer and I don't have the necessary skillset to
get the emulation components implemented in a timely manner. This is a huge
risk. How can I mitigate this risk? Is it realistic to count on you guys to
deliver the emulation components ( not sure )? Can I go with the Apache
Royale native APIs ( Jewel, Basic, Express etc ) for the mx/spark components
that are not emulated?

Also the 3rd party APIs used in my application are

AlivePDF.swc
Cairngorm.swc
CairngormEnterprise.swc
diagrammer.swc
drumbeatinsight.swc
granite.swc
kap-layouts-1.6.2.swc
MaskedTextInput.swc
multicolumnform.swc
svg-1.6.2.swc
flex-iframe-1.4.6.swc
ObjectHandles-1.0.0013.swc

Any experience/recommendation in handling the 3rd party libraries? 
I am working on the Prototype for the Management currently. But I was
thinking of trying to get the Application ( all components ) compiled using
the royale-asjs by adding stub for the missing mx/spark components. Any
other recommendations? Again thanks a bunch for your help on this.



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-18 Thread chembali

Spot on. The directory was not getting configured because I had the GOOG_HOME
environment variable already set ( pointing to a different folder ). I
deleted it and everything started working fine.



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-17 Thread Alex Harui

In theory, the build should have created a folder path:

  js/lib/google/closure-library

Does your copy of the older source have that?  If not, try running the build 
against the latest source to see what happens when it tries bring down the 
Google Closure Library.  You shouldn't have to specify -closure-lib if that 
folder path exists.

HTH,
-Alex


On 7/17/18, 4:32 AM, "chembali"  wrote:

I had the source that I had downloaded a week or so ago. I was able to
compile that source and use it successfully. I implemented the stub for an
emulation component and was able to get it working after the build. So the
issue appears to be in the latest branch ( for me at least )



--
Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C38b53e61c1284e63255508d5ebd9034e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636674239647362078sdata=L6S%2FdCG8kdfdFDnK7fI9SNCE6X8j%2B%2FxJlkqsAPbH82A%3Dreserved=0

Re: Migrating Enterprise Flex Application

I had the source that I had downloaded a week or so ago. I was able to
compile that source and use it successfully. I implemented the stub for an
emulation component and was able to get it working after the build. So the
issue appears to be in the latest branch ( for me at least )



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

I am using Java 1.8.0_161 for compiling and running.



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

It looks like the a couple of JS files are generated before the process
fails.  Compile.PNG
  





--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

I switched to the MxRoyale branch and did the build and it the build was
successful. Then I ran the same command to transpile.

C:\devenv\GitHub\royale-asjs\royale-asjs\js\bin\mxmlc -targets=JSRoyale
C:\devenv\ii\trunk\components\ControlsManagement\src-flexui\com\infogix\insight\component\controlsmanagement\exp\view\controls\InsightRoyaleTestUI.mxml
-js-output=C:\devenv\ii\trunk\components\InfogixInsight\build\flex\InfogixInsightJS

It failed with the following message. 

C:\devenv\ii\trunk\components\InfogixInsight>C:\devenv\GitHub\royale-asjs\royale
-asjs\js\bin\mxmlc -targets=JSRoyale
C:\devenv\ii\trunk\components\ControlsManag
ement\src-flexui\com\infogix\insight\component\controlsmanagement\exp\view\contr
ols\InsightRoyaleTestUI.mxml
-js-output=C:\devenv\ii\trunk\components\InfogixIns
ight\build\flex\InfogixInsightJS3
Using Royale Compiler codebase:
C:\devenv\GitHub\royale-asjs\royale-asjs\js\bin\
..\..
Using Royale SDK: C:\devenv\GitHub\royale-asjs\royale-asjs
MXMLJSC
-sdk-js-lib=C:\devenv\GitHub\royale-asjs\royale-asjs\frameworks\js\Royale\genera
ted-sources
-targets=JSRoyale
C:\devenv\ii\trunk\components\ControlsManagement\src-flexui\com\infogix\insight\
component\controlsmanagement\exp\view\controls\InsightRoyaleTestUI.mxml
-js-output=C:\devenv\ii\trunk\components\InfogixInsight\build\flex\InfogixInsigh
tJS3
Compiling file:
C:\devenv\ii\trunk\components\InfogixInsight\build\flex\InfogixI
nsightJS3\bin\js-debug\InsightRoyaleTestUI.js
InsightRoyaleTestUI as: []
InsightRoyaleTestUI mxml: [mx.containers.VBox, mx.controls.Label,
mx.controls.Bu
tton, mx.controls.NumericStepper, mx.controls.Spacer, mx.containers.HBox,
mx.con
trols.LinkButton, mx.containers.Canvas, mx.controls.TextArea,
InsightRoyaleTestU
I, mx.core.Application]
find project folder for
c:\devenv\ii\trunk\components\controlsmanagement\src-fle
xui\com\infogix\insight\component\controlsmanagement\exp\view\controls\insightro
yaletestui.mxml
checking source path
C:\devenv\ii\trunk\components\ControlsManagement\src-flexui
\com\infogix\insight\component\controlsmanagement\exp\view\controls
Internal error: java.lang.RuntimeException: Parameter 'closure-lib' not
specifie
d and closure resources not available in classpath.
org.apache.royale.compiler.i
nternal.codegen.mxml.royale.MXMLRoyalePublisher.publish(MXMLRoyalePublisher.java
:318)org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java
:384)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.
java:240)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoya
le.java:197)org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:
363)org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:299)org.a
pache.royale.compiler.clients.MXMLJSC.staticMainNoExit(MXMLJSC.java:258)org.apac
he.royale.compiler.clients.MXMLJSC.main(MXMLJSC.java:240)

Then I updated the transpile comand as shown below and ran again.

C:\devenv\GitHub\royale-asjs\royale-asjs\js\bin\mxmlc -closure-lib
C:\devenv\GitHub\royale-asjs\royale-asjs\js\lib\google\closure-compiler
-targets=JSRoyale
C:\devenv\ii\trunk\components\ControlsManagement\src-flexui\com\infogix\insight\component\controlsmanagement\exp\view\controls\InsightRoyaleTestUI.mxml
-js-output=C:\devenv\ii\trunk\components\InfogixInsight\build\flex\InfogixInsightJS

It failed with the below message.

Using Royale Compiler codebase:
C:\devenv\GitHub\royale-asjs\royale-asjs\js\bin\
..\..
Using Royale SDK: C:\devenv\GitHub\royale-asjs\royale-asjs
MXMLJSC
-sdk-js-lib=C:\devenv\GitHub\royale-asjs\royale-asjs\frameworks\js\Royale\genera
ted-sources
-closure-lib
C:\devenv\GitHub\royale-asjs\royale-asjs\js\lib\google\closure-compiler
-targets=JSRoyale
C:\devenv\ii\trunk\components\ControlsManagement\src-flexui\com\infogix\insight\
component\controlsmanagement\exp\view\controls\InsightRoyaleTestUI.mxml
-js-output=C:\devenv\ii\trunk\components\InfogixInsight\build\flex\InfogixInsigh
tJS
Compiling file:
C:\devenv\ii\trunk\components\InfogixInsight\build\flex\InfogixI
nsightJS\bin\js-debug\InsightRoyaleTestUI.js
InsightRoyaleTestUI as: []
InsightRoyaleTestUI mxml: [mx.containers.VBox, mx.controls.Label,
mx.controls.Bu
tton, mx.controls.NumericStepper, mx.controls.Spacer, mx.containers.HBox,
mx.con
trols.LinkButton, mx.containers.Canvas, mx.controls.TextArea,
InsightRoyaleTestU
I, mx.core.Application]
find project folder for
c:\devenv\ii\trunk\components\controlsmanagement\src-fle
xui\com\infogix\insight\component\controlsmanagement\exp\view\controls\insightro
yaletestui.mxml
checking source path
C:\devenv\ii\trunk\components\ControlsManagement\src-flexui
\com\infogix\insight\component\controlsmanagement\exp\view\controls
Internal error: java.lang.IllegalArgumentException: Parameter 'directory' is
not
 a directory
org.apache.commons.io.FileUtils.validateListFilesParameters(FileUti
ls.java:545)org.apache.commons.io.FileUtils.listFiles(FileUtils.java:521)org.apa

Re: Migrating Enterprise Flex Application

No I am using the develop branch. I will switch to feature/MxRoyale and see.
Thank you.



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-17 Thread Alex Harui

Are you using the feature/MXRoyale branch in royale-asjs?

On 7/16/18, 11:04 PM, "chembali"  wrote:

Met with the Management. They insisted on POC including the development of 
at
least one emulation component by me in order to proceed with the project. I
am starting on the POC work now. I got the Apache-Royale source tree cloned
and did the build without any issues. I just tried to transpile a simple
mxml file to test my build. Here is the mxml I tried.


https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Caharui%40adobe.com%7C38ae9d025c7b4119434f08d5ebab318d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636674042857406660sdata=fBmYwGgz0TbrtObCqCUf2QcJz34XlcY3UCB6mJwqLks%3Dreserved=0;
xmlns:mx="library://ns.apache.org/royale/mx">

























The command that I used to compile is

C:\devenv\GitHub\royale-asjs\royale-asjs\js\bin\mxmlc -targets=JSRoyale

C:\devenv\ii\trunk\components\ControlsManagement\src-flexui\com\infogix\insight\component\controlsmanagement\exp\view\controls\InsightRoyaleTestUI.mxml

-js-output=C:\devenv\ii\trunk\components\InfogixInsight\build\flex\InfogixInsightJS

It failed with the following error.


C:\devenv\ii\trunk\components\InfogixInsight>C:\devenv\GitHub\royale-asjs\royale
-asjs\js\bin\mxmlc -targets=JSRoyale
C:\devenv\ii\trunk\components\ControlsManag

ement\src-flexui\com\infogix\insight\component\controlsmanagement\exp\view\contr
ols\InsightRoyaleTestUI.mxml
-js-output=C:\devenv\ii\trunk\components\InfogixIns
ight\build\flex\InfogixInsightJS
Using Royale Compiler codebase:
C:\devenv\GitHub\royale-asjs\royale-asjs\js\bin\
..\..
Using Royale SDK: C:\devenv\GitHub\royale-asjs\royale-asjs
MXMLJSC

-sdk-js-lib=C:\devenv\GitHub\royale-asjs\royale-asjs\frameworks\js\Royale\genera
ted-sources
-targets=JSRoyale

C:\devenv\ii\trunk\components\ControlsManagement\src-flexui\com\infogix\insight\
component\controlsmanagement\exp\view\controls\InsightRoyaleTestUI.mxml

-js-output=C:\devenv\ii\trunk\components\InfogixInsight\build\flex\InfogixInsigh
tJS

C:\devenv\ii\trunk\components\InfogixInsight\MXRoyaleJS.swc:defaults.css(65):
co
l: 14 Error: org.apache.royale.core.beads.views.ContainerView is not
defined.



C:\devenv\ii\trunk\components\InfogixInsight\MXRoyaleJS.swc:defaults.css(65):
co
l: 14 Error: org.apache.royale.core.beads.views.ContainerView is not
defined.



C:\devenv\ii\trunk\components\InfogixInsight\MXRoyaleJS.swc:defaults.css(65):
co
l: 14 Error: org.apache.royale.core.beads.views.ContainerView is not
defined.


3.80624289 seconds

Any ideas? Your quick help is much appreciated. 





--
Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C38ae9d025c7b4119434f08d5ebab318d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636674042857406660sdata=y8x2weu3wqq2BWFoszfvIhr47K%2FO4z2pijiPI%2BN1WRI%3Dreserved=0

Re: Migrating Enterprise Flex Application

Met with the Management. They insisted on POC including the development of at
least one emulation component by me in order to proceed with the project. I
am starting on the POC work now. I got the Apache-Royale source tree cloned
and did the build without any issues. I just tried to transpile a simple
mxml file to test my build. Here is the mxml I tried.


http://ns.adobe.com/mxml/2009;
xmlns:mx="library://ns.apache.org/royale/mx">

























The command that I used to compile is

C:\devenv\GitHub\royale-asjs\royale-asjs\js\bin\mxmlc -targets=JSRoyale
C:\devenv\ii\trunk\components\ControlsManagement\src-flexui\com\infogix\insight\component\controlsmanagement\exp\view\controls\InsightRoyaleTestUI.mxml
-js-output=C:\devenv\ii\trunk\components\InfogixInsight\build\flex\InfogixInsightJS

It failed with the following error.

C:\devenv\ii\trunk\components\InfogixInsight>C:\devenv\GitHub\royale-asjs\royale
-asjs\js\bin\mxmlc -targets=JSRoyale
C:\devenv\ii\trunk\components\ControlsManag
ement\src-flexui\com\infogix\insight\component\controlsmanagement\exp\view\contr
ols\InsightRoyaleTestUI.mxml
-js-output=C:\devenv\ii\trunk\components\InfogixIns
ight\build\flex\InfogixInsightJS
Using Royale Compiler codebase:
C:\devenv\GitHub\royale-asjs\royale-asjs\js\bin\
..\..
Using Royale SDK: C:\devenv\GitHub\royale-asjs\royale-asjs
MXMLJSC
-sdk-js-lib=C:\devenv\GitHub\royale-asjs\royale-asjs\frameworks\js\Royale\genera
ted-sources
-targets=JSRoyale
C:\devenv\ii\trunk\components\ControlsManagement\src-flexui\com\infogix\insight\
component\controlsmanagement\exp\view\controls\InsightRoyaleTestUI.mxml
-js-output=C:\devenv\ii\trunk\components\InfogixInsight\build\flex\InfogixInsigh
tJS
C:\devenv\ii\trunk\components\InfogixInsight\MXRoyaleJS.swc:defaults.css(65):
co
l: 14 Error: org.apache.royale.core.beads.views.ContainerView is not
defined.


C:\devenv\ii\trunk\components\InfogixInsight\MXRoyaleJS.swc:defaults.css(65):
co
l: 14 Error: org.apache.royale.core.beads.views.ContainerView is not
defined.


C:\devenv\ii\trunk\components\InfogixInsight\MXRoyaleJS.swc:defaults.css(65):
co
l: 14 Error: org.apache.royale.core.beads.views.ContainerView is not
defined.


3.80624289 seconds

Any ideas? Your quick help is much appreciated. 





--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

Sounds reasonable. IMO, the key advantage of Royale is that it requires less
touching of your code, especially touching by transcoding to a less structured
language. That is just an invitation to new bugs. Sure there will be plenty
of new bugs in the emulation components, but there are many more people
exercising those code paths so some of those bugs will be found and fixed by
others. If you touch your code, then all bugs have to be found and fixed by
you.

My 2 cents,
-Alex

On 7/13/18, 1:54 AM, "chembali" wrote:

I have a meeting with the management tomorrow. I will try to convince them
without spending time on the POC if possible. Here is the high level plan
that I am going to present to them.

The plan is to perform the migration component by component using emulation
wherever needed. I will also consider using the new Royale APIs if the
emulation does not work for some reason. The third party libraries will be
migrated to the JS libraries.

I am putting together detailed plan for the individual component migration.
My developers can also get involved and take ownership of components and
start the migration process. Please let me know if you see any issues with
this approach.

--
Sent from:
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C93dee51c05234043832508d5e89e394d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636670688621976774sdata=nVImt9kPSoPI4IXiYVSQ9ga5sHqQ%2Bpiuc2EHhY8H1Fc%3Dreserved=0

Re: Migrating Enterprise Flex Application

2018-07-13 Thread chembali

I have a meeting with the management tomorrow. I will try to convince them
without spending time on the POC if possible. Here is the high level plan
that I am going to present to them.

The plan is to perform the migration component by component using emulation
wherever needed. I will also consider using the new Royale APIs if the
emulation does not work for some reason. The third party libraries will be
migrated to the JS libraries.

I am putting together detailed plan for the individual component migration.
My developers can also get involved and take ownership of components and
start the migration process. Please let me know if you see any issues with
this approach.



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

I forgot to mention that you should be using Flex 4.1 MXMLC to produce a SWF
that displays this one POC screen first. Then those same reduced set of
compiler
options should be passed to the Royale Compiler to see it build a SWF and/or JS
output.

HTH,
-Alex

On 7/12/18, 11:20 PM, "Alex Harui" wrote:

It is surprising that compc appeared to succeed but didn't actually
indicate that it compiled anything. But before we dig into that, I want to add
my thoughts to what Carlos suggested: We would like you to simply further if
possible for this two to three week proof-of-concept (POC).

Ideally, you would have a test case so simple that wouldn't use compc at
all. It would use mxmlc, and reference some of your other library code via
source-path. That should compile successfully and produce something you can
run and show that one screen. That should work unless your library code has
heavy reliance on Flash APIs or other 3rd party APIs.

The command-line options you are using are not correct and too heavy for
this POC. It looks like you are using the same options you needed for the
api-report but the goal there was to build a SWF using the Flex SDK but have
the Royale compiler generate the api-report. But now that you are trying to
transpile something simple, you should try to start with a much different set
of command-line options. Instead of using a flex-config.xml, you would start
by using the default, so remove that option. And then to remove dependencies
on third-party libraries we haven't emulated yet, I would remove all of the
other -library-path and -external-library-path options and see which ones you
absolutely need for this simple POC. And if you need some of those third-party
libraries, see if you can comment out the parts that rely on third-party stuff
for now. And use mxmlc if you can avoid the need for a SWC.

HTH,
-Alex

On 7/12/18, 4:19 AM, "chembali" wrote:

I am trying to compile my mxml and action script sources. I am using the
latest emulation build. So I expect most of my source code to compile
because of the emulation build that I am compiling against. I expect to
see
compile errors if any of the MX/SPARK components that I am using is not
emulated ( and no stubs ). I may be wrong. Please correct.

--
Sent from:
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C9529c2a8902f471be4cc08d5e7e9459a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636669911444095737sdata=O1oJj232nKGClofG29oD75%2FMksdJ79MM1Uc7iQEBxZU%3Dreserved=0

Re: Migrating Enterprise Flex Application

It is surprising that compc appeared to succeed but didn't actually indicate
that it compiled anything. But before we dig into that, I want to add my
thoughts to what Carlos suggested: We would like you to simply further if
possible for this two to three week proof-of-concept (POC).

Ideally, you would have a test case so simple that wouldn't use compc at all.
It would use mxmlc, and reference some of your other library code via
source-path. That should compile successfully and produce something you can
run and show that one screen. That should work unless your library code has
heavy reliance on Flash APIs or other 3rd party APIs.

The command-line options you are using are not correct and too heavy for this
POC. It looks like you are using the same options you needed for the
api-report but the goal there was to build a SWF using the Flex SDK but have
the Royale compiler generate the api-report. But now that you are trying to
transpile something simple, you should try to start with a much different set
of command-line options. Instead of using a flex-config.xml, you would start
by using the default, so remove that option. And then to remove dependencies
on third-party libraries we haven't emulated yet, I would remove all of the
other -library-path and -external-library-path options and see which ones you
absolutely need for this simple POC. And if you need some of those third-party
libraries, see if you can comment out the parts that rely on third-party stuff
for now. And use mxmlc if you can avoid the need for a SWC.

HTH,
-Alex

On 7/12/18, 4:19 AM, "chembali" wrote:

I am trying to compile my mxml and action script sources. I am using the
latest emulation build. So I expect most of my source code to compile
because of the emulation build that I am compiling against. I expect to see
compile errors if any of the MX/SPARK components that I am using is not
emulated ( and no stubs ). I may be wrong. Please correct.

--
Sent from:
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C9529c2a8902f471be4cc08d5e7e9459a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636669911444095737sdata=O1oJj232nKGClofG29oD75%2FMksdJ79MM1Uc7iQEBxZU%3Dreserved=0

Re: Migrating Enterprise Flex Application

That's fine with me, but if you really have a two or three week go/no-go 
decision about using Royale, I don’t' want to distract from trying to get your 
proof-of-concept up and running.  The list in this email contains third-party 
libraries that used the com.adobe.util packages.  We won't emulate those if we 
can find the source and transpile them.

The rest of the list needs further pruning since lots of those APIs have been 
emulated in base classes.  We can update that list if you commit to going with 
Royale.  I'll answer your other issues in another post.

Thanks,
-Alex

On 7/12/18, 9:30 PM, "chembali"  wrote:

Can I go ahead and create an issue with the list of APIs to be emulated? I 
am
thinking the flash,mx and Spark components from the below list needs to be
emulated. I am not sure about the com.adobe classes in the list. I did a
quick search for the JS implementation for the 3rd party libraries that are
used. Most of the JS counterparts are out there. I am thinking of replacing
the 3rd party libraries with JS libraries. Let me know your thoughts. Here
is the list that I came up with.

 com.adobe.cairngorm.model.IModelLocator 
 com.adobe.utils.ArrayUtil 
 com.adobe.utils.ArrayUtil:arrayContainsValue 
 com.adobe.utils.ArrayUtil:removeValueFromArray 
 com.adobe.utils.StringUtil 
 com.adobe.utils.StringUtil:replace 
 com.adobe.utils.StringUtil:stringsAreEqual 
 flash.display.BlendMode 
 flash.display.BlendMode:NORMAL 
 flash.display.DisplayObjectContainer:addChildAt 
 flash.display.InteractiveObject:contextMenu 
 flash.display.Sprite:useHandCursor 
 flash.events.ErrorEvent 
 flash.events.Event:CANCEL 
 flash.events.Event:stopImmediatePropagation 
 flash.events.Event:UNLOAD 
 flash.events.IEventDispatcher 
 flash.events.IOErrorEvent:text 
 flash.events.KeyboardEvent:stopImmediatePropagation 
 flash.events.KeyboardEvent:stopPropagation 
 flash.events.MouseEvent:ctrlKey 
 flash.events.MouseEvent:delta 
 flash.events.MouseEvent:shiftKey 
 flash.external.ExternalInterface:objectID 
 flash.filters.GlowFilter:alpha 
 flash.filters.GlowFilter:color 
 flash.filters.GlowFilter:inner 
 flash.filters.GlowFilter:strength 
 flash.net.FileReference:download 
 flash.net.FileReference:upload 
 flash.net.FileReferenceList 
 flash.net.FileReferenceList:addEventListener 
 flash.net.FileReferenceList:browse 
 flash.net.FileReferenceList:fileList 
 flash.net.URLLoader:close 
 flash.net.URLLoader:dataFormat 
 flash.net.URLLoader:removeEventListener 
 flash.net.URLLoaderDataFormat 
 flash.net.URLLoaderDataFormat:BINARY 
 flash.net.URLRequest:data 
 flash.net.URLRequest:requestHeaders 
 flash.net.URLRequestHeader 
 flash.net.URLRequestMethod 
 flash.net.URLRequestMethod:GET 
 flash.net.URLRequestMethod:POST 
 flash.system.Capabilities 
 flash.system.Capabilities:version 
 flash.system.Security 
 flash.system.Security:allowDomain 
 flash.system.Security:loadPolicyFile 
 flash.system.System 
 flash.system.System:gc 
 flash.system.System:setClipboard 
 flash.text.TextField:background 
 flash.text.TextField:backgroundColor 
 flash.ui.Keyboard:ENTER 
 flash.utils.getQualifiedSuperclassName 
 flash.utils.Timer:delay 
 flash.utils.Timer:hasEventListener 
 flash.utils.Timer:removeEventListener 
 flash.xml.XMLDocument 
 flash.xml.XMLDocument:appendChild 
 flash.xml.XMLDocument:toString 
 flash.xml.XMLNode 
 flash.xml.XMLNode:appendChild 
 flash.xml.XMLNode:attributes 
 flash.xml.XMLNodeType 
 flash.xml.XMLNodeType:ELEMENT_NODE 
 flash.xml.XMLNodeType:TEXT_NODE 
 flashx.textLayout.conversion.TextConverter 
 flashx.textLayout.conversion.TextConverter:importToFlow 
 flashx.textLayout.conversion.TextConverter:TEXT_FIELD_HTML_FORMAT 
 flashx.textLayout.elements.TextFlow 
 flashx.textLayout.elements.TextFlow:getText 
 flashx.textLayout.elements.TextFlow:linkNormalFormat 
 flashx.textLayout.formats.LineBreak 
 flashx.textLayout.formats.LineBreak:TO_FIT 
 flashx.textLayout.formats.TextLayoutFormat 
 flashx.textLayout.formats.TextLayoutFormat:color 
 mx.binding.utils.BindingUtils 
 mx.binding.utils.BindingUtils:bindSetter 
 mx.binding.utils.ChangeWatcher 
 mx.charts.AxisRenderer 
 mx.charts.AxisRenderer:axis 
 mx.charts.AxisRenderer:axisStroke 
 mx.charts.AxisRenderer:canDropLabels 
 mx.charts.AxisRenderer:creationComplete 
 mx.charts.AxisRenderer:gutters 
 mx.charts.AxisRenderer:minorTickPlacement 
 mx.charts.AxisRenderer:numChildren 
 mx.charts.AxisRenderer:placement 
 mx.charts.AxisRenderer:setStyle 
 mx.charts.AxisRenderer:tickPlacement 
 mx.charts.AxisRenderer:titleRenderer 
 mx.charts.AxisRenderer:verticalAxisTitleAlignment

Re: Migrating Enterprise Flex Application

Can I go ahead and create an issue with the list of APIs to be emulated? I am
thinking the flash,mx and Spark components from the below list needs to be
emulated. I am not sure about the com.adobe classes in the list. I did a
quick search for the JS implementation for the 3rd party libraries that are
used. Most of the JS counterparts are out there. I am thinking of replacing
the 3rd party libraries with JS libraries. Let me know your thoughts. Here
is the list that I came up with.

 com.adobe.cairngorm.model.IModelLocator 
 com.adobe.utils.ArrayUtil 
 com.adobe.utils.ArrayUtil:arrayContainsValue 
 com.adobe.utils.ArrayUtil:removeValueFromArray 
 com.adobe.utils.StringUtil 
 com.adobe.utils.StringUtil:replace 
 com.adobe.utils.StringUtil:stringsAreEqual 
 flash.display.BlendMode 
 flash.display.BlendMode:NORMAL 
 flash.display.DisplayObjectContainer:addChildAt 
 flash.display.InteractiveObject:contextMenu 
 flash.display.Sprite:useHandCursor 
 flash.events.ErrorEvent 
 flash.events.Event:CANCEL 
 flash.events.Event:stopImmediatePropagation 
 flash.events.Event:UNLOAD 
 flash.events.IEventDispatcher 
 flash.events.IOErrorEvent:text 
 flash.events.KeyboardEvent:stopImmediatePropagation 
 flash.events.KeyboardEvent:stopPropagation 
 flash.events.MouseEvent:ctrlKey 
 flash.events.MouseEvent:delta 
 flash.events.MouseEvent:shiftKey 
 flash.external.ExternalInterface:objectID 
 flash.filters.GlowFilter:alpha 
 flash.filters.GlowFilter:color 
 flash.filters.GlowFilter:inner 
 flash.filters.GlowFilter:strength 
 flash.net.FileReference:download 
 flash.net.FileReference:upload 
 flash.net.FileReferenceList 
 flash.net.FileReferenceList:addEventListener 
 flash.net.FileReferenceList:browse 
 flash.net.FileReferenceList:fileList 
 flash.net.URLLoader:close 
 flash.net.URLLoader:dataFormat 
 flash.net.URLLoader:removeEventListener 
 flash.net.URLLoaderDataFormat 
 flash.net.URLLoaderDataFormat:BINARY 
 flash.net.URLRequest:data 
 flash.net.URLRequest:requestHeaders 
 flash.net.URLRequestHeader 
 flash.net.URLRequestMethod 
 flash.net.URLRequestMethod:GET 
 flash.net.URLRequestMethod:POST 
 flash.system.Capabilities 
 flash.system.Capabilities:version 
 flash.system.Security 
 flash.system.Security:allowDomain 
 flash.system.Security:loadPolicyFile 
 flash.system.System 
 flash.system.System:gc 
 flash.system.System:setClipboard 
 flash.text.TextField:background 
 flash.text.TextField:backgroundColor 
 flash.ui.Keyboard:ENTER 
 flash.utils.getQualifiedSuperclassName 
 flash.utils.Timer:delay 
 flash.utils.Timer:hasEventListener 
 flash.utils.Timer:removeEventListener 
 flash.xml.XMLDocument 
 flash.xml.XMLDocument:appendChild 
 flash.xml.XMLDocument:toString 
 flash.xml.XMLNode 
 flash.xml.XMLNode:appendChild 
 flash.xml.XMLNode:attributes 
 flash.xml.XMLNodeType 
 flash.xml.XMLNodeType:ELEMENT_NODE 
 flash.xml.XMLNodeType:TEXT_NODE 
 flashx.textLayout.conversion.TextConverter 
 flashx.textLayout.conversion.TextConverter:importToFlow 
 flashx.textLayout.conversion.TextConverter:TEXT_FIELD_HTML_FORMAT 
 flashx.textLayout.elements.TextFlow 
 flashx.textLayout.elements.TextFlow:getText 
 flashx.textLayout.elements.TextFlow:linkNormalFormat 
 flashx.textLayout.formats.LineBreak 
 flashx.textLayout.formats.LineBreak:TO_FIT 
 flashx.textLayout.formats.TextLayoutFormat 
 flashx.textLayout.formats.TextLayoutFormat:color 
 mx.binding.utils.BindingUtils 
 mx.binding.utils.BindingUtils:bindSetter 
 mx.binding.utils.ChangeWatcher 
 mx.charts.AxisRenderer 
 mx.charts.AxisRenderer:axis 
 mx.charts.AxisRenderer:axisStroke 
 mx.charts.AxisRenderer:canDropLabels 
 mx.charts.AxisRenderer:creationComplete 
 mx.charts.AxisRenderer:gutters 
 mx.charts.AxisRenderer:minorTickPlacement 
 mx.charts.AxisRenderer:numChildren 
 mx.charts.AxisRenderer:placement 
 mx.charts.AxisRenderer:setStyle 
 mx.charts.AxisRenderer:tickPlacement 
 mx.charts.AxisRenderer:titleRenderer 
 mx.charts.AxisRenderer:verticalAxisTitleAlignment 
 mx.charts.AxisRenderer:visible 
 mx.charts.CategoryAxis:padding 
 mx.charts.CategoryAxis:ticksBetweenLabels 
 mx.charts.CategoryAxis:title 
 mx.charts.chartClasses.CartesianChart 
 mx.charts.chartClasses.CartesianChart:dataToLocal 
 mx.charts.chartClasses.CartesianChart:graphics 
 mx.charts.chartClasses.CartesianChart:height 
 mx.charts.chartClasses.CartesianChart:horizontalAxisRenderers 
 mx.charts.chartClasses.CartesianChart:updateDisplayList 
 mx.charts.chartClasses.CartesianChart:verticalAxisRenderers 
 mx.charts.chartClasses.CartesianChart:width 
 mx.charts.chartClasses.ChartLabel:updateDisplayList 
 mx.charts.chartClasses.GraphicsUtilities:fillFromStyle 
 mx.charts.chartClasses.IAxis 
 mx.charts.chartClasses.Series:addEventListener 
 mx.charts.chartClasses.Series:buttonMode 
 mx.charts.chartClasses.Series:displayName 
 mx.charts.chartClasses.Series:selectedIndex 
 mx.charts.chartClasses.Series:useHandCursor 
 mx.charts.ColumnChart:axisTitleStyleName 
 mx.charts.ColumnChart:backgroundElements

Re: Migrating Enterprise Flex Application

I am trying to compile my mxml and action script sources. I am using the
latest emulation build. So I expect most of my source code to compile
because of the emulation build that I am compiling against. I expect to see
compile errors if any of the MX/SPARK components that I am using is not
emulated ( and no stubs ). I may be wrong. Please correct. 



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-12 Thread Carlos Rovira

Hi,

If I understand right, are you trying to compile all that libraries at
once? I think that's not the way to go. As I told you you must to go from
few files and keep growing over time. For example, I see components there
that clearly depends on MX/SPARK components, so that way will never work.

2018-07-12 12:49 GMT+02:00 chembali :

> I have uploaded 2 console outputs.
> console.out
> 
>
> consoleAS.out
>  com/file/t65/consoleAS.out>
>
> The first output ( console.out ) got generated when I tried to compile one
> of my components ( mxml and as files in this component ). Here is the
> command that I ran. The process runs successfully, but no JS gets
> generated.
>
> C:\devenv\apache-royale-js\royale-asjs\js\bin\compc -compiler.locale=en_US
> -load-config=C:/devenv/ii/trunk/tools/flex/flex4.1-
> adobe/frameworks/flex-config.xml
> -compiler.source-path=C:\devenv\ii\trunk\components\
> FlexUIPlatform/src-flexui
> -compiler.source-path=C:\devenv\ii\trunk\components\
> FlexUIPlatform/src-gen/flexui
> -include-sources+=C:\devenv\ii\trunk\components\
> FlexUIPlatform\src-flexui\com
> -include-sources+=C:\devenv\ii\trunk\components\
> FlexUIPlatform\src-flexui\cosm
> -include-sources+=C:\devenv\ii\trunk\components\
> FlexUIPlatform\src-gen\flexui\com
> -compiler.source-path=C:\devenv\ii\trunk\components\
> FlexUIPlatform/res-flexui/locale/{locale}
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\flexlib.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\automation.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\Cairngorm.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\CairngormEnterprise.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\diagrammer.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\drumbeatinsight.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\FlexSpy.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\granite.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\kap-layouts-1.6.2.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\kap-licence-1.6.1-commercial.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\MaskedTextInput.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\multicolumnform.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\svg-1.6.2.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\build\flex\flexuiplatform-asset.swc
> -js-output=C:\devenv\ii\trunk\components\FlexUIPlatform\
> build\flex\flexuiplatform
>
> The second output ( consoleAS.out ) got generated when I tried to compile
> the action script sources contained in one of the folders in the component.
> Here is the command that I ran. The JS files get generated successfully in
> this case.
>
> C:\devenv\apache-royale-js\royale-asjs\js\bin\compc -compiler.locale=en_US
> -load-config=C:/devenv/ii/trunk/tools/flex/flex4.1-
> adobe/frameworks/flex-config.xml
> -compiler.source-path=C:\devenv\ii\trunk\components\
> FlexUIPlatform/src-flexui/
> -include-sources+=C:\devenv\ii\trunk\components\
> FlexUIPlatform\src-flexui\cosm
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\flexlib.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\automation.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\Cairngorm.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\CairngormEnterprise.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\diagrammer.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\drumbeatinsight.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\FlexSpy.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\granite.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\kap-layouts-1.6.2.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\kap-licence-1.6.1-commercial.swc
> -compiler.external-library-path+=C:\devenv\ii\trunk\
> components\FlexUIPlatform\lib-flexui\MaskedTextInput.swc
>

Re: Migrating Enterprise Flex Application

I have uploaded 2 console outputs.
console.out
  
consoleAS.out
  

The first output ( console.out ) got generated when I tried to compile one
of my components ( mxml and as files in this component ). Here is the
command that I ran. The process runs successfully, but no JS gets generated.

C:\devenv\apache-royale-js\royale-asjs\js\bin\compc -compiler.locale=en_US
-load-config=C:/devenv/ii/trunk/tools/flex/flex4.1-adobe/frameworks/flex-config.xml
-compiler.source-path=C:\devenv\ii\trunk\components\FlexUIPlatform/src-flexui
-compiler.source-path=C:\devenv\ii\trunk\components\FlexUIPlatform/src-gen/flexui
-include-sources+=C:\devenv\ii\trunk\components\FlexUIPlatform\src-flexui\com
-include-sources+=C:\devenv\ii\trunk\components\FlexUIPlatform\src-flexui\cosm
-include-sources+=C:\devenv\ii\trunk\components\FlexUIPlatform\src-gen\flexui\com
-compiler.source-path=C:\devenv\ii\trunk\components\FlexUIPlatform/res-flexui/locale/{locale}
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\flexlib.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\automation.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\Cairngorm.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\CairngormEnterprise.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\diagrammer.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\drumbeatinsight.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\FlexSpy.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\granite.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\kap-layouts-1.6.2.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\kap-licence-1.6.1-commercial.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\MaskedTextInput.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\multicolumnform.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\svg-1.6.2.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\build\flex\flexuiplatform-asset.swc
-js-output=C:\devenv\ii\trunk\components\FlexUIPlatform\build\flex\flexuiplatform

The second output ( consoleAS.out ) got generated when I tried to compile
the action script sources contained in one of the folders in the component.
Here is the command that I ran. The JS files get generated successfully in
this case.

C:\devenv\apache-royale-js\royale-asjs\js\bin\compc -compiler.locale=en_US
-load-config=C:/devenv/ii/trunk/tools/flex/flex4.1-adobe/frameworks/flex-config.xml
-compiler.source-path=C:\devenv\ii\trunk\components\FlexUIPlatform/src-flexui/
-include-sources+=C:\devenv\ii\trunk\components\FlexUIPlatform\src-flexui\cosm
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\flexlib.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\automation.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\Cairngorm.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\CairngormEnterprise.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\diagrammer.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\drumbeatinsight.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\FlexSpy.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\granite.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\kap-layouts-1.6.2.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\kap-licence-1.6.1-commercial.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\MaskedTextInput.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\multicolumnform.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\lib-flexui\svg-1.6.2.swc
-compiler.external-library-path+=C:\devenv\ii\trunk\components\FlexUIPlatform\build\flex\flexuiplatform-asset.swc
-js-output=C:\devenv\ii\trunk\components\FlexUIPlatform\build\flex\flexuiplatform

Again, it is hard to see/understand what is going on without a verbose
output.





--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

Good point. I had tried to compile one component. It seems to have worked
fine. No errors. But did not generate the JS output. I am going back and
trying small sets now. The first set worked just fine and generated the JS
output successfully. 



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

Sorry. I missed Alex's response. This is exactly what I was looking for. Let
me work on it. Great. Thank you.



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-11 Thread Alex Harui

Well, see if you can get one more week.  I'm on vacation this week.  Meanwhile, 
pick out an application screen that is as simple as possible but will have 
enough to convince you and your management.  Try to build a small test case 
with Flex were as little of your code as possible brings up that screen.  Once 
you have that working in Flex, we can try to make it work in Royale.

Thanks,
-Alex

On 7/10/18, 11:46 PM, "chembali"  wrote:

Thank you for the quick response. The management's confidence level is low 
at
the moment. They are considering ReactJS to move the UI to. I am the product
owner and I strongly believe it is going to take a lot longer to move to
React. They might get convinced if I can show one simple application screen
working in JS ( with no Flash Player ) and/or getting one new emulation
component implemented.  That is my goal. They want to get the html version
functioning in 6 months with 2 developers. I am struggling to get a head
start at the moment. If I can get a start and layout a decent plan, then
they would get convinced.



--
Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C2bd45c8f341946a43cb608d5e6fa154d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636668884126198014sdata=s59FjHGIMB%2BQAu2mcfTk%2F4vomJu1gHWFqMSYtvVI51g%3Dreserved=0

Re: Migrating Enterprise Flex Application

2018-07-11 Thread Carlos Rovira

But, why is not working for you?
Maybe you should give more info
in the other hand. Start with 1 AS file, then keep adding and check the
progress of your compilation.
Maybe you have some dependences on flash/flex that you don't know are
there, or something else...

For example in my AS3 POJOS I have ArrayCollection dependences, I need to
change those to royale ArrayList...

2018-07-11 13:34 GMT+02:00 chembali :

> I agree with you on the important points that you brought up. I have around
> 1767 action scripts ( mainly controller code, POJOS and business logic )
> and
> 647 mxml ( mainly UI stuff ) in my application. I was hoping to get most of
> my action scripts converted to javascript. This is my initial task. I was
> thinking that I can use the latest nightly build and use the compc in
> \js\bin to get this going. But it does not seem to be working for me.
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>



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

Re: Migrating Enterprise Flex Application

2018-07-11 Thread yishayw

Did you see Alex's response?


Alex wrote
> COMPC only produces a SWC.  If you ended up with a SWC, unzip the SWC and
> see if there are .js files in there.  If not, you may need to set
> compiler.targets.  Post a link to the console output so we can see what it
> is doing.  Also make sure you got the nightly build from the MXRoyale
> branch and not the main develop branch. 





--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

I agree with you on the important points that you brought up. I have around
1767 action scripts ( mainly controller code, POJOS and business logic ) and
647 mxml ( mainly UI stuff ) in my application. I was hoping to get most of
my action scripts converted to javascript. This is my initial task. I was
thinking that I can use the latest nightly build and use the compc in
\js\bin to get this going. But it does not seem to be working for me.



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-11 Thread Carlos Rovira

Hi,

the main concept is that all your code that will not be using flash or flex
apis, or libraries using this apis, should translate directly. For example,
all your business logic, along VOs, DTOs, Pojos, etc... should be the same.
If you use some structural framework like PureMVC, that should follow the
same rule. At the end you are the one that knows what you application does,
and what is involved. So for me is something depending of each case.

Then for the things more "client side" (controls, layouts, containers,
components...) and the rest of visual things, you can follow various
routes. One is to use emulation components, there are many people here
working on that path that help you better than I. Other is to redo the
screens using Basic, Jewel, MDL, or other UI Set. This path is what I
choose for our application, since I want some of the new things present
nowadays in modern applications (responsiveness, new components like
Drawers or Cards...) while maintaining the ease of development.

One final thought. Think about the video I posted in the last email about
responsive layout. This can be done with React, Angular or plain JS, but as
I built this code on Royale (that is no more than the set of best practices
I see here and there), I saw the great difference in terms of less code I
have to put on my app, since Royale handles the internals for you, (a
Drawer in royale is  while in HTML/JS/CSS there's many code
behind that you must setup your own, and if you make some typo, it can be a
nightmare to track what's wrong. And finally, is about structure, Alex
explain very well about the importance of having structure like in a
building, since we all know is not only about building something, is about
maintenance and be able to detect errors sooner.

A migration in the end is not an easy task, and if you choose Royale,
React, Angular or other, you'll end having in a way or another, many
headaches, for me it's a matter of think about what's happen after the
initial problems are solved? It's easy to maintain and grow? it's easy to
make others enter the project and see what's done and join the effort? For
me those are the real points that makes me go with Flex and now with
Royale, since each time I see React or Angular code, I see many lines and
complexity that makes me think that's not the right way, that as a
Application Developer, things should be far more easy (not as a framework
developer that we must abstract all that complexity).

Just my 2...

Carlos





2018-07-11 12:58 GMT+02:00 chembali :

> Thank you Carlos for your input. It is not a bad idea. But I am trying to
> convince myself first. After going through the Royale docs, I had
> communicated to the management that a lot of our code ( probably 60% )
> would
> get migrated to JS without much effort ( just by using the Royale compiler
> ). They wanted to see that happening. I am stuck and unable to progress on
> this. I would appreciate if anyone can help me on this. Please correct me
> if
> my understanding is wrong in the first place.
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>



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

Re: Migrating Enterprise Flex Application

Thank you Carlos for your input. It is not a bad idea. But I am trying to
convince myself first. After going through the Royale docs, I had
communicated to the management that a lot of our code ( probably 60% ) would
get migrated to JS without much effort ( just by using the Royale compiler
). They wanted to see that happening. I am stuck and unable to progress on
this. I would appreciate if anyone can help me on this. Please correct me if
my understanding is wrong in the first place.



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

2018-07-11 Thread Carlos Rovira

Hi,

I have some experience in convincing management people that are not
technical involved, so I think I'd share my thoughts on this to see if this
help you.
Since 2 weeks is no time, but is clear that going the React/Angular route
will be equal or greater time, you must take a strategy, more over taking
into account that this king of "measurement" are not targeting the real
work/world.

So my bet will be to take something that "markets" the Royale path. Take
into account that here you must think more as a "seller" that a
"programmer". And you want to show something cool that makes the management
be confident with your proposal.

In this case, you can take JewelExample as a starting point (take a look at
the video in this tweet to see what you get for free [1])

1.- Make a copy/paste of this project and rebrand it with a theme color
that is as close as the colors in your app (there's 12 themes for you to
choose and even you can compile your own).
2.- Change the logo for yours.
3.- Change Navigation data provider to hard coded options that match your
app
4.- make one or two screens *only* that matches your actual app. This
should not be anything that work 100% even, 30%... just should show a good
looking screen that have most of the controls (lists, buttons, text
inputs) that shows that the project can be done.

Last, take into account that this is a POC or draft app that will show the
potential of Apache Royale, but it's not something you'll be using far
beyond the meeting. It's just a "marketing tool". Then if management
approves, will be time to take the right path, measure times and go plan
something real.

I save some projects going this route, don't know if can apply to your
case, but think I can share so you can evaluate this idea.

Good Luck! :)


[1] https://twitter.com/carlosrovira/status/1016613483255947264


2018-07-11 8:46 GMT+02:00 chembali :

> Thank you for the quick response. The management's confidence level is low
> at
> the moment. They are considering ReactJS to move the UI to. I am the
> product
> owner and I strongly believe it is going to take a lot longer to move to
> React. They might get convinced if I can show one simple application screen
> working in JS ( with no Flash Player ) and/or getting one new emulation
> component implemented.  That is my goal. They want to get the html version
> functioning in 6 months with 2 developers. I am struggling to get a head
> start at the moment. If I can get a start and layout a decent plan, then
> they would get convinced.
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>



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

Re: Migrating Enterprise Flex Application