To be a SAVE-IDE Developer-A Developers Manual (short version)

If you have been granted write-permission to the SAVE-IDE repository, please read this document and 'The Complete Guideline for Developers'. The complete Guideline for Developers can be found at
<link to be announceed>
.

Installing the Environment For Development

NOTE: This software is still in pre-alpha state, and therefore this installation guide will be subject of major changes. This installation guide will give you a SAVE-IDE in Eclipse for both users and developers. In the future the user and developer installation guide will be separated and put into the user and developer manual respectively.

There are two ways to install the Eclipse (TM) framework and needed plugins. Either install a distribution that have pre-installed plugins that is needed for the SAVE-IDE, e.g., Acceleo Distribution. Or install a 'clean' Eclipse framework and add the plug-ins required. The former may lead to more installed features than neccesary.

Install SAVE-IDE for Eclipse

Update Existing Features

Note: By selecting the 'Automatically select mirrors' option the update chose the nearest update server, not necessarily the fastest. If you have selected the 'Automatically select mirrors' option previously it can be turned off in the 'Preferences' dialog. Chose the menu 'Window->preferences' and the option 'Install/Update' unselect the 'Automatically select mirrors' option.

Install New Features

You may chose to install other features from different update sites, for example, C/C++ Development Tools (CDT) from 'http://download.eclipse.org/tools/cdt/releases/callisto'.

Note: By selecting the 'Automatically select mirrors' option the update chose the nearest update server, not necessarily the fastest.

What features and plug-ins that are installed can be verified in the 'Help' menu. Chose 'About Eclipse SDK' and a dialog appears. Examine features and plug-in details by clicking the buttons 'Feature Details' and 'Plug-in Details'.

Build Your First SAVE-IDE Component-Based Model

  1. Create a new project
  2. Import an existing project
  3. To see the architectural view of the system
  4. To see a timed behavior
  5. To map and generate code for a timed behavior In this step the internal variables of a timed behavior is mapped with ports of a component and the code is generated.
  6. To generate code for the model
  7. To generate code for, and use UPPAAL PORT

Eclipse(TM) is a trademark of Eclipse Foundation INC.

Development Tools

While doing work in order to improve or implement new features into SAVE-IDE specific tools and/or additional plugins may be needed. In this section the tools and plug-ins to use is described for each module.

/trunk/save_ArchEdit/src/ide/:

/trunk/save_ArchEdit/src/repository/:

Internals of SAVE-IDE

Management of Source files

When beeing a part of a big software project it is important that some guidelines is followed for how to managing the source base after changes or adding new code. In SAVE-IDE project the source base resides in a repository at the address: svn co https://save-ide.svn.sourceforge.net/svnroot/save-ide save-ide. Before you start working with SAVE-IDE you ned tp get a local working base. For details on how to get the source base read thsi page, http://sourceforge.net/svn/?group_id=206364. Normally you check out a module frome the base codeline which is called trunk, browse the repository at http://save-ide.svn.sourceforge.net/viewvc/save-ide/trunk/.

Remember that you only have to check out the module that you will work on. For example, if you want to work on the module save_ArchEdit you must then add /trunk/save_ArchEdit to your command in order to not get the whole repository.

Checking out the Source Base From Subversion Repository

Commiting Source Files Into Subversion Repository

update or checkout do changes, if necessary change the version number according to the applicable guidelines, either general or code line specific. Do not forget to make appropriate changes to the documentation both in the code and the manuals. update create a CHANGELOG entry create a patch dos2unix on the patch file review the patch to ensure that it only contain the intended changes submit patch to tracker commit the changes to the repository, before clicking OK review which files that is comitted. If any unwanted files uncheck them.

Documentation

Source Code Documentation

User and Developer Manuals



SourceForge.net Logo