I've never done it at the same time (had the presentation open on Captivate and in PowerPoint for editing), but I have gone back and forth at times. It may be because I have sometimes edited slides throught the Captivate interface, while other times doing the edit through PowerPoint.
#Adobe captivate 9 pros and cons update#
I have seen some messages within Captivate that prompt me to update my slides, but it is hard for me to figure why the message shows up and what prompts it. Regarding the 'live' connection to PowerPoint, that's something I've wondered about too. I wish the doc had a bit more information about the internals of what is happening between Captivate and Powerpoint so problems would be easier to debug. It does seem to thwart they whole idea of having the link feature. When I see something like that in the help, it makes me worry that they must have encountered some bugs in testing so they are trying to cover themselves. That the network drive restriction does not seem reasonable. The CP file will swell by the size of the PPT file. Whomever has the CP file also has the PPT file because it's copied to the innards of the CP file If you choose to take the Captivate file home with you to work on it, you will not be able to update or make edits to the PPT, because it's on the LAN Pat may change presos whenever s/he desires Then you could just update in Captivate to pull in Pat's changes. You, the Captivate developer would then need to be aware that Pat changed the preso. That way Pat can make all the changes that are needed at any given time. Pat is constantly making updates to the PPT presos. Pat likes the presos to be stored on the company server where everyone sees them on drive letter Y. Pat is responsible for ALL PPT presos in the company. Like Articulate Storyline 2, Adobe Captivate 9 provides dynamic PowerPoint importing options and is also compatible with the entire Adobe Creative Suite. Perhaps you have a Powerful Pointing guru named Pat. Adobe Captivate 9 is Adobes offering to the world of eLearning authoring tools and is billed as end-to-end design creation. We are encountering lots of funny behavior in Captivate and the source management system when we are editing slides, so we are thinking about moving to embedding instead.Īs I understand it, here's the difference. Now we are ending up with multiple versions and having to keep track of what Captivate is linked to and where the server copy is. When we check them in, it removes the local copy. We thought this would be an advantage because it allows us to edit the slides directly from Captivate, but in practice, it seems like it just makes things more complicated when we're making updates because our source management system wants to control these slides and move them around on the server. We have imported the slides from the local copy, and then used the linking feature in Captivate.
Now we have created numerous Captivate projects that make use of these slides. We have an internally built source management system that enables us to check-out PPTs from a server location, create a local copy, use custom templates for editing, then check the file back into the server. My group uses powerpoint extensively to build course notes.
0 kommentar(er)
