Welcome STEM Developers
- 1 Introduction
- 2 STEM Installation Instructions
- 3 Software Engineering
- 3.1 Coding Conventions and Guidelines
- 3.2 Source Code Control
- 3.3 Plans to move STEM to Open Source repository
- 3.4 Subversion Source Code Control System
- 3.5 Getting Access to the STEM Source Code Repository
- 3.6 Accessing the STEM Source Code Repository with Subclipse
- 3.7 Creating a project in the STEM Source Code Repository with Subclipse
- 3.8 Software Engineering Documentation To Do's
- 4 STEM subprojects
- 5 STEM Data
- 6 Other Information
This article is intended to be the starting point for developers working on the Spatio-Temporal Epidemiological Modeler Project (STEM) code base. It contains a detailed description of how the project is organized, how to find all of the resources associated with the project, and how to install, configure and use the necessary development environment.
One of the advantages of this document is that it gets newcomers “up and running” faster and it allows them to contribute to the project immediately by correcting any inaccuracies or omissions the document contains or by clarifying any descriptions. As a newcomer to the project you have a totally unique and extremely valuable perspective, if you can't find something or it doesn't make sense to you then you're probably not alone. When you find out the answer to your quandary, please record it here so those that come after you can “stand on your shoulders”. Welcome aboard!
The STEM code base is written in Java™ Version 5 and is organized as a set of well defined components using the eclipse (www.eclipse.org) plug-in tool framework. The components are integrated through a well defined “extension point” mechanism that makes the entire code base highly extensible. The use of the eclipse framework also provides for multi-platform portability.
Interestingly, eclipse is also the STEM project's Java™ development environment. If this seems a bit strange at first, don't worry, as you understand more about eclipse and the project this will make more sense. The project is organized and managed as an open source project. Much of the inspiration, philosophy and techniques for its management are taken directly from the book producing open source software by Karl Fogel (see the references later in this document).
Step-by-step for OHF STEM developers
- Read this article.
- When you find missing, confusing, erroneous information please contribute, by fixing the problem. This Wiki allows any registered user to update content. Please do!
- Visit the OHF project page. Bookmark it.
- Subscribe to the project mailing list. The mailing list is used for all internal developer communication. It is preferred to send private Emails.
- Install Java 5.0 and Eclipse 3.2]
- Obtain the source code for the STEM project from the CVS repository.
STEM Installation Instructions
Installing Java™ 5 JVM
STEM requires Java Version 1.5. IBMers should obtain the IBM version of Java 1.5. Others can use either IBM's Java 1.5 or the Sun Java 1.5 [].
For the IBM Java:
- Register with JIM, IBM's “Java™ Information Manager”
When you register you need to specify why you need access to Java™.
- When you receive authorization in the form of an email download the file (e.g., ibm-java2-sdk-50-win-i386)
- Run the installation program by double clicking on the file.
Installing the Eclipse Environment
Goto STEM Eclipse Setup
Installing/Running the STEM application
Running Stem as a standalone application If you want to first tryout STEM as an application then we provide a standalone version of STEM that only requires that you have Java 1.5 or higher installed.
You can get the file by going to the project page: and then clicking on "Files". Download stem0.1.0.zip (it is a very large file) and unzip it to your favorite directory.
This is a self-contained stand-alone version of STEM that is launched by double-clicking on the "STEM.exe" executable file in the root directory of the expanded archive. You'll need to have Java1.5 installed for it to run, but if you do and it's on the path, you should be greeted by the STEM "splash screen" while it starts up.
- Go to Windows->Preferences->STEM->Simulation Management and enable "Pause simulation after each cycle" and set the seconds to pause to 2.
- Open the Simulation perspective.
- Open the Map view with Window->Map to see the spread of the disease.
- Select the Spanish Flu Scenario under STEM Internal Data Test in the Scenario's view
- Select Stem->Run from the menubar or toolbar.
The Scenario only has the USA and Mexico at this time.
To run the Stem-GoogleEarth view:
- You must have installed GoogleEarth V4
- Select the GoogleEarth View. Window->Other->Stem->GoogleEarth View
- Select Window-Preferences->Stem->GoogleEarth and set:
- Check Method -> Direct Launch
- Check "Automatically process every simulation"
- Select the Spanish Flu Scenario under STEM Internal Data Test in the Scenario's view
- Select Stem->Run from the menubar or toolbar.
Coding Conventions and Guidelines
As with any product being built by a team, there are various areas where standards, conventions, and other guidelines can play a role in helping to ensure that the resulting product presents to developers and customers as a unified whole rather than as a loose collection of parts worked on by a variety of individuals each with their own styles and ways of working.
The STEM project will use the conventions and guidelines used by the Eclipse project. See the Eclipse Development Conventions and Guidelines.
The most important guidelines for STEM code are that it have good JavaDoc documentation and not generate compiler warnings.
The Eclipse compiler verifies the code against a preference list and will generate warning messages for code that does not follow rules specified in the compiler preferences. For example, it will check for "unchecked Generic type operations" and give a warning. We ask you removes all of the Eclipse compiler warnings before submitting the code. Also preferences for the following JavaDoc options should be changed to generate warnings and the warnings removed by fixing the code and/or creating accurate and informative Javadoc comments,
window->preferences->java->compiler->javadoc: Process Javadoc comments Malformed Javadoc Comments: warning Missing Javadoc tags(public) warning Missing Javadoc comments(Public) warning
If you are the owner or creater of a STEM subproject you can create more restrictive standards by checking in a set of project preferences. However, please do not remove warnings by checking in project preferences that ignore bad coding practices.
Each source file should include the following copyright statement. It should follow the package statement and proceed the import statements.
/******************************************************************************* * Copyright (c) 2006 IBM Corporation and others. * All rights reserved. This program and the accompanying materials * are made available under the terms of the Eclipse Public License v1.0 * which accompanies this distribution, and is available at * http://www.eclipse.org/legal/epl-v10.html * * Contributors: * IBM Corporation - initial API and implementation *******************************************************************************/
import ... ;
National Language Support
STEM supports languages other than English. The basic process is to provide properly named properties files that mirror the "native" English properties files. These files are grouped into a "plug-in fragment" which acts as an "add on" to a plug-in and adds the files of the fragment to the plug-in as if they were there originally. We separate them so that additional languages can be added without changing the original plug-in.
If a native file is named "messages.properties", then the corresponding file with Spanish translations for the messages would be named "messages_es.properties". It is also possible to provide translations that are specific to a particular country, for instance, for Canadian English, the corresponding file would be "messages_en_CA.properties". For Californian English it would be "messages_en_US_CA.properties". This follows the regular Java conventions.
To get us started, I've created one new plug-in fragment called "org.eclipse.ohf.stem.ui.nl1" which contains the properties files for the main UI component of STEM in the plug-in "org.ecliopse.ohf.stem.ui". Each of the other plug-ins with translatable strings will require their own (yet to be created) plug-in fragment. I also created properly named, untranslated, properties files for Californian English, Canadian English, Spanish, Hebrew, Tamil and Chinese in the new fragment.
To start STEM (Eclipse) in a language different from the working language of the operating system, you need to use the "-nl" command line parameter. For example, use "-nl en_US_CA" to start STEM in Californian English, or "-nl es" to start it in Spanish. You might find it useful to create a new launch configuration in Eclipse with the parameter specified. I have one for each language.
1) Use the "Run..." menu item to open the "Create, manage, and run configurations" dialogue. 2) Duplicate the Eclipse application you use to launch STEM and rename the new one to reflect the language (e.g., "STEM Californian") 3) Select the "Arguments" tab 4) In the "Program arguments" text box enter the command line parameter (E.g., "-nl en_US_CA" without the quotes, for Californian English). 5) Apply 6) Run
Open the Active Simulations View and you should see a different title than normal.
Here are some good resources for more detailed information:
"Building Commercial Quality Plug-ins", Clayberg,
"The Java Developer's Guide to ECLIPSE", D'Anjou, et al.
Source Code Control
<P>All of the files that constitute the STEM project are maintained in a “source code control” system. Anyone can obtain a copy of the files in the system, but only people designated as “contributors” are allowed to add new files or make other changes to the repository.
The only files that are in the repository are those that cannot be
derived from others. For instance, Java™ source files would be in the repository, but not Java™ class files.
Plans to move STEM to Open Source repository
Soon the STEM repository will be moved to the official Eclipse CVS repository and the following Subversion information will no longer apply.
Anyone will be able to checkout the STEM source code and data from the CVS repository as described later.
To submit to the Eclipse CVS repository you will need a Bugzilla account and be added to the list of committers.
Subversion Source Code Control System
The project uses the Subversion source code control system. This is an open source revision control system that is designed to be the successor to CVS. Subversion was conceived and implemented by developers who are intimately familiar with CVS and so was designed to be a superior replacement. It includes a number of features missing from CVS including atomic operations, full version support for folders and better performance (this is an incomplete list). Most new open source projects are selecting Subversion to manage their source code repositories.
While Subversion performs a similar function as CVS, it differs from the later in a very fundamental way. In CVS, each file has a version or revision number which changes as it is changed and checked-in to the repository. In Subversion, there is only one global revision number for the entire repository and each time any change (a “commit”) is made to the repository, this number is increment. Subversion is, in essence, a “versioning file system”. The concept is simple, any state of the file system since it came into existence can be recreated, all one needs is the “revision number”of the desired state and it can be “checked out” from the system. For instance, the state of the file system after the three hundred and thirty fourth change is represented by the revision number “r334” (the prefix “r” is required). Understanding this, it should be clear that from one revision to another, a file can be exactly the same even though “its” revision number is different. The key point to remember is that the revision number is not for the file, but for the repository.
For example, a newly created repository is at revision “r0”. If we add file “foo.java” and commit it to the repository, the revision number of the repository would become “r1”. If we add another file “bar.java” and commit it, the revision number of the repository will increase to “r2”.
Subversion also differs from CVS and other repository systems in the way it handles “branches” and “tags” of the repository. A branch is an alternative version of the repository usually used to do parallel development without affecting the main development path. A tag is basically a label attached to a version of the repository used to name some significant state such as a release. In CVS these concepts are specifically implemented and maintained by the system, in Subversion these concepts have no specific support. Instead they are implemented by creating new “sub-folders” in the repository and then copying the appropriate file system tree in the repository to the new sub-folder. On the surface this seems very strange and inefficient. The trick is that Subversion is implemented in such a way that copies are very fast and very efficient. When a file is copied in the repository nothing much changes except for a few bookkeeping entries.
By convention, but not enforced by the system, the root of a Subversion source code repository contains three top-level folders named “trunk”, “branches” and “tags”. The trunk folder holds the main copy of the code being developed. The branches folder contains sub-folders that define different branch copies of the contents of trunk. The tags folder contains sub-folders that each define different “tagged” copies of the contents of trunk. The names of the folders in both the branches and tags folders act as the labels of the corresponding “branch” and “tag”. Development occurs (i.e., files are committed) under trunk and branches, but not tags. The development efforts on the branches sub-folders should have a life-cycle that causes their contents to be merged back into the trunk (how to do that is another story) or abandoned, and then ultimately, regardless of their fate, deleted from the current revision of the repository. The tags folder should never be changed. It represents a labeled snapshot of the trunk.
<diagram of trunk/branches/tags here>
Getting Access to the STEM Source Code Repository
There are three ways to access the STEM source code repository, through the Subclipse eclipse plug-in, through the tortoiseSVN integrated windows shell tool, and through the command line using Subversion commands. Installation of Subclipse was described earlier in this document and we give specific instructions on how to use subclipse but you are free to use TortoiseSVN or the command line if you prefer.
Accessing the STEM Source Code Repository with Subclipse
These instructions assume that the Subclipse plug-in has been installed in eclipse.
- Select Window->Open Perspective->Other->SVN Repository Exploring
- In the “SVN Repository” perspective right click on the view to bring up the context menu and select “New→Repository Location”
- In the dialog there will be a box labeled “Url:”, enter https://svn.opensource.ibm.com/svn/stem/trunk This is the URL of the source code repositories “trunk”.
- In the “SVN Repository” view you will now have a list of all of the current projects. Select the ones you want (usually all) and from the "right click" select “Check Out...” This will get all of the projects into your eclipse workspace.
Accessing the STEM Source Code Repository with tortoiseSVN
TortoiseSVN is a Subversion client, implemented as a windows shell extension. One would download and install TortoiseSVN from the Tigis.org [] web site.
Accessing the STEM Source Code Repository with CVS
For use when STEM is on Eclipse.OHF
At the current time, both users and developers of STEM must access the code and data from the CVS repository in order to use the system. However all elements of the Eclipse STEM project is available for anonymous read-only access to the development CVS repository. Using anonymous access you can checkout the code and data to your local system. You can then use the system and if you wish modify it locally. However you can not use anonymous access to write it back to the repository. This is handy if you would like to fix a bug or add a feature. Get the code via anonymous access, do your work and then pass the work on to a committer (in a patch attached to a bug report) for inclusion in the repository. Committers love to have bugs fixed for them!
To use anonymous access from a running Eclipse platform, simply go to a Repository View and add a new CVS repository location. Use the following information to connect:
Expand the list from:
HEAD -> org.eclipse.ohf -> stem
- org.eclipse.ohf.stem. ...
Select all of the stem projects and checkout the projects to your Eclipse workspace (e.g. c:/stem)
The repository is also available for browsing here.
- Committer access to CVS
Developers with commit rights have individual user ids and passwords in the Eclipse project development repository. As a committer you can use SSH (Secure SHell) to connect to the CVS repository as follows. Go to a Repository View and add a new CVS repository location. When asked for the repository location enter the following:
|User||(your committer user id, supplied by the webmaster)|
|Password||(your committer password)|
Once your information is authenticated, you can browse the repository and add projects to your workspace. If you do some changes that you'd like to contribute, after testing and ensuring that you have followed the contribution guidelines, you are free to release your changes to the repository. Of course, you can only release changes to projects for which you have commit rights. The current list of committers for OHF can be found here.
Note that you can use the SSH protocol and your Eclipse user id to access projects for which you are not a committer but you will not be able to release changes.
More information about CVS usage with Eclipse is available here.
Creating a project in the STEM Source Code Repository with Subclipse
When you create a new Eclipse project you are going to want to be able to save it in the source code repository both so it can be backed up and so that you can share it with others. Basically you will create the project using eclipse and then initially store it as a "branch" in the Source Code Repository. You can invite others to access your branch when you get ready to have others try it. At some future point, it may be decided that this project should be migrated to the Source Code Trunk.
The process is as follows:
- Create the Eclipse project using the Eclipse wizards.
- "Right click" on the project name and select Tean->Share Project
- On the "Share Project with SVN" screen, select "create new repository location"
- On the "Enter Repository Location ..." screen in the "URL" field enter "https://svn.opensource.ibm.com/svn/stem/branches" and click "Next"
- On the "enter FolderName" screen, select "Use project name as folder name" and click "Finish"
If it complains about the name, that may be because someone has already created a project with that same name and you need to choose a different name. Question? Should there be a project name registry?
If you want to share your project with others, give them the name of the project and tell them to access the project using the Subclipse command to access it. For example, if you created a project "com.ibm.almaden.stem.dogflu" then they would do the following:
- Go to the SVN Repository perspective.
- If "https://svn.opensource.ibm.com/svn/stem/branches" is not listed then "right click" and select New->Repository Location
- Enter "https://svn.opensource.ibm.com/svn/stem/branches" as the URL
- If the required project is not listed, "right click"->refresh.
- Choose "com.ibm.almaden.stem.dogflu" and select "Checkout"
Software Engineering Documentation To Do's
Describe the basic development philosophy of the project and the basic ideas behind “agile” software development.
Explain how to build the system
Explain how to test the system
Explain how to submit a bug report
Explain how to use JUnit
STEM consist of a basic core system and (in the future) many projects that either use the basic system or enhance it. The following section describe the subprojects that use STEM or enhance it.
STEM - GoogleEarth Interface
STEM is a computer software system for defining and visualizing simulations of the geographical spread of contagious diseases. One way to visualize this geographical information is to overlay it on the GoogleEarth 3D world model.
The STEM-GoogleEarth project (STEM-GE) enables the logging of the spatial data with disease statistics included as it runs. Either simultaneously or after the fact, the logged data(in the form of KML files) is read by GoogleEarth and displayed by mapping disease state to color intensity.
To run the STEM-GoogleEarth Interface you need to do the following:
- Build the ge project
- Checkout the org.eclipse.ohf.stem.ui.ge project into Eclipse. (See earlier instructions)
- cd to the above ge project directory.
- Start STEM application
- Display the STEM-GE Window
- windows->open views->Other->Stem->GoogleEarth
There are numerous ways that you can use GoogleEarth with your simulations. We will not describe them all. The STEM-GE Preference Page is described below. That is where you specify many options that control what the STEM-GE interface does. The most common use of STEM-GE is to run a simulation and have it write KML files to a folder. Simultaneously GoogleEarth is reading these KML files via a webServer and displaying the results of the simulation on the GoogleEarth screen.
For example, if you have a predefined scenario that you want to run, then do the following:
To be completed
The STEM-GoogleEarth interface has a set of preference that control how the application works. This preference page is accessed by going to windows->preferences and selecting the GoogleEarth entry.
You will get the following window: File:GEPreferences.jpg
- Choose the Method used to display STEM Results
With this option, the KML files are written but not displayed by GoogleEarth.
With this option, the KML files are written and then displayed by GoogleEarth. GoogleEarth actually requests the file from a webserver Servlet whcih actually reads the file.
The KML is written on every cycle, overlaying the previous cycle. GoogleEarth asks for new data on a predetermined interval and is sent the current KML.
With this option, the KML files are directly sent to GoogleEarth. This can cause problems because GoogleEarth may get files sent at inopportune times but it is more efficient.
- Manual Launch
The map is generated by user selection of MapDisplay from the context menu (Right Click).
- Folder for KML Logging
This is the folder where STEM will write the KML files that GoogleEarth will read. If it already contains KML files, the user will be given the oportunity to delete them, keep them or choose a new folder.
- Hostname:port for external webserver:
This is the required hostname and port for an external webserver. Normally the internal webserver would be used so this is not needed but there are cases where one might want to use an existing web server.
- Use internal webserver
This is used to cause the webserver built into Eclipse to be used.
- Automatically startup GoogleEarth
If specified then when the STEM-GoogleEarth view is started, then the GoogleEarth application is also launched.
- Automatically log KML for every simulation
if specifid, then when you start any simulation running, it will automatically log files to GoogleEarth. Only the first one will be displayed by GE since it would be counterproductive to show 2 different views at the same time.
- Only write a KML file file every Nth cycle
If the simulation does not change rapidly from cycle to cycle, significant overhead can be saved by only sending data to GoogleEarth every Nth cycle.
- Chose the STEM Aspect to be displayed
The graphical display can only display one of the disease attributes at a time. Normally you would select one of S E I or R but Any would be specified when you are displaying an existing folder and you want whatever was logged to be displayed. All would be specified when you want all of the disease statistics to be logged. (4 files for each cycle).
- Allow debug output on Console
This is used for problem determination.
- Choose the Method used to display STEM Results
In Process documentation This section is in the very early stages of documentation. Please help complete it.
An important component of STEM is the large collection of data that it contains. This section will attempt to describe the different data that is available, where it is and how it is used.
Administration Level The administration level for geographic data refers to the "political resolution" of the data sets. The United Nations defines political divisions called "Administration Levels".
The highest level is "UN Administration Level 0" which corresponds to "countries". We have 244 such "countries", we get our definition of a country from the ISO-3166-1 codes, of which there are 244. There is a ISO-3166-1 code for the United States (a country), and one for Puerto Rico (not a country, but a slightly separate political division). For the United States the ISO-3166-1 2 character code is US and the ISO-3166-1 3 character code is USA.
The next level down is "UN Administration Level 1", which for the United States are the states and for Canada are the provinces and territories. Below that is "UN Administration Level 2" The definition of these areas varies from country to country which is why we use the "level" instead. Level 2 is the limit on our current data sets. In the future we could add higher resolutions. For instance, for a small country like Israel we might go to level 3 and use something like a census track as the location.
Latitude: Latitude gives the location of a place on Earth north or south of the Equator. Latitude is an angular measurement in degrees (marked with °) ranging from 0° at the Equator to 90° at the poles (90° N for the North Pole or 90° S for the South Pole). In Stem, latitudes north of the Equator are positive values and south of the equator are negative.
Longitude: Longitude describes the location of a place on Earth east or west of a north-south line called the Prime Meridian. Longitude is given as an angular measurement ranging from 0° at the Prime Meridian to +180° eastward and −180° westward. The Greenwich meridian is the universal prime meridian or zero point of longitude.
ISO3166 code ISO 3166 is a three-part geographic coding standard for coding the names of countries and dependent areas, and the principal subdivisions thereof. The official name is Codes for the representation of names of countries and their subdivisions.
- ISO 3166-1 codes for country and dependent area names.
- ISO 3166-1 alpha-2 two-letter country codes
- ISO 3166-1 alpha-3 three-letter country codes
- ISO 3166-1 numeric three-digit country codes
- ISO 3166-2 Codes for the representation of names of countries and their subdivisions -- Part 2: Country subdivision code - defines codes for the principal subdivisions of a country or dependent area.
A list of all the county (Administration 0) codes is here: http://www.davros.org/misc/iso3166.html
Data Location and Usage
STEM Projects that contain data The following STEM projects contain data files that are used in STEM. In most cases these projects also contains code that processes the data.
- Eclipse Project names
Contains the Latitude/Longitude data for the Administration areas.
Contains the properties files that describe all of the data in STEM.
No longer actively used and should be ignored.
Code and data used to prepare the properties files
Property files in org.eclipse.ohf.stem.internal.data The following property files are found in the following directory. NNN is the 3 character Country code and N is the administration level.
- resource/data/country/XXX/ There is a separate subdirectory for each country.
- XXX_N_area.properties This property file contains the area of the administration level in square kilometers. The Key is the key for the administration level ( level 0 = USA; Level 1 = US-CA; Level 2 = US-CA-06075
- XXX_N_human_2006_population.properties This property file contains the population of the administration level.
- XXX_N_node.properties This property file contains the full name of the administration area. >> we need an example of how to access it <<
- XXX_names.properties This property file contains a xref of both Level 1 and level 2 names.
- resource/data/relationship This contains the following subdirectories.
- commonborder See below.
- resource/data/decorator/disease This contains property files that describe existing diseases.
Spacial Data (Geographic Coordinates) that provides the latitude and longitude coordinates for the borders of the Administration areas.
Project: org.eclipse.ohf.stem.geography Path: resource/data/geo/country/XXX/ XXX_0_MAP.xml XXX_1_MAP.xml XXX_2_MAP.xml Example URI: platform:/plugin/org.eclipse.ohf.stem.geography/ resources/data/geo/country/USA/USA_2_MAP.xml
Key Format: For level 1 data, the key is the ISO3166-2 code. An ISO3166-2 code is composed as follows: Two letter country code followed by up to three alphanumeric characters for the level 1 administration. For level 2 data, the key is the ISO3166-2 code followed by up to six digits. The leftmost two digits indicate the level 1 container of a level 2 administration (i.e. California is a level 1 container for Orange County; a level 2 administration). The two digits were taken from a lexicographic sorting of all the level 1 administrations within a country. Similarly, the four leftmost digits indicate the level 2 administration. Again, these four digits are an index into the lexicographic sorting of all level 2 administrations within a level 1 administration.
Common Border Data that describes which Administration areas have common borders.
Project: org.eclipse.ohf.stem.internal.data Path: resource/data/relationship/commonborder/ XXX_2_XXX_2.properties Common Borders between admin areas within country XXX XXX_2_YYY_2.properties Common Borders between admin areas of country XXX to the admin areas of Country YYY where XXX and YYY have a common border. The property files will list the bordering admin level 2 areas. Example URI: platform:/plugin/org.eclipse.ohf.stem.internal.data/ resources/data/relationship/ commonborder/AFG_2_CHN_2.properties
Generated by: NeighborUtility.java Located in: org.eclipse.ohf.stem.internal.data
The following is a list of software that is useful to have while working on the STEM project.
IBM's Java™ 5 JDK
Eclipse Features and Plug-ins
|Subclipse||Subversion client||Subversion client|
|UMLet||UML class diagram drawing tool||http://homepage.mac.com/martin.auer/umlet|
|Metrics||Java™ code metrics computations||http://metrics.sourceforge.net|
|Merline Generator||GEF generator from EMF||http://sourceforge.net/projects/merlingenerator|
|EMF 2.2||Latest EMF downloads||http://download.eclipse.org/tools/emf/scripts/downloads.php|
Eclipse Modeling Framework Budinsky, F., et al, Addison-Wesley. 2003. ISBN 0131425420. This is THE book on the eclipse modeling framework (EMF). Note- a second edition is due out very soon, and is available for pre-order
Eclipse:Building Commercial-Quality Plug-Ins Clayberg, E., Rubel, D., Addison-Wesley, 2004. ISBN: 0321228472. Good reference, but starts out a bit too simply.
Eclipse Distilled Carlson, D., Addison-Wesley, 2005. ISBN 0321288157. A concise guide with advanced explanations of how to exploit the features of eclipse. Very useful for people who are already familiar with eclipse because it adds an extra layer of sophistication to the reader's bag-of-tricks.
Eclipse Cookbook Holzner, S., O'Reilly, 2004, ISBN 0-596-00710-8. Good “how to” guide to use eclipse, less for eclipse plug-in development itself.</P>  Eclipse Holzner, S., O'Reilly, 2004, ISBN 0-596-00641-1. Good starter for new eclipse users/developers.</P> "The Definitive Guide to SWT and JFace Harris, R., Warner, R., Apress, 2004, ISBN 1-509059-325-1.</P>
Producing Open Source Software Fogel, K., O'Reilly, 2005, ISBN 0-596-00759-0. This is a great book on how to manage software development in general not just open source. We're using it as a guide for this project.</I>
- The STEM II project main web site provides access to project documents, bug tracking, and a web interface to the source code repository
- The STEM SVN repository browser.
- The main web site of the eclipse project.
- A collection of eclipse plug-ins.
Transition to Eclipse OHF project
During the next month (Feb 2007) we will be moving STEM to be a sub project of the Eclipse Open Healthcare Framework
- Eclipse OHF website
- The following link will take you to the OHF page on the eclipse.org website.
- OHF WIKI
- The following is the OHF top Wiki page.
- OHF Mailing List
- Open Healthcare Framework Mailing list <firstname.lastname@example.org>
- The archives for ohf-dev mailing list is at:
- The Newsgroup for OHF is:
- To access the newsgroup you will need to go to the following page and request a userid and password. (Note: you apparently have no choice in the selection of either the userid or the password)
- Bug reporting
- Eclipse uses the Bugzilla system for reporting and processing Bug reports for the OHF project.
- The following page has a link for creation of a Bugzilla account.
- The bug reporting page is:
- The following page can be used to find bugs in OHf.
- Enter OHF as the PRODUCT