Feel free to zip up all of your API reports and post a link to where I can
download them.
My concern is that if you get too many errors compiling your SWCs that the
Royale Compiler may not be outputting all of the Flex API usage. So it would
be best to have zero errors (or close to zero). It is pretty rare for your
code in a SWC to not use a Flex API somewhere, so I would expect to see Flex
APIs listed in every API report for every SWC and module.
Each API report will list your classes, the Flex APIs used, the Flash/AIR APIs
used, and any third-party library APIs that were used. You can then build a
list of Flex APIs you are using and compare against what is in the list for
Alina's app. That should be roughly what is available at compile-time. For
runtime, we have only the most basic operations working for mx Button,
Checkbox, RadioButton, TextInput, TextArea, ComboBox, List, DataGrid,
NumericStepper, DateField, DateChooser, MenuBar, maybe Menu, Panel, VBox, HBox.
And Spark Button. I'll probably work on Tree next.
You don't have to remove references to Flex classes, but yes, you do have to
change the xml namespaces in your MXML files. The Flex compiler looks for a
flex-config.xml in the Flex SDK. The Royale Compiler looks for a royale-config
in the Royale SDK. The flex-config.xml file lists the Flex SWCs in the library
path. The royale-config.xml lists the Royale SWCs. All other command-line
options that you specified when building the SWFs with Flex should remain the
same. That's the theory, anyway, but we'll see.
However you built your app with Flex (Maven, Ant, command-line) should work
with Royale. But I’m sure there are bugs, so let us know the details of what
you run into.
-Alex
On 7/23/18, 12:18 PM, "bhau" <bhau2...@gmail.com> wrote:
Hi Alex,
Generating api-report is not a problem. It is getting generated through
MXLMC and COMPC compiler.
Please advise (and correct me also) on my approach (or understanding) for
migration.
1) API report contains list of all components being used in my application
(or module) . It is not the list of components needs to be emulated. I was
generated this api-report by running MXMLC on my main application mxml file
to find out which components I have to work on for this migration. But you
have suggested to generate api-report for all modules (one by one) ,which is
very huge list.
2) I don't know which of these components from api-report have been already
emulated completely and which are only emulated with compile only mode. How
can I find out to calculate my final to-do list for emulation ?
3) You have mentioned in earlier response that I don't have to remove any
adobe flex references before running compc compiler. That means I don't have
to replace adobe mx/spark namespace with Royale namespace in any of my mxml
file. Does Royale compiler need command line argument to locate these adobe
classes (or libraries) ? Does Royale compiler has some mapping between adobe
mx/spark to Royale mx/spark components to generate corresponding js files?
How and where does it find that?
4) If I have to generate only js files (no swf files) for migration. What
would be right approach for application having many modules linked with each
other?
Thanks,
--Bhau
--
Sent from:
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7Cb9a53625093f4b627d3008d5f0d10f9f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636679703057589156&sdata=U8lzL6%2B0TMRgficCCTzfDJ11syrTsjJ9bxrFqGCgAro%3D&reserved=0
