We're following a slightly different approach; the effort in getting the emulation classes all put together and working properly is huge and it will end up being a similar scale to the Flex libraries - lots of code handling cases that are very rarely used... so I've much preferred the Royale concepts of keeping everything as simple and modular as possible. > Yes, I read about that and it's not difficult to see that is a better > approach however is Royale exclusive to new applications (the Royale > approach), Flex compatibility (emulation) or both ? At the beginning of this project (it's already years I think) I saw a lot of discussion about it and ends up to the new Roayle approach. I have a project with 1.5 millions lines of code and more then 500 views. Change this to a new approach it's not viable at all. Change to the emulation approach in a more mature state will probably need weeks of fixs and probably month to the stable but it's acceptable. Royale came from Flex, have a new structure and it's good but should not forget from where it came from that's why I think that the mix approach that we have now it's the better one. How prefer using the new approach is not affecta at all. Perhaps migration a project and letter starting moving thinks to the new approach. The new emulation that I read on Flex foruns kept my attention.
Anyway, there's always choices for how to do things! And it's perfectly possible to use a mixture of the emulation classes, your own classes, and other Royale ones... > That's true. Flex SDK is a beast and loads many thinks that I don't need. In terms of documentation, there's some pretty good stuff available online: https://apache.github.io/royale-docs/Create%20An%20Application.html > Thanks. I already saw that. I will read more. -- Sent from: http://apache-royale-users.20374.n8.nabble.com/
