Reference documents for Kepler developers.
Because Kepler is a collaborative project, adhering to consistent formatting and naming conventions is especially important. Please review the guidelines for information about best practices.
How to check out, build, and run the Kepler source code using the Eclipse Integrated Development Environment (IDE).
How to execute Kepler from the command line (with or without the GUI ("headless"))
Does your new Java actor source use only existing Ptolemy or Kepler classes? Compile and import the actor into Kepler with a few simple steps.
Did you write an actor that uses new Java classes? See this tutorial for information about how to add new classes to Kepler.
Instructions for adding commons logging to a Java class.
To access or configure one of Kepler's HSQL databases (containing provenance, or cache information), follow these instructions.
In Ptolemy II 7.0, the package dependencies are encoded in the makefiles. For more information, please see this page.
Are you creating a Kepler installer? Here's a handy checklist to peruse before deploying it.
A brief look at some useful aspects of the initialization process when Kepler starts up.
The 'event-state' module contains a framework for communicating gui state changes among Kepler modules.
How to update the set of Directors and Actors that are shipped with Kepler
Kepler uses Ptolemy II and Ptolemy II optionally includes third party packages. See below for a description of what files need to be updated to exclude a Ptolemy II third party package.
Information on the configuration of the cron job that periodically executes 'ant validate-ptolemy' to test and, if it works, change the revision of Ptolemy that Kepler runs against to the current Ptolemy trunk revision
Details about the Python Actor
The Eclipse Preferences Window with the Compiler Pane showing that the "Compiler compliance level" is set to 1.6
This doc explains how to create actor xml/documentation after a new actor is implemented.