Hi,
The next release should have better support for emulation components. You do
have to change the xml namespace to use them:
xmlns:mx="library://ns.adobe.com/flex/mx"
xmlns:s="library://ns.adobe.com/flex/spark"
need to be changed to:
xmlns:mx="library://ns.apache.org/royale/mx"
xmlns:s="library://ns.apache.org/royale/spark"
Regarding migrating your application, we have some tooling to try to analyze
your code and see what Flash and Flex APIs are using. And you can just fork
your code, replace the XML namespaces and see what happens.
Regarding the external components, you can examine the imports they use to see
what flash classes are being used. MXML files have some hidden "automatic"
imports so it is a bit harder to see what they use. We have emulated some
Flash classes, but it is not a goal to emulate all of them. We want to get
away from dependencies on Flash APIs because some sort of rely on the way Flash
renders, and some features like listener priorities and weak references are not
easily reproduced on other platforms.
You can get started now with a nightly build. Please continue the conversation
over at d...@royale.apache.org.
Thanks,
-Alex
On 11/6/18, 5:26 PM, "hferreira" <hferreira...@gmail.com> wrote:
Hi Alex,
I just come from the first Apache Royale test (current version 0.9.2).
I think that my last attempt was 0.5 (or less) !
Starting on the IDE:
I know by now why there is no starting tutorial for IntelliJ: Because does
guys are waiting to see where this will end up, so there is no official
IntelliJ support by now.
Flash Builder as said before is not an opinion for years and I will not go
back there.
I tryed Moonshine and seems that this IDE was designed for Apache Royale. I
couldn't expect that could be easier to start a project (even for a
beginner), however without intellisense support unfortunately it's a no.
For last but not least, I went thru Visual Studio Code (ho, boy that text
editor evolved from my last test). Everything it's manual however following
this instructions
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FVisual-Studio-Code&data=02%7C01%7Caharui%40adobe.com%7C49a953b78b2a4e324c2208d6444fff87%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636771507711668266&sdata=jIJop6p5wZur1kZksz%2BvBUGjxeQmchJ06Rpq21ffsoQ%3D&reserved=0
I was able to
build a Hello Word test project and then started to play around.
Intellisense works out of the box !
And I saw references to TLF on intellisense that you mentioned before (very
good :) ).
Pure Apache Royale it's noticeable more mature than before and without
compiling errors on the first experience. It's not a alpha product anymore
an deserves to be almost version 1.0 but this was a short test.
I didn't even care about debug for now.
As explain before, for me, to be even possible to move from Apache Flex to
Apache Royale, I need to:
1. Move a very big ship (block by block) to your new approach emulation
components (accepting that they will not optimised for speed);
2. Find a way to move a few external components (I have the source code of
all them);
3. Fix a lot of issues during a few months in tests;
4. Then and only then, I can start moving pieces of components to pure
Apache Royale (accepting that there is the possibility to end up with a mix
of pure Apache Royale components and emulated ones but I already have that
with MX and Spark anyway).
During this test, I tryed but not be able to use any MX component so my
guess is that is not yet on this release and perhaps only on the night
builds or even on your local machine waiting for commit. This assumption is
correct ?
MX and Spark emulation are predicted for the next 0.9.3 ?
As you can imagine, there is old code that is not following the best
approach.
I have the business logic separated from the UI but it's not all the cases.
My first work will be starting refactoring and this, I can start right now.
As much perfection my code is before the port, easier will be.
Then, only after MX and Spark emulation be on a release will make sense to
start but I'm excited to do and when I enter on that space, for sure that I
will be a contributor (at least on documentation for others, report bugs and
provide fixs).
Thank you very much for you work since always on this project.
For what I saw, I believe that one day I may move my code (I was not
expecting that).
--
Sent from:
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-development.2333347.n4.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C49a953b78b2a4e324c2208d6444fff87%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636771507711668266&sdata=4slKcrT4gvKwLoDhtvOfNXPMX%2BDEf7sGRI7qDUOcPts%3D&reserved=0
