Probably you already know this blog post
Just my 2c. anyway I think the author (Anton Arhipov) and Michael Neal is best people to answer you. Not sure they are reading this forum.
Thanks for the link. It seems that what I've been looking or is covered by GuvnorNG.
Mic should be reading these forums but he may be a bit busy at the moment with the imminent release. But Mike Brock is also helping.
Hey guys - yeah sorry I am more used to ignoring mailing lists then ignoring forums ;)
We had a google summer of code project to make editors pluggable (ended up using code generation) so that is what that blog post is about. That is specifically designed for opening files in guvnor and then choosing which editor to use based on the file extension meta data (like any OS does).
Not sure how applicable it is to everyone else, but its fairly general purpose. If there is a widget that obeys a certain constructor, then you can add it to a properties file, run a script to generate the "glue" code - and there you go (glue means launching code, plus menu items to create new ones etc, icons and such).
it was designed for the drools guvnor, but most of the concepts are general and Mike and I will be looking into making it generic.
An "editor" in this context is something that displays an editable form (or upload/download form) for some file that is stored (each save creates a new version, by default) in the repository. It is not so much for features like deploying/testing etc... just editing.
Mike may be able to comment more.
Does that make sense?
It is correct that we are developing a generic console framework that will support pluggable editors, that will be able to stand on it's own outside of Drools.
Yes, we should be using whatever you guys come up with. So far it looks FANTASTIC :-)