Hi Guys, I think emulation components are in state where allow quite a bit of Flex copoonents being compiler to JS, but not neccassery displayed.
If you have your application compiled using emulation components - That's great because you just passed first step. Next step is simply prepare those components in a way where they are displaying what you want. - There wasn't simply any volunteers who can do that. Jewel visually looks great, so maybe that's the way we can go. In my simple case would be - Take Emulation Button and Take Jewel Button - and see how to get best part in order to display something. Or Do not use at all Jewel, start stylizing on your own for your app purposes emulation components. Thanks, Piotr On Thu, Aug 23, 2018, 5:14 PM radu birsan <[email protected]> wrote: > I would like to see the examples working as well > > On Thu, Aug 23, 2018 at 5:43 PM Nico Voss - QIAGEN <[email protected]> > wrote: > >> Hi Carlos, >> >> >> thanks for the update. I am glad and thankful that so much progress was >> achieved. >> Having even Tour de Flex examples so close to accomlishment is mind >> blowing. >> >> However, the Tour de Flex examples from the link you provided are not >> working for me currently, except the main page. Clicking on any example >> causes my system to bloat and crash. Of course I didn't try every example >> because of that. But thats not the big issue. >> >> As I already mentioned, I also can not get any of the emulation >> components working after installing various nightly builds locally. How >> do you guys develop Emulation Components without being able to see them >> currently? >> >> At this moment I'm not able to show at least the tinyest bit of >> successful migration in order to convince decisionmakers, except >> "successful" compilation. I'd be glad if it turns out to be just my fault. >> >> >> Thanks again, >> >> Nico Voss >> ------------------------------ >> *Von:* Carlos Rovira <[email protected]> >> *Gesendet:* Dienstag, 21. August 2018 10:49:41 >> *An:* [email protected] >> *Betreff:* Re: Emulation/Migration of Flex to Royale - Status? >> >> Hi Nico, >> >> Emulation components are in a huge development this days, that branch >> pursues first to get the MX/SPARK Flex code base compile without errors, >> that step seems mostly done and contributors are working through getting >> visuals. Alex Harui is working in getting Tour de Flex compiled with Apache >> Royale and few days ago posted this link with the first visual results: >> >> >> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/TourDeFlexMigration/lastSuccessfulBuild/artifact/examples/mxroyale/tourdeflexmodules/bin/js-debug/index.html >> <https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2FTourDeFlexMigration%2FlastSuccessfulBuild%2Fartifact%2Fexamples%2Fmxroyale%2Ftourdeflexmodules%2Fbin%2Fjs-debug%2Findex.html&data=01%7C01%7CNico.Voss%40qiagen.com%7C78461b7c2bf747bf3df308d6074312b0%7Cdc81d03c239c4fd5a96f18a58773c86c%7C1&sdata=z6KSwn6J7XP44xUCO6VY%2Frr4x5QbSEPQrnh0hC44Jy8%3D&reserved=0> >> >> that are very promising. I think we must wait a bit so that work will be >> merged into develop hopefully soon. >> >> Regarding Jewel, that is the part where I'm working, I'm trying to upload >> every improvement as I get it done, so what you get in develop is the >> latest code I'm developing. >> >> For MXRoyale, If you plan to contribute will be great to go faster, and I >> think you can team with Alex, Alina and others to get to it sooner. >> Wait few days for Alex's coming back to talk about how to do it. >> >> Thanks >> >> Carlos >> >> >> >> El lun., 20 ago. 2018 a las 20:07, Nico Voss - QIAGEN (< >> [email protected]>) escribió: >> >> Hello, >> >> >> I am evaluating the possibility of migrating a flex/flash app to Apache >> Royale in order to get it run in native browser environments. >> >> I've read about Emulation Components, and I see there is already plenty >> of code in >> >> >> https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/MXRoyale >> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fframeworks%2Fprojects%2FMXRoyale&data=01%7C01%7CNico.Voss%40qiagen.com%7C78461b7c2bf747bf3df308d6074312b0%7Cdc81d03c239c4fd5a96f18a58773c86c%7C1&sdata=XVw2E25FpIZBKnUyQikC5S0cc5qhuh1yfvtefnen1K8%3D&reserved=0> >> >> >> Therefore I installed several nightly builds and successfully compiled >> significant parts of the app (after modifying and disabling some code). >> Yet, the browser page remains blank. Even the most simple MXRoyale example >> (Alert) doesn't show anything. >> >> However I am able to get a few Jewel examples running, some of >> them partially. >> >> Can someone please give me a glimpse of the current state of MXRoyale? >> I'm also considering to contribute, if I can. >> >> >> Thanks in advance, >> >> Nico Voss >> >> -- >> Carlos Rovira >> http://about.me/carlosrovira >> <https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=01%7C01%7CNico.Voss%40qiagen.com%7C78461b7c2bf747bf3df308d6074312b0%7Cdc81d03c239c4fd5a96f18a58773c86c%7C1&sdata=bGTcVXo7kvSEqTySKgnhKX5muzmekzaMIGr8ygwP%2FOg%3D&reserved=0> >> >> >> >>
