You can view the Interactions in the project only when you view the HTML5 output hosted on a web server. Interactions are not visible when you view the published output locally on your computer.
You can also publish HTML5 output of projects to Adobe Connect. For more information, see Publish projects to Adobe Connect (available only in the update for subscription and Adobe Software Assurance customers).
From Adobe Captivate 8.0.1 and above versions, you can publish projects to PhoneGap without using a standalone App packager application. Publishing to Devices (app) menu item is integrated in Captivate. Follow the steps below:
Certificates and authentication keys are essential for users to enable security for their accounts and prevent any unauthorized access.
Create certificates for iOS
- Refer to the apple developer support site and create an app developer certificate. Refer toprogram enrollment for more information.
- Refer to the instructions on the PhoneGap build site as mentioned below to convert the certificates into supported P12 format and upload the certificates:
Generate keys for Android
- Refer to the instructions on the PhoneGap build site to generate and upload keys to PhoneGap build.
In Captivate 8.0.1, after you log in with PhoneGap user id and password, click Next in Publish window, and provide certificate info in the dialog as shown below:
AppleKey title in the above snapshot represents the certificate name that you uploaded in PhoneGap build. Your certifcates are populated in the Title drop down after you upload them in PhoneGap build website. Similarly, the keys you uploaded to PhoneGap build appear in Title drop down. You can continue to publish even if you do not have keys for Android by choosing No key selected option.
If you publish using Windows 8 OS, you can see an additional option in Publish To as Windows 8. If you choose this option, the dialog appears as below:
Project title, location information, and the options under More are similar to iOS/Android dialog options. Follow the steps accordingly.
If you remove preferences of Adobe Captivate, then you have to create certificates again.
Objects in the project that are not supported in the HTML5 output get dynamically listed in the HTML5 Tracker. To view the tracker, click Window > HTML5 Tracker. When you delete or modify such objects in the project, the tracker too is updated.
The following objects and slides are not published in the HTML5 output:
- Text and SWF animations (only the first frame is visible).
- Mouse click animations (only one default click effect is supported).
- Question pools, Likert question slides, and random question slides (supported in Cp 7 and later).
- Slide transitions.
- Slide background if a SWF file is used.
- Audio attached to invisible objects.
- Borders (supported in Cp 7 and later).
- Reporting to internal server and Acrobat.com (supported in Cp 7 and later).
- Video streaming using RTMP is not supported in HTML5 output.
Note: FLV files that are created using On2VP6 codec only are supported in the HTML5 output.
- Object effects: (CP 7) The unsupported effects are marked with an asterisk (*) in the object effects list. The effects marked with double asterisks (**) are rendered differently in HTML5 output compared to a SWF output.
Left to Right
Left to Right Ease
Right to Left Ease
Right To Left
HTML5 output can be accessed on iPads/iPhones only through web browsers. Upload the entire HTML5 output folder to a web server root folder and make the URL available to your users. Your users can access the URL from their iPad/iPhone and view the content that plays within the web browser.
Webserver root for IIS: C:\Inetpub\wwwroot\
Webserver root for Apache: <Apache install folder>\htdocs\
HTML5 output is supported only on iPads with OS version 5 or later.
HTML5 output is supported only on the following browsers:
Type the following URL in one of the above web browsers:
For example, if the HTML5 output folder is MyCpProject, the URL will be:
- Use the recommended project resolutions (presets) for iPad.
- Avoid overlapping audio in the project. If at all you need overlapping audio, read the article Adobe Captivate audio for iPad.
- In general, do not have too many overlapping media (especially very short ones) for movies that have to run on IOS devices.
- Disable button click sound as it may lead to unexpected behavior on iPad occasionally.
- Disable Scalable HTML Content in the Publish dialog box.
Avoid using overlapping audio in your projects if they are to be used extensively on iPads.
If you use overlapping audio, the preferences to different types of audio are as follows:
The sequence in this case is:
Object audio > Slide audio > Background audio
Object audio is played first, followed by slide and background audio.
Case 1: Object 1 has audio for 0-4 seconds and Object 2 has audio for 0-8 seconds. Object 2 is lower in the z-order of the Timeline.
Audio of Object 2 is played for 8 seconds and then Adobe Captivate checks if there is any other audio at that point (8th second) in the Timeline. In this case, there is no audio to be played at the 8th second. Therefore, audio of Object 1 is not played.
Case 2: Object 1 is lower in the z-order.
Audio of object 1 is played for 4 seconds. A check at 4th second indicates that the audio of object is for 4 more seconds. So, the audio of second object is played from the beginning. After 8th second when the second object’s audio is played, a check on the Timeline indicates that there is no more audio to be played.
Case 1: Object Audio is present from 0-4 seconds and Slide Audio is present at the same time. (no background audio)
Object Audio is played first for 4 seconds and then the whole Slide audio will be played.
Case 2: Object Audio is present from 2-6 seconds and slide audio is present at the same time. (no background audio)
First Slide Audio will be played for 2 seconds, then Object Audio for 4 seconds and then Slide Audio again.
Case 3: Object Audio is present 0-4 seconds, Slide Audio 0-8 seconds and Background Audio is present. (slide duration let say is 14 seconds)
Object Audio is played for 4 seconds, then slide audio for 8 seconds, then the remaining slide duration background audio is played.
Videos are played one after the other based on their order in the Timeline.
For example, consider that two videos are present on a single slide with the following durations on the timeline:
Video that is lower in the z-order is played first. For example, consider that Video1 is present on a slide from 0-8 seconds and Video2 is also present on the same slide from 0-12 seconds.
When Video 2 is present lower in the z-order, Video 2 is played for 12 seconds and the Video1 is never played.
When Video1 is present lower in the z-order, Video1 is played for 8 seconds and then Video2 is played until the slide duration.