Hi Michelle, maybe one more thing that you should know is about the MX and SPARK emulation effort. Alex and others and working in Royale in emulate the MX/SPARK Apis and components, so people that wants to migrate from Flex to Royale (before known as FlexJS) can do it more quickly
The work is still in progress, but many people could still compile his code agains that code, although many of the components still doesn't show on screen, and that will come hopefully soon. You (and others) are welcome to contribute and help in that effort. To know more about Apache Royale visit our webstite: https://royale.apache.org, and follow us on twitter, facebook, linkedIn and/our Google plus thanks Carlos El jue., 1 nov. 2018 a las 19:36, Alex Harui (<aha...@adobe.com.invalid>) escribió: > Hi Michelle, > > FlexJS became the Apache Royale project about a year ago. I encourage you > to find out more about FlexJS/Royale on the Royale mailing list ( > d...@royale.apache.org). > > It isn't just IE and Edge. Just about every popular browser will turn off > Flash by the end of 2020. Of course, I'm biased towards Royale since > that's what I spend my day working on, but I think the safest choice is to > choose an open-source development environment like Royale. That way you > are free from corporate decisions about product futures. No corporation > controls Apache projects like Royale, and users are encouraged to become > contributors so that you or other people like you can help cut releases, > fix bugs, create new features, etc. That way, you ensure that you have > more control over the future. > > So far, I've heard the following options: > > 1) Apache Royale > 2) Adobe AIR > 3) Extended IE support > 4) Custom Browser. > > Depending on resources and timeframes, Adobe AIR might make sense if you > are ok changing your deployment model. All future updates have to be > "installed" or your AIR app has to be a "shell" that downloads the rest of > the app. Converting a Flash Browser app to AIR might be less work if there > is a lot of Flash animation/timeline content. Royale doesn't have any > replacement for frame-based SWF animations. If you know that browser video > quality is insufficient, you might also choose AIR video. You also need to > be aware of subtle differences between AIR and Flash around security, > ExternalInterface, and some other APIs. On the other hand, having access > to the file system might be a benefit. > > If you control what browser your users use, I've heard that IE will have > extended support for Flash, but I think there is an end date for that > eventually. > > I've also heard that some folks are trying to create browsers that will > host the Flash plugin. > > Anyway, I hope to see you on the Royale lists. > > -Alex > > On 11/1/18, 3:00 AM, "michelle_s...@tzuchi.com.tw" < > michelle_s...@tzuchi.com.tw> wrote: > > Hi, good day! > > We have a very large and complex healthcare information system > where its front-end is written in Flex > (the Flex SDK we are currently using is FlexSDK416). > > We are very concerned about the future of the browser support > particularly Internet Explorer & Edge > for our Flex applicaton. > > If Internet Explorer & Edge will not be supporting Flex anymore > starting > next year, > how and to what technology should we migrate our Flex application? > Should we use AIR, FlexJS or which one is appropriate? > I would like to have your professional advise on this matter as you > are > the experts on Flex. > > I would greatly appreciate your response on this matter. > > Thanks and regards, > Michelle > Hualien, Taiwan > Tzu Chi Medical Foundation > > -- Carlos Rovira http://about.me/carlosrovira
