The Captivate folks might also have more informed advice about your current predicament, and I'd recommend asking over in their forum. The Captivate team would have been best position to speak about implications of Flash EOL in the context of their product, but the general strategy for those applications was to remove dependencies on Flash between 20 and allow people to republish old content to modern surfaces where that was feasible. When we as the Flash team speak about Flash, we do so from the scope of Flash Player (and sometimes Flash Authoring/Animate) as a product. There's no way that we could ever hope to track the individual implementation details for how each of those products used Flash (and multiply that over ~15 years of product versions released since the Adobe acquisition). Captivate is one of hundreds of downstream products that happen to leverage some aspect of Flash technology. I totally get the confusion from where you sit. Trust me, I am aware that we should have had something else in place, but I don't own the company and from everything that we read, and the owner read as well, it was only support that was going away, as well as the browsers not allowing it anymore. Adobe has discontinued support on other software, such as Muse, but they still function. These are not being posted online, they are just being run independently on local machines. I will worry about the security of my machine. This was just a bad move for Adobe to block the player. It is quite limited in what will function. We are fully aware that Captivate publishes as HTML5, HTML5 does not have the interactivity that our modules require. That is far more than just discontinuing support.
exe files so they could work as stand alone's. We were well aware that the browsers would not play them. The issue is that what was said, or at least the way that it was understood by our company as well as many others that I have seen post about this, is that Adobe was not going to support the player anymore. You'll definitely want to complete your migration before that happens.
#Adobe captivate support update#
Also, a future Windows Update will remove the ActiveX Flash Player from machines on Windows 8 and higher. There's some more information on HARMAN in the Enterprise EOL FAQ:Īlso, for Intranet applications, it's possible to configure Flash Player to continue to load content however, if you're shipping to a large number of customers, each customer would need to deploy an mms.cfg to their environment to work around this issue. They have a lot of experience with helping folks to package standalone applications that require Flash support.Īs you can imagine, they're handling a high volume of requests, but are working hard to get back to folks in as timely a manner as possible. We'd advise engaging with our support partner HARMAN to see if they can help you arrive at an interim option. Here's the original announcement from 2017, which also links off to the roadmaps for all of the major browser vendors: More importantly, that announcement was made in tandem with all of the major browser vendors, who are dropping support for browser plug-ins entirely around the same time. We announced that Flash Player was going away back in 2017 in an effort to give developers plenty of time to migrate. If you have the original source Captivate documents, have you tried simply publishing them to the non-Flash target from a modern version? I get that it doesn't address your LMS issue, but it might save you a lot of work. Modern versions of Captivate allow you to publish directly to HTML5.
0 kommentar(er)
