Re: Migrating Enterprise Flex Application

[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: compc compiler error

[Alex Harui]

Try reducing the number of files you are compiling to see if you can get 
anything to work.  Nobody has had time to make more verbose output.  Patches to 
do so are welcome.

Most of the command-line options are the same as in the Flex COMPC and MXMLC.

For Modules, you should be able to compile each module separately, just as you 
did in Flex.

HTH,
-Alex

On 7/18/18, 2:49 PM, "bhau"  wrote:

I tried with '-' also. But it hangs forever. 

"D:\Software\ApacheRoyale\apache-royale-0.9.3-src\royale-asjs>compc
-source-path=D:\Learn\MyFirstRoyaleApp\src\FlexUIPlatform\src-flexui 
-output=flexuiplatform.swc
-include-sources=D:\Learn\MyFirstRoyaleApp\src\FlexUIPlatform\src-flexui 
-compiler.show-actionscript-warnings
Using Royale Compiler codebase:
D:\Software\ApacheRoyale\apache-royale-0.9.3-src\royale-asjs
Using Royale SDK:
D:\Software\ApacheRoyale\apache-royale-0.9.3-src\royale-asjs
args:

-sdk-js-lib=D:\Software\ApacheRoyale\apache-royale-0.9.3-src\royale-asjs\frameworks\js\Royale\generated-sources
-source-path=D:\Learn\MyFirstRoyaleApp\src\FlexUIPlatform\src-flexui
-output=flexuiplatform.swc
-include-sources=D:\Learn\MyFirstRoyaleApp\src\FlexUIPlatform\src-flexui
-compiler.show-actionscript-warnings
target:JSRoyale
COMPCJSCRoyale
"

1) I wish there is log file or some verbose flag to seen what is going on.

2) Is there any detail document for these command arguments (other that
-help switch) ? Does it accept regex patterns like '*' to include multiple
sources to compile? Can we include multiple source folders by comma
separation?

3) For modular application can we compile migrated sources of module2 by
linking with existing (flex 4.1 based) module1.swc file as external-lib ? 
  



--
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%7C36e1ca58eaac44da44f708d5ecf847ae%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636675473453337966sdata=U6sJL0T8G4Qewi%2BNRqiaRl323K9Rxt6BWRY6hCQ95A8%3Dreserved=0

Re: compc compiler error

[bhau]

I tried with '-' also. But it hangs forever. 

"D:\Software\ApacheRoyale\apache-royale-0.9.3-src\royale-asjs>compc
-source-path=D:\Learn\MyFirstRoyaleApp\src\FlexUIPlatform\src-flexui 
-output=flexuiplatform.swc
-include-sources=D:\Learn\MyFirstRoyaleApp\src\FlexUIPlatform\src-flexui 
-compiler.show-actionscript-warnings
Using Royale Compiler codebase:
D:\Software\ApacheRoyale\apache-royale-0.9.3-src\royale-asjs
Using Royale SDK:
D:\Software\ApacheRoyale\apache-royale-0.9.3-src\royale-asjs
args:
-sdk-js-lib=D:\Software\ApacheRoyale\apache-royale-0.9.3-src\royale-asjs\frameworks\js\Royale\generated-sources
-source-path=D:\Learn\MyFirstRoyaleApp\src\FlexUIPlatform\src-flexui
-output=flexuiplatform.swc
-include-sources=D:\Learn\MyFirstRoyaleApp\src\FlexUIPlatform\src-flexui
-compiler.show-actionscript-warnings
target:JSRoyale
COMPCJSCRoyale
"

1) I wish there is log file or some verbose flag to seen what is going on.

2) Is there any detail document for these command arguments (other that
-help switch) ? Does it accept regex patterns like '*' to include multiple
sources to compile? Can we include multiple source folders by comma
separation?

3) For modular application can we compile migrated sources of module2 by
linking with existing (flex 4.1 based) module1.swc file as external-lib ? 
  



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

Re: Migrating Enterprise Flex Application

[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: compc compiler error

[Alex Harui]

Are you missing the '-' before 'source-path'?  The compiler might be thinking 
that is the main source file.

HTH,
-Alex

On 7/18/18, 9:59 AM, "bhau"  wrote:

Hi,

I am getting following error when compiling with compc command. 
Any help is appreciated. 


D:\Software\ApacheRoyale\apache-royale-0.9.3-bin-js\royale-asjs\js\bin>.\compc
source-path=D:\Learn\MyFirstRoyaleApp\src\FlexUIPlatform\src-flexui 
-output=flexuiplatform.swc
-include-sources=D:\Learn\MyFirstRoyaleApp\src\FlexUIPlatform\src-flexui 
-compiler.show-actionscript-warnings
Using Royale Compiler codebase:
D:\Software\ApacheRoyale\apache-royale-0.9.3-bin-js\royale-asjs\js\bin\..\..
Using Royale SDK:
D:\Software\ApacheRoyale\apache-royale-0.9.3-bin-js\royale-asjs\js\bin\..\..
args:

-sdk-js-lib=D:\Software\ApacheRoyale\apache-royale-0.9.3-bin-js\royale-asjs\js\bin\..\..\frameworks\js\Royale\generated-sources
source-path=D:\Learn\MyFirstRoyaleApp\src\FlexUIPlatform\src-flexui
-output=flexuiplatform.swc
-include-sources=D:\Learn\MyFirstRoyaleApp\src\FlexUIPlatform\src-flexui
-compiler.show-actionscript-warnings
target:JSRoyale
COMPCJSCRoyale
java.util.NoSuchElementException
java.util.NoSuchElementException java.util.ArrayList$Itr.next(Unknown

Source)com.google.common.collect.Iterators.getOnlyElement(Iterators.java:308)com.google.common.collect.Iterables.getOnlyElement(Iterables.java:294)org.apache.royale.compiler.internal.targets.JSTarget.getRootClassCompilationUnit(JSTarget.java:219)org.apache.royale.compiler.internal.targets.JSTarget.buildAndCollectProblems(JSTarget.java:190)org.apache.royale.compiler.internal.targets.JSTarget.build(JSTarget.java:114)org.apache.royale.compiler.internal.targets.JSTarget.build(JSTarget.java:226)org.apache.royale.compiler.clients.COMPJSCRoyale.buildApplication(COMPJSCRoyale.java:408)org.apache.royale.compiler.clients.COMPJSCRoyale.buildJSTarget(COMPJSCRoyale.java:373)org.apache.royale.compiler.clients.COMPJSCRoyale.buildArtifact(COMPJSCRoyale.java:365)org.apache.royale.compiler.clients.COMPJSCRoyale.compile(COMPJSCRoyale.java:163)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:240)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:197)org.apache.royale.compiler.clients.COMPJSC._mainNoExit(COMPJSC.java:210)org.apache.royale.compiler.clients.COMPJSC.mainNoExit(COMPJSC.java:140)org.apache.royale.compiler.clients.COMPJSC.staticMainNoExit(COMPJSC.java:125)org.apache.royale.compiler.clients.COMPJSC.main(COMPJSC.java:108)


27.453418911 seconds

Thanks,
--Bhau



--
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%7Ca89afb19209a4d73ff0908d5eccfc9e3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636675299539423387sdata=I15egzK1jvC6Qym7G%2FRbpFMuoNjbrjFQj39qvqcnKDg%3Dreserved=0

compc compiler error

[bhau]

Hi,

I am getting following error when compiling with compc command. 
Any help is appreciated. 

D:\Software\ApacheRoyale\apache-royale-0.9.3-bin-js\royale-asjs\js\bin>.\compc
source-path=D:\Learn\MyFirstRoyaleApp\src\FlexUIPlatform\src-flexui 
-output=flexuiplatform.swc
-include-sources=D:\Learn\MyFirstRoyaleApp\src\FlexUIPlatform\src-flexui 
-compiler.show-actionscript-warnings
Using Royale Compiler codebase:
D:\Software\ApacheRoyale\apache-royale-0.9.3-bin-js\royale-asjs\js\bin\..\..
Using Royale SDK:
D:\Software\ApacheRoyale\apache-royale-0.9.3-bin-js\royale-asjs\js\bin\..\..
args:
-sdk-js-lib=D:\Software\ApacheRoyale\apache-royale-0.9.3-bin-js\royale-asjs\js\bin\..\..\frameworks\js\Royale\generated-sources
source-path=D:\Learn\MyFirstRoyaleApp\src\FlexUIPlatform\src-flexui
-output=flexuiplatform.swc
-include-sources=D:\Learn\MyFirstRoyaleApp\src\FlexUIPlatform\src-flexui
-compiler.show-actionscript-warnings
target:JSRoyale
COMPCJSCRoyale
java.util.NoSuchElementException
java.util.NoSuchElementException java.util.ArrayList$Itr.next(Unknown
Source)com.google.common.collect.Iterators.getOnlyElement(Iterators.java:308)com.google.common.collect.Iterables.getOnlyElement(Iterables.java:294)org.apache.royale.compiler.internal.targets.JSTarget.getRootClassCompilationUnit(JSTarget.java:219)org.apache.royale.compiler.internal.targets.JSTarget.buildAndCollectProblems(JSTarget.java:190)org.apache.royale.compiler.internal.targets.JSTarget.build(JSTarget.java:114)org.apache.royale.compiler.internal.targets.JSTarget.build(JSTarget.java:226)org.apache.royale.compiler.clients.COMPJSCRoyale.buildApplication(COMPJSCRoyale.java:408)org.apache.royale.compiler.clients.COMPJSCRoyale.buildJSTarget(COMPJSCRoyale.java:373)org.apache.royale.compiler.clients.COMPJSCRoyale.buildArtifact(COMPJSCRoyale.java:365)org.apache.royale.compiler.clients.COMPJSCRoyale.compile(COMPJSCRoyale.java:163)org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:240)org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:197)org.apache.royale.compiler.clients.COMPJSC._mainNoExit(COMPJSC.java:210)org.apache.royale.compiler.clients.COMPJSC.mainNoExit(COMPJSC.java:140)org.apache.royale.compiler.clients.COMPJSC.staticMainNoExit(COMPJSC.java:125)org.apache.royale.compiler.clients.COMPJSC.main(COMPJSC.java:108)


27.453418911 seconds

Thanks,
--Bhau



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

Re: Migrating Enterprise Flex Application

[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

[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

[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

[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

[Yishay Weiss]

From: Olaf Krueger
Sent: Wednesday, July 18, 2018 2:06 PM
To: 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

[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

[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

[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

[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

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