Next: About this document ... Up: The MX architecture and Previous: Cinema-MX modules in use

#
Step by Step

1. Define a new identifier class. See for instance ``uk.ac.man.bioinf.apps.cinema.util.CinemaUtilityIdentifier``. Make sure that you get the class name of your module correct. I tend to group my identifiers into logical blocks, as loading identifiers for modules that you don't actually use, has a very low overhead.
2. Define a new module class. This can be very small. Take for instance ``uk.ac.man.bioinf.apps.cinema.utils.CinemaSlaveViewerModule`` . This module is used only by other modules. The ``uk.ac.man.bioinf.apps.cinema.utils.CinemaStatusInformation`` is a ``user-facing'' module, that is also very simple. It provides the ``cursor information'' in the status bar.
3. Write, or add to a ``main.xml''. This file should be placed in ``./cinema/config''. This directory should already exist if you have run Cinema-MX. This is a simple XML file with a top level tag of ``configuration''. The DTD can be found in the Cinema-MX source.
4. Load your identifier code. Listing 6 shows how to do this.
5. Actually load and start the module. Listing 7 shows how to do this.

And pretty much that should be it.

Next: About this document ... Up: The MX architecture and Previous: Cinema-MX modules in use