Best Practices for Publishing your Captivate Project

Come join RealEyes tomorrow for a session on publishing Captivate projects. We will be discussing each method of publishing, and the benefits and drawbacks of publishing that way. We will also cover some of the common things missed that can make a better experience for your viewers when accessing your project.
Come here to join us: http://cyourteam.com/realeyesconnect/ev … te-project
The session is from 11A-12P Mountain Time.

Ok, we finally have a version of this session to post up here.
Enjoy! http://cyourteam.com/realeyesconnect/ev … and-tricks

Similar Messages

Help Please!! Best Practices for building an NDS Project...

We are doing a Proof of Concept on using NDS to develop non-SAP Java applications. We are attempting to determine if we can replace our current Java development tools with NDS/WAS.
We are struggling with SAP's terminology and "plumbing" for setting up/defining Java projects. For example, what is and when do you define Tracks, Software Components, Development Components, etc. All of these terms are totally foreign to us and do not relate to our current Java environment (at least not that we can see). We are also struggling with how the DTR and activities tie in to those components.
If any one has defined best practices for setting up Java projects or has struggled with and overcome these same issues, please provide us with some guidance. This is a very frustrating and time-consuming issue for us.
Thank you!!

Hello Peggy,
this is my first post but I hope it helps you anyway.
To learn the SAP "language" I additionally used the a SAP Presentation regarding the SAP JDI.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/java development infrastructure real world use webinar.pdf
I think this one is quite useful as an addon to the other links for information you already got. Your name also indicates that your mother-tongue language is German. If so, the german version of the book (Java-Programming with the SAP WAS) is already available for purchase and really useful. Then, you can also use the information provided by the University of Potsdam. They have an introduction about how to setup a track in the SLD and then how to setup SCs.
http://epic.hpi.uni-potsdam.de/nwlab/SC+Track.html
Hope this helps...

Best Practices for Defining NDS Java Projects...

We are doing a Proof of Concept on using NDS to develop non-SAP Java applications. We are attempting to determine if we can replace our current Java development tools with NDS/WAS.
We are struggling with SAP's terminology and "plumbing" for setting up/defining Java projects. For example, what is and when do you define Tracks, Software Components, Development Components, etc. All of these terms are totally foreign to us and do not relate to our current Java environment (at least not that we can see). We are also struggling with how the DTR and activities tie in to those components.
If any one has defined best practices for setting up Java projects or has struggled with and overcome these same issues, please provide us with some guidance. This is a very frustrating and time-consuming issue for us.
Thank you!!

Hi Peggy,
In Component Model we divide software projects into small components.Components can use other components in well defined manner.
A development object is a part of a component that can be changed or developed in some way; it provides the component with a certain part of its functionality. A development object may be a Java class, a Web Dynpro view, a table definition, a JSP page, and so on. Development objects are always stored as sources in a repository.
A development component can be defined as a frame shared by a number of objects, which are part of the software.
Software components combine components (DCs) to larger units for delivery and deployment.
A track comprises configurations and runtime systems required for developing software component versions.It ensures stable states of deliverables used by subsequent tracks.
The Design Time Repository is for versioning source code management. Distributed development of software in teams. Transport and replication of sources.
You can also find lot of support in SDN for the above concepts with tutorials.
Refer this Link for a overview on Java development Infrastructure(JDI)
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/java/java development infrastructure jdi overview.pdf
To understand further
Working with Net Weaver Development Infrastructure :
http://help.sap.com/saphelp_nw04/helpdata/en/03/f6bc3d42f46c33e10000000a11405a/content.htm
In the above link you can find all the concepts clearly explained.You can also find the required tutorials for development.
Regards,
Vijith

Best Practices for File Organization/Project Explorer

So we are finally getting SCC at my organization to manage our LabVIEW development, and that is good!
Now, we are starting in on discussions about how we should organize our files on disk and how we should use the Project Explorer. When I started here about 3 years ago, I wasn't very familiar with the project explorer, so I read the article at http://zone.ni.com/devzone/cda/tut/p/id/7197. Two of the main things I took away from that article are:
1. Organize Files in a logical manner on disk. Whatever that is, it is not a flat file structure.
2. The top level VI should be separate from other source code. Preferably, it should reside in the application folder.
Push Back Against These Recommendations
Before I was hired, most, if not all LabVIEW development was done utilizing a flat file structure and the top level VI lived with the source code. Since we didn't have a proper SCC, each individual organized files as he saw fit. So I started using the Project Explorer (not even its use is totally accepted right now) and I began follow recommendations 1 and 2 above. I didn't always follow #1 very strictly, but I have been working towards it, and I have always followed #2 religiously.
Since we are starting these discussions on how we should organize files on disk I'm starting to get some push back to following these two recommendations.
The arguments I get in favor of using a flat file structure is that you always know where every file is; including the top-level VI. It is also argued that it is a lot of effort to organize and search for VIs when they all reside in different folders. I think the fear is that by getting "clever" and organizing our files in such a manner we'll make things complicated and we will somehow shoot ourselves in the foot.
The argument I get against separating the top level VI from the rest of the source code is that it:
(a) Won't be clear where it is (like it is buried within hundreds of VIs). However, it is argued, you can just put a "!" in front of the file name and then it is always the at top of the flat file structure.
(b) An extension of argument of (a) is that things either look or seem messy when VIs (including top level VI) don't live in a sub-folder and are just hanging out with the Project Explorer file.
(c) I think there may be some fear of breaking the VI by moving it and altering the dependencies for the VI.
Convincing Others its Good to Follow These Recommendations
So, if I want to follow NI's recommendations, I need to come up with reasons we should follow these recommendations. Also, I should state that I care about following these recommendations because its what NI recommends. They've been around the block a few times and I'm sure there are good reasons why these are best practices. However, I don't think I've given a very compelling case for why these recommendations should be followed.
So I'll tell you all what I think good reasons are for these recommendations and perhaps I can get some feedback or additional support? If I'm crazy for wanting to follow these recommendations maybe someone can point out why I'm crazy.
(a) Arguments for Following Both
I. I passed the CLAD a couple of weeks ago, and I have started studying for the CLD. Part of the CLD is following both of these recommendations (see page 6 of http://ftp.ni.com/evaluation/certification/cld/cld_exam_prep_guide_english.pdf). While this isn't a reason in and of itself, it suggests that if it important when being certified it is important in practice!
II. If we hire new developers that are familiar with LabVIEW, they will most likely be familiar with these recommendations, especially if they are certified. That will lead to increased productivity out of the door because they won't have to learn our special way of doing things.
(b) Arguments for Organized File Structure
I. Unused VIs are easier to identify and remove. Right now we never remove VIs because we don't know if they are used or not. This leads to a lot of VI bloat.
II. It is hard to know what a specific VIs function is in a flat file structure by looking at the name.
(c) Arguments for Separating Top Level VI from Source Code
I. Placing the top level VI is an intuitive place for this VI. As long as the top level VI is the only VI in the application folder there is no mistake it is the top level VI, especially once you open it. This makes it easy for new developers to find the top level VI. I'd argue it isn't very intuitive for new developers to know that a VI in the source code folder that is prefaced with a "!" is the top level VI.
Summary
So that is what I think so far. Is there anything else I am missing to support following those two recommendations or am I just being inflexible?
Thanks!

zenthoef,
As a CLA, I have struggled with file structure over the years. Here are my recommendations:
1. Put the top level VI and the project in the top-level folder. This makes it very clear where to begin.
2. Put the remaining user interface VIs in a separate folder. Again, it makes it very clear what the functionality of these VIs are.
3. If you are using object, put each object in a separate folder. Place the family of objects in one folder, with each object in a subfolder.
4. Keep the remaining VIs either in a single folder. This can contain a small number of subfolder if your project is large, but too many folders makes it hard to figure out where your VIs are. For example, you might have a DAQ subfolder, an Analysis subfolder, and a Report subfolder. But if you had a Test1 folder, a Test2 folder, and you had a VI that was used by both tests, where would it go? Keep it simple.
5. You inferred that it is hard to figure out what a VI does by its name. That implies that 1) you need better names, and 2) your VIs are too complicated. A VI should do a single function which can be adequately described by its name. That VI might be something like Analyze Data.vi, which would contain a bunch more subVIs (like Get 1st Harmonics.vi), but each VI would contain a single function. You wouldn't save the data to a report in the Analyze Data.vi, for example.
The most compelling reason for following these suggestions is that it is easier to figure out what the code is doing after you haven't looked at it for a while. Once you have an application that is working and bug free, you shouldn't have to touch the code until you want to add features. If that is even 6 months later, you will probably have forgotten how the code works. As a consultant, I have had to update other people's code, and just figuring how where to start can be a challenge.
Tom Brass
Certified LabVIEW Architect
Saint Bernard Engineering, Inc.
www.saintbernardengineering.com
Tom Brass
Certified LabVIEW Architect
Saint Bernard Engineering, Inc.
www.saintbernardengineering.com

What is the Best Practice for publishing Offline Root CA Cert and CRL to Active Directory?

Hi,
I've read and seen in a few labs different approaches to what is published in Active Directory for a Offline Root CA. I've seen just the Root Cert published to AD as well as the Root Cert and the Root CRL published to AD.
I can understand why the Root Cert is published to AD, but why would the Root CRL need to be published to AD, especially if my Offline Root CA just issues the Cert for my Subordinate Issuing CA? So looking for Best Practices here.
Thanks for your help! SdeDot

On Sun, 22 Feb 2015 18:44:25 +0000, Andrzej Kazmierczak wrote:
Best practice is to publish CRL to 2 alternative paths - LDAP for your internal users to access them on the first place and HTTP as an alternative option to LDAP and as the only option for your external users.
No, the current recommended best practice is to publish to a highly
available HTTP location first (and possibly the only CDP) that is available
both internally and externally. This covers Windows and non-Windows
devices, domain joined and non-domain joined devices and internal and
external devices as well as multi-forest scenarios with no trust between
forests.
Paul Adare - FIM CM MVP

Best practice for moving images between projects?

Hey all,
I have a project that has an album inside of it. I want to move the album, containing all of the photographs to a new project. If I drag the photos individually to the new project it moves them successfully although they now don't belong to an album in their new project. If I drag the album itself it moves the album and photographs but leaves the photos in the original project as well.
Does anyone have some best practice ideas for this scenario?
Thanks in advance for any help!

As you have discovered if the drop target is the project the images move projects. If the drop target is an album the images show up in the album but do not actually move anywhere. Moving albums does nothing to move masters. So...
Select all of the images in the album. Drag them to the new project and then drag the album to the new project. Simple enough.
RB

Best practices for publishing to Skillport/Skillsoft.

We are having a devil of a time getting our Captivate files to work. I've read the other forum posts on similar topics and we've done all the suggestions in them.
Here's the two scenarios:
1) We publish SCORM 1.2 files in Captivate (which work fine on SCORM Cloud and in Moodle), but the Run Time check fails when we try to publish in SkillPort Publisher
2) Since the SCORMs don't work, we publish regular .swfs and import them in Skillport's Dialogue Design, with the Self-Paced Learning (SPL) box checked in the TOC. However, when we play the .swfs and close them (the "Exit" button in the Captivate swf doesn't work, we have to exit out of the Dialogue player) and reopen them, the SPL isn't working and it starts at the beginning.
Skillport is of no help on this issue. Hard to believe that a big LMS and the most popular authoring program don't play together.

Hi,
If the same package uploads fine on Scorm Cloud and Moddle but gives error on Skillport, you can consult with their team about possible reasons, to investigate better, create a sample project (a couple of slide ) Configure it and upload it again and see if it goes through fine.
Also, verify under -- Quiz--Quiz Preferences-- Reporting -- LMS Customization Settings -- "Never Send Resume Data " should be [unchecked].
Also, download this template --http://blogs.adobe.com/captivate/2011/04/a-new-way-to-report-scores-to-the-lms-from-your-c aptivate-courses.html
and check if that works.
Thanks,
Anjaneai

What is Best Practice for Publishing and Subscribing to Multicast Video P2P

Please, could someone help with an issue I am having in developing a peer to peer video chatting application? My application uses multicast to publish and subscribe to video streams of NetGroup members. I'm listening for the NetGroup.Neighbor.Connect event, and I'm calling the following function:
protected function onPeerConnect(event:NetStatusEvent):void{
                var peerID:String = event.info.peerID;
                // create user vo here
                // user Value Object for incoming stream
                userVO = new User();
                userVO.peerID = peerID;
                netGroup.addNeighbor(peerID);
                receiveStream(userVO);
protected function receiveStream(userVO:User):void{
                // init netstream
                var stream:NetStream = new NetStream(nc,groupspec.groupspecWithAuthorizations());
                stream.receiveVideo(true);
                stream.addEventListener(NetStatusEvent.NET_STATUS,netStatus);
                // init panel
                // alter to use custom component instead
                var panel:Panel = new Panel();
                panel.id = "panel" + panel_seq;
                panel.title = "Panel" + panel_seq;
                panel.width=322;
                panel.height=281;
                panel.x = 50 * panel_seq + 200;
                panel.y = 25 * panel_seq + 200;
                var cpanelContent:Array = new Array();
                panel.controlBarContent=cpanelContent;
                panel.controlBarVisible=true;
                // init video
                var video:Video = new Video();
                video.width=320;
                video.height=240;
                video.attachNetStream(stream);
                stream.play("media");
                // init videoWrapper
                var videoWrapper:UIComponent = new UIComponent();
                videoWrapper.id = "wrapper" + panel_seq;
                videoWrapper.addChild(video);
                // add to display list
                addElement(panel);
                panel.addElement(videoWrapper);
                // drag and drop panel
                panel.addEventListener(MouseEvent.MOUSE_DOWN,function(event:MouseEvent):void{
                    panel.startDrag();
                    addElement(panel);
                panel.addEventListener(MouseEvent.MOUSE_UP,function(event:MouseEvent):void{
                    panel.stopDrag();
                panel_seq++;// used for unique panel id
                userVO.panel = panel;// reference to the panel
                userVO.stream = stream;
                userVO.video = video;
                peers.addItem(userVO);
I am confused on this:
var stream:NetStream = new NetStream(nc,groupspec.groupspecWithAuthorizations());
What should I pass as the second parameter to establish an incoming NetStream with the publishing peer? I've seen people put in the farID but I haven't figured out how to access it. What is the difference between event.info.peerID and event.info.neighbor? And since I'm multicasting to the group do I need to pass in the groupspec or the farID? I would love some clarification on this.
What is happening is this:
When I join the group, and there are two members in the group already, I'll get three panels with videos. However, duplicate video streams are being attached. When I inspect the peerStreams array I'm seeing a length of 0, so does that mean that no one is subscribing to my published netstream? If so, how do I specifically subscribe to each published stream in the group? Sometimes if I step through in debug mode, I get three separate camera feeds in their prospective panels, but if I run it will have duplicates. I thought at first that this was a referencing error because all of the NetGroup.Neighbor.Connect events where happening all at the same time and perhaps that is the reason for the duplicates?
My only other thought is that maybe I'm multicasting one guys stream to the whole group, but I'm getting varying results so I want to know what is the correct way to grab, in sequence, a NetGroup members' published netstream and be sure that all other members are subscribing to my NetStream as well?
Also, I am using Value Objects to keep track of who my group members are, is that data shared with the group or is it not accessible to all members?   or should I use another method of keeping track of my group members?
Please help! Thank you in advance!

it appears you posted an identical message in two threads. i've responded in the other thread:
http://forums.adobe.com/message/3701380#3701380

Best practices for organizing a large "project" with multiple programmers

should i put everyone in one application? should everyone get their own applcation? my understanding (limited) is the level of granularity for CVS is the application. sounds to me like multiple developers checking the same application in and out would be a disaster. if every developer has there own application what problems will i have deploying. how do i handle my configuration (navigation) diagram? any thoughts would be appreciated.

Have a read through these:
http://download.oracle.com/docs/html/B25947_01/team_productivity.htm#BABBEFFF
http://brendenanstey.blogspot.com/2006/11/tips-for-using-cvs-with-jdeveloper.html

Best Practice for BEX Query "PUBLISH to ROLE"?

Hello.
We are trying to determine the best practice for publishing BEX queries/views/workbooks to ROLEs.
To be clear of the process I am referring: from the BEX Query Designer, there is an option QUERY>PUBLISH>TO ROLE. This function updates the user menu of the selected security role with essentially a shortcut to the BEX query. It is also possible to save VIEWS/WORKBOOKS to a role from the BEX Analyzer menu. We have found ROLE menus to be a good way to organize BEX queries/views/workbooks for our users.
Our dilemma is whether to publish to the role in our DEV system and transport to PROD,... or if it is ok to publish to the role directly in the PROD system.
Publishing in DEV is not always possible, as we have objects in PROD that do not exist in DEV. For example, we allow power users to create queries directly in PROD. We also allow VIEWS and WORKBOOKS to be created directly in PROD. It would not be possible to publish types of objects in DEV.
Publishing in PROD eliminates the issues above, but causes concerns for our SECURITY team. We would be able to maintain these special roles directly in PROD.
Would appreciate any ideas, suggestions, examples of how others are handling this BEX publish-to-role process.
Thank you.
-Joel

Hi Joel,
Again as per the Best Practices.Nothing to be created in PRD,even if we create them in PRD for Power users its assumed as temprory and can be deleted at any time.
So if there are already deviations then you can go for deviations in this case as well but it wont be the Best Practice.Also in few cases we have workbooks created in PRD as they cud nt be created in DEV due to various reasons...in such cases we did not think of Best Practice ,we had a raised an OSS on this aswell.
In our Project,we have done everything in DEV and transported to PRD,in case there were any very Minor changes at query level we have done in PRD and immedialtely replicated the same in DEV so that they are in SYNC.
rgds
SVU

Best practice for putting together scenes in a Flash project?

Hi, I'm currently working on a flash project with the following characteristics:
using a PC
2048x1080 pixels
30 fps
One audio file that plays (once) continuously across the whole project
there are actions that relate to the audio, so the timing is important
at least 10 scenes
about 7 minutes long total
current intent is for it to be played in a modern theater as a surprise
What is the best practice for working on this project and then compiling it together?
Do it all in one project file?
Split the work into different project (xfl) files for each scene and then put it together when all the scenes are finalized?
Use one project file but create different "scenes" for each respective scene? I think this is the "classic" way (?).
Make the scenes "movie clips" and then insert them into the timeline with the audio as its own layer?
Other?
I'm currently working on it by having it all in one project file. But I've noticed that there's some lag (or it gets choppy) at certain parts during playback and the SWF history shows 3.1 MB with a yellow triangle with exclamation point symbol. Thanks in advance.

you would only do that if it makes your job easier. generally speaking, it would not.
when trying to sync sound and animation i think most authors find it easiest to use graphic symbols because you can see their animation when scrubbing the main timeline. with movieclips you only see their animation when testing.
however, if you're going to use actionscript to control some of your symbols, those symbols should be movieclips.

Query Best Practice for Reports

I am new to Apex and I am wondering what is the best practice for store your sql quries for reports. I am a believer of storing all sql behind pacakge functions or procedures. And it looks like the only options for report pages are to use a direct SQL query, or a function that returns a query as a string. Yes the function method counts as putting the code in Oracle but not really. It is still getting compiled and parsed on the Apex side. It would be nice if Apex could handle a cursor but I have read that it doesn't directly. You have to have a function that returns a cursor and then create a pipelined function that calls the cursor function. That is kind of silly. Is there some other way to do this?
Apex 4.2
Oracle 11.2.0.2
Thanks for any input.
Jeff

Hi Jeff,
I'm not necessarily a believer in packaging queries. I'm a little more pragmatic in that I believe it may make sense in environments where you have a client environment that just expects a result set that is then manipulated by the client for the purposes of presentation, pagination etc. Apex has a different architecture in that the client is purely an HTML presentation layer (browser) and the presentation, pagination etc is formulated in the database along with the data using the Oracle web toolkit, which is a set of internal packages that produce HTML. Note that handling and manipulating ref cursors inside PL/SQL is not a joy, they were mainly designed to be passed out to external clients. (Often to shield programmers who don't or won't even try to understand relational concepts)
This means that when you create a report based on a query, the Apex engine will manipulate that base query, depending on the display requirements and pagination requirements of your report, before it submits that query to the database for execution. To get an idea of how this manipulation occurs, you can run your report in debug mode and check the actual query that is submitted to the database. If the query is presented as an already executed ref cursor, then the Apex engine can't execute in the way that it does. As you have already found out, the only way of using packaged queries returning ref cursors is by the use of a pipelined function, so that the Apex engine can treat the result as a normal query.
This is the architecture of Apex, and I suspect that re-engineering the Apex engine to handle ref cursors natively, as opposed to using a pipelining trick, would be a considerable change. I hope this at least helps to explain why ref cursors and Apex don't mix. I personally don't see the purpose of having an abstraction layer of packaged queries below an abstraction layer of an API such as Apex. SQL is a perfectly good API.
Regards
Andre

Best Practice for Recording to HDD's.

I want some answers from some people who have been using Logic for a while and have experience in this topic. I have a 2010 MBP 13" with 1 Firewire 800 port, after looking for a cheap quality interface i purchased a Saffire Pro 14 which has a Firewire 6pin interface and i assume is Firewire 400mbps. The interface also doesn't have an extra Firewire port and the manual says not to "daisy-chain" becuase of latency and CPU spikes. Honestly i haven't noticed any problems with my HDD I/O in Logic, when i skip around it peaks but never any errors. I formatted an old 160GB Sata 1 drive and hooked it up over USB, i noticed that when i "skip" arround or w/e its called it doesn't peak (get red) anymore. I want to know peoples experience with Daisy chaining firewire devices, and using USB HDD's.
When i invest more money, would it be ok to stick with my interface for now and get a Glyph drive and daisy chain my interface on at the end? Should i stick with USB storage? Should i stick with internal 5400RPM drive? Should i upgrade it to a 7200RPM ( my original idea). In I.T. we call it best practices, whats the best practice for storing your audio/logic files on a Mac when running Logic.

Please don't just tell me Firewire is faster than USB.....I'm an I.T. Proffesional (wishing i went to school for recording ) I know how comptuers work, i build them and fix them all day. I want to know from peoples personal experience what they run and their suggestions. Thanks so much!

Best Practices for JMS Service Documentation

Our software consists of a variety of JMS producers and consumers used to transform and transmit business to business messages on a large scale.
The service nodes do a variety of things, and we've had trouble over the years ensuring every queue-based service clearly identifies the parameters and payload it accepts, so that everyone from programmers to system administrators can easily see what services are available and how they are to be used.
Some have advocated always adding a web service in front of each message-based service to guarantee interface contracts are all well publicized. I think there are reasons to choose web services and reasons to choose message-based services, and am not convinced this is the right answer to address limitations in expressing the design contract for a message-based service. That said, I really like what we've been able to do with self-documenting web services based on annotations, and wonder if there's a conceptual equivalent in message-based software.
What are your best practices for ensuring your message-based services are as self-documenting as your modern web service?
Thanks in advance for your advice!
Edited by: lsamaha on Apr 16, 2012 11:46 AM

*bump

Best practices for setting up projects

We recently adopted using Captivate for our WBT modules.
As a former Flash and Director user, I can say it’s
fast and does some great things. Doesn’t play so nice with
others on different occasions, but I’m learning. This forum
has been a great source for search and read on specific topics.
I’m trying to understand best practices for using this
product. We’ve had some problems with file size and
incorporating audio and video into our projects. Fortunately, the
forum has helped a lot with that. What I haven’t found a lot
of information on is good or better ways to set up individual
files, use multiple files and publish projects. We’ve decided
to go the route of putting standalones on our Intranet. My gut says
yuck, but for our situation I have yet to find a better way.
My question for discussion, then is: what are some best
practices for setting up individual files, using multiple files and
publishing projects? Any references or input on this would be
appreciated.

Hi,
Here are some of my suggestions:
1) Set up a style guide for all your standard slides. Eg.
Title slide, Index slide, chapter slide, end slide, screen capture,
non-screen capture, quizzes etc. This makes life a lot easier.
2) Create your own buttons and captions. The standard ones
are pretty ordinary, and it's hard to get a slick looking style
happening with the standard captions. They are pretty easy to
create (search for add print button to learn how to create
buttons). There should instructions on how to customise captions
somewhere on this forum. Customising means that you can also use
words, symbols, colours unique to your organisation.
3) Google elearning providers. Most use captivate and will
allow you to open samples or temporarily view selected modules.
This will give you great insight on what not to do and some good
ideas on what works well.
4) Timings: Using the above research, I got others to
complete the sample modules to get a feel for timings. The results
were clear, 10 mins good, 15 mins okay, 20 mins kind of okay, 30
mins bad, bad, bad. It's truly better to have a learner complete
2-3 short modules in 30 mins than one big monster. The other
benefit is that shorter files equal smaller size.
5) Narration: It's best to narrate each slide individually
(particularly for screen capture slides). You are more likely to
get it right on the first take, it's easier to edit and you don't
have to re-record the whole thing if you need to update it in
future. To get a slicker effect, use at least two voices: one male,
one female and use slightly different accents.
6) Screen capture slides: If you are recording filling out
long window based databse pages where the compulsory fields are
marked (eg. with a red asterisk) - you don't need to show how to
fill out every field. It's much easier for the learner (and you) to
show how to fill out the first few fields, then fade the screen
capture out, fade the end of the form in with the instructions on
what to do next. This will reduce your file size. In one of my
forms, this meant the removal of about 18 slides!
7) Auto captions: they are verbose (eg. 'Click on Print
Button' instead of 'Click Print'; 'Select the Print Preview item'
instead of 'Select Print Preview'). You have to edit them.
8) PC training syntax: Buttons and hyperlinks should normally
be 'click'; selections from drop down boxes or file lists are
normally 'select': Captivate sometimes mixes them up. Instructions
should always be written in the correct order: eg. Good: Click
'File', Select 'Print Preview'; Bad: Select 'Print Preview' from
the 'File Menu'. Button names, hyperlinks, selections are normally
written in bold
9) Instruction syntax: should always be written in an active
voice: eg. 'Click Options to open the printer menu' instead of
'When the Options button is clicked on, the printer menu will open'
10) Break all modules into chapters. Frame each chapter with
a chapter slide. It's also a good idea to show the Index page
before each chapter slide with a progress indicator (I use an
animated arrow to flash next to the name of the next chapter), I
use a start button rather a 'next' button for the start of each
chapter. You should always have a module overview with the purpose
of the course and a summary slide which states what was covered and
they have complete the module.
11) Put a transparent click button somewhere on each slide.
Set the properties of the click box to take the learner back to the
start of the current chapter by pressing F2. This allows them to
jump back to the start of their chapter at any time. You can also
do a similar thing on the index pages which jumps them to another
chapter.
12) Recording video capture: best to do it at normal speed
and be concious of where your mouse is. Minimise your clicks. Most
people (until they start working with captivate) are sloppy with
their mouse and you end up with lots of unnecessarily slides that
you have to delete out. The speed will default to how you recorded
it and this will reduce the amount of time you spend on changing
timings.
13) Captions: My rule of thumb is minimum of 4 seconds - and
longer depending on the amount of words. Eg. Click 'Print Preview'
is 4 seconds, a paragraph is longer. If you creating knowledge
based modules, make the timing long (eg. 2-3 minutes) and put in a
next button so that the learner can click when they are ready.
Also, narration means the slides will normally be slightly longer.
14) Be creative: Capitvate is desk bound. There are some
learners that just don't respond no matter how interactive
Captivate can be. Incorporate non-captivate and desk free
activities. Eg. As part of our OHS module, there is an activity
where the learner has to print off the floor plan, and then wander
around the floor marking on th emap key items such as: fire exits;
first aid kit, broom and mop cupboard, stationary cupboard, etc.
Good luck!

Best Practices for Publishing your Captivate Project

Similar Messages

Maybe you are looking for