Komo takes advantage of many of the advanced features of the Eclipse RCP platform, such as the help system, coolbar, preference pages. Many Komo components were included with the understanding that they would need to be edited by the application developer. The idea behind this is that it is easier to change a component than it is to create it from scratch. This can be particularly true of Eclipse, where development can be frustrated by documentation that I often found to be sparse and uneven.
The Komo program code is designed for easy adaptation and extensibility. Efforts were made to provide extensive documentation for the java and xml files, and attention was given to Java programming standards and Eclipse conventions. The oode is organized into three packages. The komo package includes the KomoPlugIn class, which is necessary for running the application and all of the classes that format and run the Komo interface. Datatools includes the classes that access the database. Preferences contains classes that control the preference store and preference pages.
Customizing Komo for a specific application will, of course, involve programming the application-specific features. This step is beyond the scope of this help item. In addition, customization requires a fairly simple and straightforward process of changing the following branding items.