Ticket #74 (closed task: wontfix)

Because of the template engine described in ticket #72, Notes will be quite modular, able to be deployed in a variety of situations. For example, Notes could be run side-by-side with any acquisition software during acquisition, to produce a companion OME-XML file representing the person's notes during the experiment. Alternately, Notes could be run after the fact, to add further thoughts, notes about analysis, and so forth, to the data. Or Notes could be embedded in another piece of software such as VisBio or the 4D Data Browser plugin for ImageJ, to allow viewing and editing of the associated metadata. Each of these types of deployment should leverage a distinct template to optimize the user experience.

The template engine will need to be intelligent not just about which metadata fields are included and where they are arranged on-screen, but also what mode of operation Notes is currently in. An embedded viewer with editing capabilities disabled is different from a full-featured, standalone editor, which is very different from a helper app running side by side with a third-party acquisition system.