If you have HTML experience, you can take your published Captivate files and create links from your Web page to the published files. Of course, you’d need the HTML experience to proceed.
MenuBuilder offers a quick way to package your Captivate projects for distribution to your customers— without the need for HTML experience. Using MenuBuilder, which comes with Captivate, you can create a “home” page or “menu” that contains links to your Captivate projects or other links. The “home” page can serve as the gateway to your projects.
If you’ve purchased my Captivate workbooks, you already know how to create MenuBuilder projects. In that case, I won’t bore you with the details of how to create the projects. I will, however, provide two cautionary tales when working with MenuBuilder (the first tip is in my Captivate book, the second is not).
First, when creating a link to an item, make sure you select the Save file with project checkbox. If you fail to select this option, users clicking the link after you have published the project will following the absolute path to your project, such as C:\Captivate2Data\ MenuBuilderFiles\MenuBuilderExports instead of the CD or Web site where your movie are actually stored. With the Save file with project option selected, the link will instead become a local link.
Second, after publishing your MenuBuilder project as SWF files, check the target folders. I’m betting the folder will be missing a few files, mainly the skin .swf that gets published if you include a skin in your Captivate 2 movie; and the standard.js file that was discussed in last week’s newsletter. Without these two critical files, your movie will not play. The solution is a manual one, but it works. Find the skin .swf and .js files in the folder where you published your Captivate project prior to working on the MenuBuilder project. Copy the files and paste them into the MenuBuilder published project folder before uploading the published files to your Web server or, worse, burning the files to a CD.
I’m currently working in Captivate 3, trying to build a menu for some projects to be distributed via CD. So far, the menu works well for me; it’s when others test the menu that it doesn’t work.
I followed the tips above; the folder has all the files it needs.
2 people have not been able to get any of the links to work.
1 person got the links to work (by downloading the newest flash player), but a link to an internet file would not open at all – not even a response.
Any suggestions would be appreciated. Thanks.
I’m currently working in Captivate 3, trying to build a menu for some projects to be distributed via CD. So far, the menu works well for me; it’s when others test the menu that it doesn’t work.
I followed the tips above; the folder has all the files it needs.
2 people have not been able to get any of the links to work.
1 person got the links to work (by downloading the newest flash player), but a link to an internet file would not open at all – not even a response.
Any suggestions would be appreciated. Thanks.
I’m currently working in Captivate 3, trying to build a menu for some projects to be distributed via CD. So far, the menu works well for me; it’s when others test the menu that it doesn’t work.
I followed the tips above; the folder has all the files it needs.
2 people have not been able to get any of the links to work.
1 person got the links to work (by downloading the newest flash player), but a link to an internet file would not open at all – not even a response.
Any suggestions would be appreciated. Thanks.
I made a menubuilder and I am trying to jump to Articulate Presenter files. Articulate makes a player.html file that you need to jump to. Of course all 4 modules that I made are named player. So, I named them player1.html, player2.html etc… These files jump to a Folder named Player. This works fine if the modules are in separate folders and I link by C:folder/folder etc… The problem is that when I publish the file anyone that clicks on it can’t get to my C: drive
If I use your Save file with project function, it jumps to the first Player folder that it sees causing all my links to go to the same file. How do I get out of this?
I made a menubuilder and I am trying to jump to Articulate Presenter files. Articulate makes a player.html file that you need to jump to. Of course all 4 modules that I made are named player. So, I named them player1.html, player2.html etc… These files jump to a Folder named Player. This works fine if the modules are in separate folders and I link by C:folder/folder etc… The problem is that when I publish the file anyone that clicks on it can’t get to my C: drive
If I use your Save file with project function, it jumps to the first Player folder that it sees causing all my links to go to the same file. How do I get out of this?
I made a menubuilder and I am trying to jump to Articulate Presenter files. Articulate makes a player.html file that you need to jump to. Of course all 4 modules that I made are named player. So, I named them player1.html, player2.html etc… These files jump to a Folder named Player. This works fine if the modules are in separate folders and I link by C:folder/folder etc… The problem is that when I publish the file anyone that clicks on it can’t get to my C: drive
If I use your Save file with project function, it jumps to the first Player folder that it sees causing all my links to go to the same file. How do I get out of this?
Hi John,
For the links to work as stress-free as possible, I recommend you publish everything to be used in the menu to the same folder. As you’ve seen, the wheel starts to come off of the cart if you publish to different sub-folders.
Kevin
Hi John,
For the links to work as stress-free as possible, I recommend you publish everything to be used in the menu to the same folder. As you’ve seen, the wheel starts to come off of the cart if you publish to different sub-folders.
Kevin
Hi John,
For the links to work as stress-free as possible, I recommend you publish everything to be used in the menu to the same folder. As you’ve seen, the wheel starts to come off of the cart if you publish to different sub-folders.
Kevin
I am working with menubuilder and the problem I am having is that even though I select “open in same window” for links, it continues to open the links in a new tab. Thus, I ended up with a whole bunch of tabs open.
Any suggestions?
I am working with menubuilder and the problem I am having is that even though I select “open in same window” for links, it continues to open the links in a new tab. Thus, I ended up with a whole bunch of tabs open.
Any suggestions?
I am working with menubuilder and the problem I am having is that even though I select “open in same window” for links, it continues to open the links in a new tab. Thus, I ended up with a whole bunch of tabs open.
Any suggestions?