Setting up Version Management (Git, SVN) for Captivate Projects

I'm guessing the answer is No, but I thought I would ask:
Is there any way to set up some kind of Version Management/Source Code management for a Captivate project?
Currently, I just have a bunch of nearly identical cptx files with some kind of naming convention so that I can tell which one is which. If I need to revert something, I have to hope that I made a "Save As" at the right point in time. If I need to work with a colleague, there is no straight-forward way to review the changes that she made.
Adobe Captivate is basically a speciallized IDE with some additional graphical stuff. Having some kind of version control tool, especially if it were Git, would be very helpful both for my personal productivity as well as for managing collaboration with my colleagues.

So far the only WOW version control i have found is AlienBrain but i have a better chance of being struck by lightning on a clear summer day than ever owning it.
http://www.alienbrain.com/features
A promising solution is Razuna http://razuna.org/whatisrazuna but I havent "project tested" it yet to see how well it will work while developing in a team enviroment. 
Something i doubt i will ever find is a solution to "show the difference" in a file similar to how WinMerge http://winmerge.org/ shows the difference in files or compairison of folder directories.
It would be nice to be able to compare two (or more) captivate files slide by slide with syncronised scrolling to note differences.
Seems like most people are pretty quiet about what they use for version management.

Similar Messages

  • Poll: Which LabVIEW version do you use for new projects?

    I have posted a poll on the LAVA forums, here:
    Poll: Which LabVIEW version do you use for new projects?
    Thank you for taking the time to tell us your thoughts.

    I'm giving this thread a bump to remind eveyone that we want to know your opinion.  Please vote in our poll.
    Thanks,

  • Comparing version management after import for structures

    Hi,
    I am having issues with transports on ECC 6.40 for table structures. I went to Utilities, Version, Version management, Remote comparison with QAS, and clicked on Delta display, I see that it saids 'Unchanged'. Would this mean that nothing got transported or impotred to QAS?
    Is it correct that SAP structures are  not transportable? I am actually enhancing SAP standard structures and fields through using a SAP provided standard report.
    Would I have to run this report on the target system QAS and eventually PRD to add the SAP fields to the structures? Woudd that also mean that I would have to ask Basis to open the system, run the report, and close it?
    Thanks
    null

    Hi Padmanabha,
    in addition, you should replicate the datasource 8<source cube> and reactivate the transfer rules using RS_TRANSTRU_ACTIVATE_ALL.
    Hope it helps,
    regards
    Siggi

  • Free hosting for Captivate projects

    I am a student in instructional design and I want to create an online portfolio to showcase some of my e-learning modules. Does anyone know of a free hosting service where I can upload Captivate project (HTML or SWF)?
    thanks

    You can try to use Scorm Cloud where you can upload published zipped output from Captivate, In order to do that you have to enable the reporting of your module within Captivate.
    Visit the link to create your account for free -   SCORM Cloud
    Click on sign up and create your account. Maximum upload size may be around 100 mb.
    techPreceptor

  • Managing a set of documents that require approval, for each project stage

    Good day to all,
    I am new to SharePoint but I have dived in head first due to my job.
    The users I am dealing with need a solution where they can upload a specific set of named document types (example: project charter, site plan, schedule, costing approval, designs) but all documents will be scanned to PDF before being uploaded. Every stage
    will have its own set of documents with the same named document types. Each document has to be checked and the approved.
    I know I can use a workflow for the check and approve part.
    What I don't know is how to create a "blank" document set for uploading PDF files. In other words, I envisioned that I would have a document set of sorts where I can enter common information such as the Project Number, and the Project stage, and
    then I would have multiple upload fields that are named by the types above (project charter, site plan, etc.) so that the users will know exactly what documents are needed to complete the document set.
    Can anyone assist me in find a solution?
    Thanks and best regards.

    Hello,
    One thing to note is that the document set content type in SharePoint is analogous to a folder; you don't specify upload fields on the document set, but users can upload any number of documents to the set once it is created. You can have fields of information
    on the document set, and different fields of information on the documents within the set.
    With that in mind, the best way to accomplish what you're looking for may be to have columns on the document set that indicate which required documents have been uploaded.
    Document Set content type columns:
    Project Number (text)
    Project Stage (choice)
    Project Charter Complete (yes/no)
    Site Plan Complete (yes/no)
    Schedule Complete (yes/no)
    Costing Approval Complete (yes/no)
    Designs Complete(yes/no)
    Document content type columns:
    Document type (choice)
    It can either be a manual step so that when a user uploads a document, they then mark the corresponding yes/no checkbox, or it could be automated with a workflow.

  • Steps for configuration of version management

    Dear Experts,
    Kindly tell me what is meant by version management and under which situation this will be used and how its impact in MM after configuring this. Kindly let me know the configuration steps for version management.
    Regards,
    Prasath

    You make the settings here for activating the version management:
    SPRO --> MM --> Purchasing --> Version management --> Set up version management for PR -->here make the settings and tick on the activate indicator...
    Now define the relevent fields which shd go under version change:
    SPRO --> MM --> Purchasing --> Version management --> Version relevent fields of PR's
    If you wanna set up change displays and its output, then make settings here:
    SPRO --> MM --> Purchasing --> Version management --> Set up change displays...
    NOTE: You can only release this PR fully if you tick the version completed indicator in the PR document...
    Similrly you can activate for Purchase order
    spro-mm-purchasing-version management-purchase order

  • Version management tool for Eclipse Juno / fiori apps

    HI All,
        We have working with fiori apps. We are using Eclipse Juno. I was wondering what would be the best tool for version management.
    THanks for your suggestions,
    Gopi

    Hi Gopi,
    yeah, that's right. When your eclipse recognize a git repository, you can't use the share-functionality of the Team-Provider plugin. But there's a little trick to use it, even if you have a git repo.
    Just right-click on your git-project in eclipse, go to "Team" and click on "Disconnect". After that, you can share your project via Team-Provider plugin. The problem with this approach is, that you always have to work with the console or git-bash, when you want to execute git-task.
    Sry, i have no experience with NWDI. The only thing i can say is, that it should be no problem to work with multiple people on a project based on git. You can work with a central repo or with a decentralized (beacuse git is a distributed version control system).
    Regards
    Michael

  • Purchase order item text version management is not creating.

    Dear sap professionals,
    I have an issue in item text as per customer need I created item text type as drawing number, the problem is when ever an user change drawing number review in text area system should create new version number,  but in present case instead of creating new version number the data is updating in existed version number.
    Same time I am not able to trace field name and table used for this specific drawing number type, do I need to do any new configuration for that or I missed any  thing in this process.
    Did any one experienced same issue?
    With Regards,
    Ranganath

    ranganath.kakarla wrote:
    Dear sap professionals,
    >
    > I have an issue in item text as per customer need I created item text type as drawing number, the problem is when ever an user change drawing number review in text area system should create new version number,  but in present case instead of creating new version number the data is updating in existed version number.
    > Same time I am not able to trace field name and table used for this specific drawing number type, do I need to do any new configuration for that or I missed any  thing in this process.
    > Did any one experienced same issue?
    >
    > With Regards,
    > Ranganath
    Hi,
    path:mm-purchasing-version management-Set Up Version Management for External Purchasing Documents
    Doc.cat will be F means po, Doc type will be NB & p.org of ur client
    in control data active both version acrive & version 0 ok.
    in field selection reason, shorttext& requestor is required option & save
    give the reason for ur inputs
    in Set Up Change Displays category willbe f for all doc types
    Regards
    Raj.

  • Version management in PR

    Dear All SAP Gurus,
    I have done the SPRO settings for PR version management but when i want change PR ,system is not asking for version management means not asking for required entry field eg reason for change.
    Please suggest me how to configure pr version management.
    Thanks in advance and Regards
    Mahesh

    Hi,
    In Set Up Version Management for Purchase Requisitions : Document Type --
    In field Selection make Required , Optional or Supress Field as per your requirement for
    Reason
    Short Text
    Requester
    External Numbe
    Posting Date
    Secondly version Management will active after taking Printout of PR.
    In Version-Relevant Fields of Purchase Requisitions enter following :
    Type Table  Field name
    NB   EBAN   ADRNR
    NB   EBAN   BESWK
    NB   EBAN   BSART
    NB   EBAN   EINDT
    NB   EBAN   EKGRP
    NB   EBAN   EKORG
    NB   EBAN   EMATN
    NB   EBAN   FLIEF
    NB   EBAN   KNTTP
    NB   EBAN   LFDAT
    NB   EBAN   LGORT
    NB   EBAN   LOEKZ
    NB   EBAN   LPEIN
    NB   EBAN   MATKL
    NB   EBAN   MATNR
    NB   EBAN   MEINS
    NB   EBAN   MENGE
    NB   EBAN   PEINH
    NB   EBAN   PREIS
    NB   EBAN   RESWK
    NB   EBAN   TXZ01
    NB   EBAN   WAERS
    NB   EBAN   WERKS
    NB   EBKN   ABLAD
    NB   EBKN   KOSTL
    NB   TEXTID B01
    Rgds,
    Vikaa
    Edited by: Vikas Mayekar on Nov 11, 2008 7:07 AM

  • Version Management error

    Dear Gurus,
                          Am havng a problem in version Management. After creating a P.O and saving it I need to make changes in it. I am changing the quantity and before saving the P.O i want to enter the reason for change. The red flag on top of status tab is not coming and it is not allowing me to enter the reason for change. Kindly guide me how to fix this prblm...Thankyou...

    Hello,
    New version will only be triggered, once you completely release the PO, output the PO and then do any changes with print relevant fields.
    For maintaining reason for change in version, you can follow Customizing --> Purchasing --> Version Management  --> Set Up Version Management for External Purchasing Documents, and make the field mandatory.
    Hope this helps.
    Thanks & Regards,
    Mihir Popat

  • Fields triggering Version management in POs

    I see in the following path in SPRO
    MM-> Purchasing ->Version Management -> Set up version management for external purchasing document:
    Version Management is active for doc cat 'F ' , doc type EC , and Purchasing Org FR01. But still when I changed the price of a PO (type EC and pur org FR01 ) and set the delivery indicator in the PO , the version management was not triggered.
    What is the reason for this? Is it that VM will be triggered only for a specific fields in the PO?Where are these fields set?
    I have seen in the same path there is an option "Version-relevant Fields of Purchase Requisitions" , but there is nothing for PO

    hi,
    Check your settings properly...
    You can't set the fields for the PO as you do for PR...
    The whole document will be taken in to consideration for version change and if setttings done properly
    then the version compleated indicator must be set before releasing the PO and then check...
    Regards
    Priyanka.P

  • Version Management Table values

    Dear Friends,
    Following are the requirements of client to make the Purchase Order Version active.
    Price Change
    Qty Change
    Change in Material Code
    Change in Material Description
    Header Text Change
    Pl let me know whether all the 5 requirements are possible for PO and also help me to find out the table and field names of the 5 above requirements.
    Regards,
    ASK

    hello,
    did you activated the version management in the system. if not activate it through the following menu path,
    spro>material management>purchasing>version management> Set Up Version Management for External Purchasing Documents
    check the box against your P.org.
    once you activate it., create a po with that p.org and try changing that po through me22n. a version tab will appear in header details. make any required changes in po and save it. now go to the versions tab, select the version line and click on the "display changes" button. you'l get a detailed changes list that you have made in the po.
    hope this helps,
    regards,
    vamshi

  • Version management(Purchasing)

    Hi All,
             please clarify the Use of version management,what&why and when it is required?
             please explain briefly process....like
             set up version management for
            1. PR's and Externanal Purchase documents
            2. define reasons for change,what are the reasons
            3.  set up change displays
            4.  version relevent fields of  PR's, why not for Purchase orders
       thanks in advance
    Thanks&regards
    Venkate

    Hi,
    SPRO > MM > Purchasing > Version Management
    - Set Up Version Management for Purchase Requisitions
    In this step, you set up the Version Management facility for purchase requisitions.
    For a combination of document category and document type, you can:
    Activate Version Management: - If Version Management is active, the changes made to a purchasing document are managed in versions.
    Set up field selection for versions: - For certain fields of the version, you can specify which properties they are to to have: mandatory entry, optional entry, display only, suppressed.
    Note: - When a purchase requisition is created externally (e.g. via a BAPI), the system does not check whether these fields have been designated as mandatory-entry fields.
    - Set Up Version Management for External Purchasing Documents
    In this step, you set up the version management facility for external purchasing documents.
    For a combination of purchasing organization, document category, and document type, you can:
    Activate version management: - If version management is active, changes to a purchasing document are managed in versions.
    Define field selection for versions: - You can specify the attributes certain fields of the version are to have: mandatory entry, optional entry, display only, field suppressed.
    - Define Reasons for Change
    In this step, you can define the reasons for changes to requisitions and external purchasing documents (e.g. increase in material requirement).
    - Set Up Change Displays
    In this workstep, you can specify whether and in which change displays (e.g. for version via @II@) a certain field is to be displayed.
    - Version-Relevant Fields of Purchase Requisitions
    In this step you can specify whether changes to a field are version-relevant. ("Version-relevant" means that a change to a field causes a new version to be created.)

  • Note 533276 - Setting the batch management requirement indicator

    Hi;
    we have found an oss note for setting the batch management requirement
    indicator.. but the program mentioned in oss note does't exist in the
    attachement part.. we urgently need your help..
    how can we find program RVBCONVMAT2BM?
    Note 533276 - Setting the batch management requirement indicator
    Solution
    Here, the standard procedure is to clear stocks of the current and the previous period as well as to complete the open documents. Note 30656 provides further information about this.
    Alternatively, in the case of a large data or document volume, you can use a conversion report from the batch development that sets the batch management requirement indicator without the necessity of manual preliminary works such as the posting of the stocks or the completion of open documents.
    We have developed the main features of this report, but it must be adjusted to individual business processes in a customer project that is subject to charges.
    If you require further information about functions of this tool or about running such a customer project, you can send an e-mail to the consulting department ([email protected]).

    Hi,
    You also need to check for open sales order, open production orders, open WM transfer orders and open deliveries. These documents needs to be closed/completed.
    Check OSS notes 533276 - Setting the batch management requirement indicator.
    Following is the details of this notes;
    Summary
    Symptom
    The attempt to set the batch management requirement indicator for a
    material in the material master record maintenance fails because there are
    stocks or documents that are not completed such as production orders, sales
    orders, deliveries or WM transfer orders.
    More Terms
    MARA-XCHPF, MARC-XCHPF, RVBCONVMAT2BM
    Cause and Prerequisites
    Solution
    Here, the standard procedure is to clear stocks of the current and the
    previous period as well as to complete the open documents. Note 30656
    provides further information about this.
    Alternatively, in the case of a large data or document volume, you can use
    a conversion report from the batch development that sets the batch
    management requirement indicator without the necessity of manual
    preliminary works such as the posting of the stocks or the completion of
    open documents.
    We have developed the main features of this report, but it must be adjusted
    to individual business processes in a customer project that is subject to
    charges.
    If you require further information about functions of this tool or about
    running such a customer project, you can send an e-mail to the consulting
    department (BMToolsatsap.com).
    Regards,

  • What all is placed under version management?

    If I check a JDeveloper project into SCM what all is placed under version management?
    Is only the project placed under version management?
    Is each of the project components placed under version management?
    Are both the project and all the project components placed under version management?
    Thanks,
    Phil S.

    Hi Philip,
    When you invoke Add... (or Check In, Check Out, Undo Checkout), a dialog will appear that confirms the files the operation will apply to.
    For a project, usually, the operation will apply to the project itself (the .jpr file), and all the files in the project. You can exclude any files that you don't want to be added using the Remove button in the confirmation dialog.
    Thanks,
    Brian
    JDev Team

Maybe you are looking for