Jewel which is separate UI set and not using Basic at all > OK, like mx and spark in the Flex framework ?
emulation + Jewel for good looking that probably require some work > As the first approach no. first get compiled using emulation and then - Using those components make it visible and working. > Yes, that was my first idea. That last part require work - No matter in which direction you go. > No doubt. I'm doing all this questions, because I'm new to Apache Royale world and whant to know more to understand the approach that is different from how is used to Flex SDK. I already did a few tests on the last days with latest Royale build + emulation + small ports of Flex code and it's very easy to port code and build with few changes however almost nothing happens because we are on the early days of the emulation. I know that now. My first ideia was in fact to port to Roayle/Flex emulation and latter perhaps move to Jewel or just leave it on the emulation forever. I don't have the knowlege to help on the emulation process, so I have 2 choices now: 1. Wait and came back here in a few months and see where is the emulation point; 2. Forget the emulation 1 to 1 and jump directly to Jewel, starting a new aside project, recreating and testing every view. Independent of the selected choice, I came to the conclusing that I should learn Royale framework and the Joewel component on my spare time and then start playing around with Royale/Jowel and see what is missing to my current needs. Only then, I should decide the best way for me. -- Sent from: http://apache-royale-users.20374.n8.nabble.com/
