4 Replies Latest reply: Jul 10, 2012 2:22 AM by VikramGaur RSS

    Aggregator for HTML5

    jay fresno Community Member

      Is there a similar feature to aggregator in Captivate 6 that could aggregate HTML5 modules?

        • 1. Re: Aggregator for HTML5
          VikramGaur Adobe Employee

          Hello,

           

          Welcome to Adobe Forums.

           

          Aggregator only accepts .swf formats so if you are uploading your HTML5 modules on an LMS, then you can call the 2nd module at end of your 1st module.

           

          Note : When you upload your module on it gives you a direct link, you can use that direct link (or URL) on the last slide of your 1st module.

           

          Hope its helps !!

           

          Thanks,

          Vikram

          • 2. Re: Aggregator for HTML5
            jay fresno Community Member

            I'm not using an LMS for this particular project. The project will be uploaded to a web site and learners can view the modules on the web site. What is your recommendation for this situation so that learners can easily navigate from one module to the next.

            • 3. Re: Aggregator for HTML5
              jay fresno Community Member

              As I said, I'm not using an LMS. My project will be on a web page and users should be able to view it on that web page.

               

              It would be very helpful to see an example of a simple html5 set of files -- an example of a simple web page that was done in html5 for an iPad to see the structure of the folders and files.

               

              The only information I can find is in the Captivate Help menu as follows:

              Hosting HTML5 output on web servers for iPad/iPhones

              HTML5 output can be accessed on iPads/iPhones only through web browsers. Upload the entire HML5 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\

               

              This is not enough information for me to know how to set up the files.

               

              My project consists of several modules. I published them to html5 into a main folder that I created. My folder structure looks like this:

              • There is a main folder called "Published"
              • Within that "Published" folder there are 6 sub-folders, one for each module in the project, and each one with a unique name, like 'module1', module2', 'module3', and so forth.
              • Within the sub-folders are all the related files: a folder 'ar', 'a folder 'assets', a folder 'callees', a folder 'dr', a folder 'vr', a file 'index.html', and a file 'Project.js'

               

              I need to set up a link to module1. When a user finishes module1, I want them to be navigated to module2, and so forth.

               

              Being able to see an example of a simple web page that was done in html5 for an iPad with the structure of the folders and files would be extremely helpful for me.

              • 4. Re: Aggregator for HTML5
                VikramGaur Adobe Employee

                Hello,

                 

                As you mentioned that you are using IIS, so you will place the "Published" folder on the root location (C:\Inetpub\wwwroot\)

                 

                To access 'module1', URL will be http://localhost/Published/module1/index.html (Depending on your server URL, localhost might get changed with your Server name)

                 

                On the last slide you will Insert a hyperlink or Text Caption (Click box over it) and you will call URL : http://localhost/Published/module2/index.html

                 

                You can test this and then follow the same steps for other module, users will able to navigate to other modules as well

                 

                Note : Same steps will apply for Apache Server

                 

                Hope this helps !!

                 

                Thanks,

                Vikram