Skip to main content
B
baba2012
Participant
October 19, 2011
Question

adobe captivate command line options (publish swf on command line)

Hi,

I am new to Adobe Captivate and I'd like to know if there's a way to publish my .cp project to SWF without going through the IDE.

Is there a command line way of running Captivate so I can quickly convert or publish my .cp project to .SWF files?

Thanks,

Baba

    Ce sujet a été fermé aux réponses.

    2 commentaires

    B
    baba2012Auteur
    Participant
    October 19, 2011

    What is Aggregator? will it help with automating publishing .CP (adobe captivate) projects?

    Captiv8r
    Captiv8r
    Legend
    October 19, 2011

    Hello again

    I'm puzzled why Lilybiri suggested aggregator. Hopefully she will clarify.

    Personally, I'm doubtful aggregator would be of any help here. Basically an Aggregator project allows you to point at several SWFs and present them to the end user as if they are a single project or SWF. The end user is none the wiser that they are working with a collection of SWFs. But the SWFs must already be compiled, which is why I'm confused as to the mention of Aggregator.

    Cheers... Rick

    Helpful and Handy Links

    Captivate Wish Form/Bug Reporting Form

    Adobe Certified Captivate Training

    SorcerStone Blog

    Captivate eBooks

    RodWard
    Community Expert
    RodWardCommunity Expert
    Community Expert
    June 20, 2019

    Hi, thanks for the replies!

    We are indeed publishing to HTML5, but the question about automation stands.

    Our content is spread over 55 Captivate projects, each translated into 6 languages, and each published to two different formats. As the number of projects grows, publishing them via the main Captivate app becomes a bottleneck. If we decided to change our themes and needed to re-publish all our content, we'd have to go through the clicks to change settings and publish 660 (55 x 6 x 2) times.

    Any thoughts on how I might be able to achieve this more efficiently?

    Some concrete example scenarios:

    1) I want to publish the same content as HTML5 with SCORM and as HTML5 with xAPI. This would be much easier if I was able to write a script which invokes "Captivate Publish" against all my projects with the two different sets of configuration.

    2) I'd like to give my content creators the ability to commit their project (.cptx) files and assets to source control and have the publish process run nightly.

    Any help or suggestions are appreciated!


    Assuming there are no components or aspects of your projects that are incompatible with HTML5, the difference between publishing to SWF or to HTML5 is simply a matter of which option the developer selects in the publishing dialog.

    However, if you are hoping to just open older CPTX files that were originally published to SWF and now publish out as HTML5 instead then you are in for some surprises. Depending on how old the projects are, you may have almost no re-work all the way up to a complete redesign/rebuild being more practical.

    However, even if these are current projects that would work equally well in either output, your problem is going to be that Adobe has never provided any other way of triggering the publishing other than from within an instance of Captivate.  So whether it was a human operator or an AI algorithm selecting each project file and going through the motions of selecting all the publishing options, there's still going to be a requirement to have at least one or more instances of Captivate open to do the work.  It may be possible to automate, but in the 12 or more years I've been using Captivate I've never seen any of this done via a command line.

    Captiv8r
    Captiv8r
    Legend
    October 19, 2011

    Welcome to our community

    I'm unsure there is a way to accomplish that. But I would ask why in the world that would be important? I can't think of any situation where changes would occur outside of the Captivate application where such a thing would be useful. Generally, you compile the SWF as the last step and that's that. It's simply used from there forward.

    Can you describe a workflow where it would make sense to compile without opening Captivate? I'd really like to understand it.

    Cheers... Rick

    Helpful and Handy Links

    Captivate Wish Form/Bug Reporting Form

    Adobe Certified Captivate Training

    SorcerStone Blog

    Captivate eBooks

    B
    baba2012Auteur
    Participant
    October 19, 2011

    Hi Rick,

    I am interested in a command-line version of Captivate because I have multiple CP projects but I want to add the creation of the SWF files as part of an automated nightly build and have them stored in a staging folder (rather than having version control for both the CP files and the SWF files).

    If there is no command line, is there maybe a way to publish multiple CP projects at once? I just don't want to have to manually open, publish, close, and then reopen one CP project after another as I have about 100 projects...

    Thanks

    B

    Lilybiri
    Lilybiri
    Legend
    October 19, 2011

    Do you know the Aggregator?

    Lilybiri

    Conditions d'utilisationAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices