Skip to main content
S
suginoya
Participant
May 27, 2010
Question

Piggybacking a project with too many slides

  • May 27, 2010
  • 1 reply
  • 982 views

Hi everyone

I've read before that if a project has too many slides that you can somehow piggyback one set of slides with another and another to make one fluid project. Is this the same function as teh aggregate function? Any help is great. Thanks

Dave

This topic has been closed for replies.

1 reply

RoboWizard
RoboWizard
Inspiring
May 27, 2010

Hi Dave

I think you may be referring to Daisy Chaining.

Aggregator does perform this function for you. However, it also adds a Table of Contents that you may not want.

Daisy Chaining is described at the link below.

Click here to view

Cheers... Rick

Helpful and Handy Links

Captivate Wish Form/Bug Reporting Form

Adobe Certified Captivate Training

SorcerStone Blog

Captivate eBooks

S
suginoyaAuthor
Participant
June 10, 2010

Hey Rick

Currently I am working on a module where I am taking a video on Captivate of each powerpoint slide and then taking a snap shot at the end.

Doing this does two things: a) Allows me to record Powerpoint with all of its preset animations and b) gives 2 slides per powerpoint slide (1 for the video and 1 for the snapshot). Because my Powerpoint presentation intitally has 105 slides, putting it into Captivate resulted in a total of 210 slides. Also, because Captivate cannot handle a project of this capacity in one 'project', I have to cut sections out into their own separate 'projects' and will link or daisy chain or aggregrate them together depending on which option is better.

In all of this, I want a table of contents option to be present on each slide so that if the user feels they are sufficient or tired of one section, they can always click on the table of contents or 'home' button to start from where they want to start. The problem with putting a table of contents is that the Captivate 4 version apparently does not allow or work with daisy chain projects, rather they work with aggregate projects (which I am still figuring out what this means). One nice option with the table of contents is that it allows users a 'search' option and a resume function so if a user accidentally clicks on 'home' they can resume back to where they were previously. However, the table of contents may look different from the powerpoint presentation. What I propose to do now, is to have my own table of contents based off of the powerpoint presentation as one separate project and to have all of my other projects linked to this table of contents because I have access to daisy chaining other projects. Is this a doable workaround or does the aggregate option sound better? Is there something else that I am missing or can do in regards to my issue with the table of contents? Let me know if you need further clarification on anything I mentioned. Thanks in advance!

Dave

J
jamesnotjim
Inspiring
June 15, 2010

This Table of Contents (TOC) vs Aggregator issue confuses people. Here's the difference:

1) TOC: Every Cp project gives you the option of including a table of contents via Project, Table of Contents, which launches the Skin Editor. You then check the SHow TOC box on the TOC tab and make whatever other customizations you want.

2) Aggregator: This is a separate application, included with Cp4, which allows you to combine the SWF output from separate Cp4 projects and define a TOC for them. If your projects already have a TOC defined (via method #1, above), this TOC will be included in the Aggregator-generated TOC as a folder. The Aggregator TOC has the disadvantage that it is always open. It lacks the overlay mode which the individual project TOC contains.

I prefer using Aggregator to create TOCs, as this forces/allows me to create a separate Cp4 project file for each discrete unit of a training. Doing this has a number of advantages:

1) It allows for easier collaboration between developers (e.g. "You take topics #1, #2, and #7. I'll take #4, #5, and #8).

2) It allows for reuse of certain components (i.e. once you've shot the "logging in" vid for an app, you can use it in as many projects as you like).

3) It reduces the scope of damage if a Cp production file become corrupted.

4) It helps avoid some known issues with Cp4 projects that are in the 50 slide range.

5) It creates a group of small SWFs, rather than one large one. This has a positive effect on load times. It also works around file-size limitations on certain storage systems. And it saves bandwidth in general. On the down side, it will increase hard drive consumption on your production machine, as you'll have multiple Cp production files, and each of these, even if it only contains a few slides, eats up a lot of space.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices