[rules-dev] GuvnorEditor refactoring

Hi All. Looking at a refactoring of the Guvnor Editor stuff to make it more "pluggable" so others can more easily create and reuse editors for given artifact types (file types). Really in principle is is simple, and close to what we have now: * An editor is responsible for showing a given artifact type. * An editor will be launched by guvnor when someone wants to view that file type * An editor can implement certain interfaces in which case it can be injected with events/other things it may need automatically * All editors will subclass GuvnorEditor * An editor registry (currently EditorLauncher which is hardcoded) will not what opens what etc... See attached sketch on how this may work... The benefits mean that editors can be very loosely coupled. Thoughts ? -- Michael D Neale home: www.michaelneale.net blog: michaelneale.blogspot.com