Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Created by: null on 17-08-2005 10:39:00 AM Audium provides either copy content into the different application (which is a folder for each application). 1. If many developers are working on a same module how to intergration these pieces of code together. 2. If application contain more module, how to develop the application and integrate between these modules
Subject: RE: integration the modules Replied by: Vance Vagell on 17-08-2005 02:57:52 PM Hi Mahesh,
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 I have included some 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.
[b:25d5b1d087]First the short answer:[/b:25d5b1d087]
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.
[b:25d5b1d087]Now the detailed explanation:[/b:25d5b1d087]
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 your development style requires that several developers work on the same page of an application, the process is slightly more complicated. If this is the case, please let me know and I will provide details on how this can be accomplished. Note, however, that one-developer-per-page is the cleanest solution.
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.
Regards, Vance
Subject: Using Audium Builder Replied by: null on 22-08-2005 10:21:03 AM I am using Audium Builder 3.3. Can you give detail how to integrate it in Builder.
Subject: RE: Using Audium Builder Replied by: Vance Vagell on 22-08-2005 04:03:21 PM Hi Mahesh,
The process of integrating the work of several developers is somewhat different in Audium 3.3, since Audium applications used to be saved as binary files. Additionally, since then, Audium has integrated with Eclipse allowing for easy use of standard versioning systems (as my previous response outlined). Please refer to this post for various suggestions on how to collaborate on Audium 3.3 applications.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: