Hi, there's no one path for any of us migrating. So for example, Alex (Harui) did a great work with emulation components (MXRoyale library) in Royale to make Flex migration as easy as possible. I think the example is in Tour De Flex, he migrated that app with minimum changes. Maybe is not 100% same code as Flex but very close. So you could try that alternative.
In the other hand we have Jewel UI set that are a modern set of components with most of the ones you know from MX/Spark but some new ones for designed to use in mobile devices. We migrate a huge app where all logic was mostly the same but we need to migrate the UI and tweak a little bit to conform with Jewel UI Set. So around 70-80% of code and structure from Flex was valid. About data crunching, since there's no more info about it I assume AS3 code. All AS3 code can run as is in most cases always not depend in flash player APIs (I-e: PureMVC works the same since is pure AS3 with no Flash Player dependencies). If you use flash apis, then you need to try to change APIs for royale ones (most of the times it will be possible). HTH Carlos El vie., 19 jul. 2019 a las 17:14, gkk gb (<modjkl...@comcast.net>) escribió: > I have a Flex app 4.12 that does a lot of data crunching. If I want to > create an Apache Royale app that is far simpler than the Flex app but > relies on the Flex app's code for data crunching, what's options do I have > to do this? > > > The Royale app (HTML output) would accept some inputs from the user then > crunch some data and return the results in a table, for example. Is it > possible to have a single code-base that contains both Flex and Royale > apps, where the first exports to Air and the second to HTML? Or, should I > copy the Flex codebase and hack it to create the Royale app (if so, can the > two projects share the same libraries)? etc. > -- Carlos Rovira http://about.me/carlosrovira
