I had posted a fix for using Captivate 6 HTML5 projects in DPS. In that article, I showed how to remove embedded browser check code so that your project would render without a browser check in DPS. However, in Captivate 7, removing the browser check script from the index.html file doesn’t do the job. (If you have my DPS Examples app installed on your iPad, and you’re reading this blog on your iPad, then tap here to see examples of Captivate content running in a DPS folio.)
I asked the Captivate engineers if they had a trick up their sleeves, and this is what they delivered (thanks to Suresh Jayaraman and independently to Mayank Mahajan: if you see either of them, give them each a high five…)
- Open “AdobeCaptivate.ini” file present in Adobe Captivate installation folder .
- Add the following line of text at line 2 or line 3 of the “AdobeCaptivate.ini” file .
SuppressIncompatibleBrowserMessage = 1
- Publish the project to HTML 5
Now, the result is a folder with an index.html file. As I indicated in the earlier article, you can then make a Web Content overlay and point it at your index file. Another approach is to use the Captivate project as an HTML article rather than in a Web Content Overlay.
If you have portrait-only folio, rename the index.html file to index_v.html. If you have a landscape-only folio, rename the index.html file to index_h.html. If you have a dual-orientation folio, don’t change the name of the index.html file. In the Folio Builder panel of InDesign CC, click the “Add article” button and choose Import Article.
Enter your article metadata and then browse to the folder that contains your Captivate project, and then click OK.
InDesign will now seem to go into zombie mode, in which it will appear to be processing the HTML folder, but will never finish the task. The solution, which I outlined in another blog post, is to quit InDesign while it is hanging on the HTML import. Actually, what you need to do is to tell inDesign to quit, but don’t actually quit. Instead, wait, and InDesign will emerge from its coma and finish importing the HTML article.
Then, you can politely tell the “Do you really want to quit?” dialog that you do not want to quit, and your HTML project from Captivate will now be safely in your folio, with no browser check. Once published, your user will need to push the “play” button on the Captivate project to start it, which is annoying to be sure. I hope the Captivate engineers will allow us one day to auto play a Captivate HTML5 project, if only in our DPS folios.