Re: Migrating Enterprise Flex Application

I downloaded the nightly build and it is working fine in the nightly build. -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

That error indicates that something is wrong with the set of beads specified for the class (PanelWithControlBar). I just tried MenuExample and AccordionExample in my local build and they seemed ok. You might want to try a nightly build. HTH, -Alex On 10/8/18, 10:01 PM, "chembali" wrote:

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

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

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

Re: Migrating Enterprise Flex Application

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

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:

Re: Migrating Enterprise Flex Application

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

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

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

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"

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

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

Re: Migrating Enterprise Flex Application

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. > > >

Re: Migrating Enterprise Flex Application

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.*"

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

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

Re: Migrating Enterprise Flex Application

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"

Re: Migrating Enterprise Flex Application

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:

Re: Migrating Enterprise Flex Application

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,

Re: Migrating Enterprise Flex Application

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">

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

an 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

RE: Migrating Enterprise Flex Application

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

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

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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.

Re: Migrating Enterprise Flex Application

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

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

Re: Migrating Enterprise Flex Application

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

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

Re: Migrating Enterprise Flex Application

> 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

RE: Migrating Enterprise Flex Application

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

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:

RE: Migrating Enterprise Flex Application

>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

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 ab

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

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

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:

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

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

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

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

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

Re: Migrating Enterprise Flex Application

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

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"

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,

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

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

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

Re: Migrating Enterprise Flex Application

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.

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

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:

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

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

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

Re: Migrating Enterprise Flex Application

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

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 ).

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

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

Re: Migrating Enterprise Flex Application

Your home grown APIs may not need to be rewritten in JS. It depends on what they depend on. If they depend on mx and spark, the emulation components in the api report should allow your code to automatically port. It is more work if you have Flash dependencies, but still possible. The main

Re: Migrating Enterprise Flex Application

Most of the api's listed in the report are home grown ( not 3rd party ). I guess we need to rewrite then in JS. The true 3rd party apis are alivepdf and granite libraries. I believe there are counterparts in the JS world. I need to do more research. I was reading the doc on writing emulation

Re: Migrating Enterprise Flex Application

Hi, I have downloaded the files and will turn it into a single combined report. Some next steps might be: -Look through the report files yourself for 3rd-party components and come up with a plan for replacing those. -Decide whether you want the UI to remain as similar as possible or whether you

Re: Migrating Enterprise Flex Application

I generated the api reports for the components in my application. Please see the attached reports. Please review them. What should be my next steps? reportControlMgmt.txt reportDashboards.txt

Re: Migrating Enterprise Flex Application

Hi, Yes, we would expect duplicates. I was able to use Excel to group and subtotal duplicates. At a quick glance, the list of APIs look like there is a lot of overlap with Alina's app so you should be able to leverage a lot of the work she and Shahid have done. -Alex On 7/2/18, 11:35 PM,

Re: Migrating Enterprise Flex Application

I fixed the compile errors and generated the api report for my first component. reportFlexUIPlatform.txt . Please review it and let me know your comments. I will start working on generating the api reports

Re: Migrating Enterprise Flex Application

It might depend on what kind of errors. Try the api-report, see what you get and think about whether it makes sense. Thanks, -Alex On 6/29/18, 1:49 AM, "chembali" wrote: I skipped the offending mxml and the compiling of my first component completed. It is giving me a bunch of

Re: Migrating Enterprise Flex Application

I skipped the offending mxml and the compiling of my first component completed. It is giving me a bunch of errors. Should I try to fix these compile errors or can I just rerun with the api-report option to generate the report? -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

The name of the mxml file is PopupTemplate.mxml. I have attached the ResizableTitleWindow.as -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Migrating Enterprise Flex Application

Interesting. What is the name of this MXML file? What does ResizableTitleWindow.as look like? Is ResizableTitleWindow.as in the same swc as this MXML file? For the purposes of generating the API report, you can probably skip this entire file. It appears to only be using VBox from Flex.

  1   2   >