| Knowledgebase Home | Contact |
 Search the Knowledgebase |
 Jump to ID |
 Browse by Category |
| How to use source control to manage an Audium application | ||||||||||||
| Categories: Audium Studio (3.4.x) | ||||||||||||
This article explains the general procedure for using a source control system to manage your Audium applications. This procedure allows multiple developers to work on a single Audium application. SYMPTOMS Developer would like to use source control to keep a revision history of an Audium application, and to incorporate work done by other developers. RESOLUTION Since Audium Studio sits on top of Eclipse, it can leverage the functionality that is included with Eclipse. One of these features is integration with existing source control systems, such as CVS. Below are instructions on how to use source control with an Audium Studio project, which will allow you to bring together the work of several different developers. Note that these instructions assume that you already have a source control system in place, and that you have configured Audium Studio (i.e. the Eclipse portion) to connect to it. First the short answer: If you have an existing source control system, you can use that to combine the work of several developers. It is easier if they do not work on the same page of the application at the same time. Now the detailed explanation: If you have multiple developers working on the same project, they can each work on a different part of the project simultaneously. However, it is highly recommended that only one person work on any given page of the application at any given time. If this guideline is followed, then only the page folders listed under the "pages" subfolder of the "callflow" folder should be checked in (i.e. not individual elements). For example, if a developer makes a change on page32, no one else should be working on page32 concurrently, and she can safely check-in the page32 folder when she is done. Others can then check-out the changes, close and reopen their callflow, and the changes will be reflected. If new pages need to be added to the callflow, they should be added by one individual. Because of this, we recommend that extra empty pages be added to a project, to allow for future growth without having to add pages later. To add a page, one person should follow these steps: - Disable the filter that blocks .callflow items from being displayed in the Navigator pane (click on the down-arrow icon on top of the pane, choose Filters, and then deselect .callflow). - A file named .callflow should now be listed as a child of the "pages" folder in the Navigator pane. - Add the new page(s) to the application and save it. - Check in the .callflow file. - All other developers should now check out the callflow folder (which includes the .callflow file, and the new page folder), and then close and reopen their callflow. The new pages should now be listed. Note that it is possible for multiple developers to concurrently add new pages to an application, but it will require the .callflow file to be merged. It is an XML file, and should not pose much difficulty. However, for simplicity, it is recommended that one person be in charge of adding pages (and that several extra pages be added to allow for growth), to avoid having to merge this file manually. |
Print this page
Post a comment
(1 vote)
| Visitor Comments |
| No visitor comments posted. Post a comment |
| Related Questions |
| Attachments |
| No attachments were found. |