Re: Migrating Enterprise Flex Application

[chembali]

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

[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

[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

[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

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

Re: Migrating Enterprise Flex Application

[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

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

Re: [MAVEN-BUILD] Royale-asjs - Build # 879 - Still Failing

[Carlos Rovira]

Hi,

just created this ticket at infra:

INFRA-16749 - not enough space on the disk for Apache Royale




2018-07-11 12:17 GMT+02:00 Apache Jenkins Server 
:

> The Apache Jenkins build system has built Royale-asjs (build #879)
>
> Status: Still Failing
>
> Check console output at https://builds.apache.org/job/Royale-asjs/879/ to
> view the results.




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

Fwd: [MAVEN-BUILD] Royale-asjs - Build # 879 - Still Failing

[Carlos Rovira]

Hi

We're running out of space. Hope someone take care of this issue at infra.

>From the logs:

[ERROR] [ERROR] : There is not enough space on the disk[ERROR] ->
[Help 1][ERROR]



Thanks in advance for your help

Carlos



-- Forwarded message --
From: Apache Jenkins Server 
Date: 2018-07-11 12:17 GMT+02:00
Subject: [MAVEN-BUILD] Royale-asjs - Build # 879 - Still Failing
To: carlosrov...@apache.org, comm...@royale.apache.org


The Apache Jenkins build system has built Royale-asjs (build #879)

Status: Still Failing

Check console output at https://builds.apache.org/job/Royale-asjs/879/ to
view the results.



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

Build failed in Jenkins: royale-asjs #1043

[apacheroyaleci]

See 


Changes:

[carlosrovira] remove style left from tests

--
[...truncated 203.67 KB...]

download-other-license:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

download-dependency-jar:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-cache:

download-jar:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

get-if-not-cached:
  [get] Getting: 
https://repo1.maven.org/maven2/net/sourceforge/jburg/jburg/1.10.2/jburg-1.10.2.jar
  [get] To: C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\lib\external\jburg.jar
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

double-check-file:
 [echo] ${env.ROYALE_DOWNLOAD_CACHE}
 [echo] Need file: ${still_no_file}

get-from-cache-if-needed:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

fail-if-not-found:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-sum:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

put-in-cache:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

copy-if-cached:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

download-dependency-zip:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external//jflex.jar

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

echo-project-jar:
   [delete] Deleting: C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources\project.properties
 [echo] ${INFO_DOWNLOADING_FILE_FROM}
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

download-apache-license:
 [echo] basedir is C:\Program Files 

Re: Migrating Enterprise Flex Application

[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

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

Re: Migrating Enterprise Flex Application

[Alex Harui]

Two weeks is pretty short given where we are now, depending on what they are 
looking for to convince them to fund migrating to Royale.

What is the total time they expect to have a working app without Flex?  If you 
port your Flex app to some other JS framework, that could take several 
person-years.  So saying 2 weeks is not wise, IMO.  The reason folks should 
choose migrating with Royale instead of porting to some other JS framework is 
because AS and MXML are structured, and giving up on that and porting all of 
that code to unstructured source is like building a large building without any 
forms or braces that enforce structure.  More mistakes will be made, and many 
will be hard to find and some will have a huge impact.  By investing in Royale, 
your company gets to leverage the same structured source code it has been 
using.  They get additional engineering talent by leveraging the other 
committers and contributors on this project. IOW, if you need some Flex API 
emulated, someone other than you in the Royale community might already be 
working on it.  By migrating to some other JS framework, you have to replace or 
emulate that API yourself.

If you have a dialog box or some UI that contains only DG, List, TextInput, 
Button, ComboBox, RadioButton, CheckBox, we should be able to make that appear 
on screen in two weeks, but it may not look that nice.  So it depends a bit on 
whether your management wants to see if Royale is ready now, or has a chance of 
being ready sooner than going to some other JS framework.

HTH,
-Alex

On 7/10/18, 8:42 PM, "chembali"  wrote:

The management has asked me to do a POC and demo it to them before they can
fund the migration project. Can I just convert couple of screens in the
existing Flex web app to Apache Royale JS? Do you think it is doable in 2
weeks? What are the step that I should take to make this happen? Please
share your thoughts. This is going to be the critical 2 weeks for this
migration project. 

Thank you
Sajith



--
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%7C175774dd07974f230e0708d5e6e0606f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636668773739011189sdata=2daVxR8cviYd7RJjisXbfCFKuZdIAWtTLA4w36ddUoY%3Dreserved=0

Re: Migrating Enterprise Flex Application

[Alex Harui]

Hi,

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.

-Alex

On 7/10/18, 12:15 AM, "chembali"  wrote:

So most of the components listed below that are in the mx and spark packages
would have to be implemented. Some of the components may have been defined (
the skeletons ) but not implemented. I can download the latest Royale source
and take a look to figure this out. Please correct me if I am wrong. 

BTW, I got the nightly build and tried to run compc ( JS ) compiler on one
of my components. Here is the command I tried. 

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

-js-output=C:\devenv\ii\trunk\components\FlexUIPlatform\build\flex\flexuiplatform.js

I tried with -output and -js-output. The compilation was successful, but it
did not create any output ( JS ).  Please help me here.



--
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%7C7768947146ee4a8f8cd108d5e634e07d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636668037140043504sdata=b4RvIullGLdK1HtBqixVB7pI17DoCs6C9Q7sTappDPU%3Dreserved=0