My experience working with Jewel is that we are with all the needed pieces to go to production, but we find many things to fix or improve as we go, but still need some more key points at least for our case. Some examples are: DateChooser needs to develop a "year" view, still didn't have time to do that. Or I need an autocomplete feature for combobox. But for example ComboBox is working right and show good.
we talked to make Jewel be the face of MX / SPARK some day, since in theory we can swap beads and Royale can instantiate in mxml for example an UIBase with the beads that create a component and that should work. But that's theory right now. Hope we reach that point some day, but I think first we need to improve emulation and improve jewel. as well jewel needs time to evolve since making something work takes time. I first use to make it work in actual browsers, then go to IE11 and normally things doesn't work and need to make changes to make work on IE11. Then probably if we start some day to use jewel visuals in mx/spark, we'll need to change things in jewel, but depending on how many time it will cost us to reach that point, we could end making some new code based on Jewel, since probably will need changes that could break things for other users. One last thing. I know for sure, that if you want to migrate some app you'll need to get involved in royale (using either emulation or jewel) and not look at it as something only "to use". It will be very rare that we can develop all the things you'll need, so you'll end having to contribute and use. HTH Carlos El sáb., 17 nov. 2018 a las 15:22, hferreira (<[email protected]>) escribió: > > 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/ > -- Carlos Rovira http://about.me/carlosrovira
