* Use AST analysis for all controller inspection. The motivation for doing so is that it catches changes to annotations in a clean manner. The caveat is that ASTs are created frequently, resolving bindings in the process. This could be a source of performance issues over time. If it is, go back to the higher-level Java model API, and consider using IJavaElementDelta.getAnnotations.

* Make use of the Glossary's revision property, so that the inspector and info panels are updated instantaneously.

* Make controller suggestions based on the document name, as well as the controller content.

* Add the Glossary as a listener to the Java model from the outside, instead of from its constructor.

* Include a method that all panel controllers can implement to react to editor controller reference updates.