Great to know that you can build.
The Cas Viewer assumes that there is a type system file with name
ending
with"typesystem.xml" in the same folder as the xmi file. Because of
that, by
putting a small code to look at the type system folder in your Cas
Editor
RCP, it is possible to put the Cas Viewer in your RCP.
I did have this small piece of code. Do you like me to submit that ?
Sure this is possible, why should we do this ?
The Cas Editor shows nearly the same information as the Cas Viewer
does. I think it would be confusing to have two different editors to
show
a CAS file. If there is something important missing in the Cas Editor,
it
can be added, just point it out.
It is not a big deal to create a plugin which contains the viewing an
editing part
of the Cas Editor. This plugin will then expose an API to open a CAS
object in
the editor. We can then use this in the Cas Editor RCP and together with
a uima development plugin inside an eclipse instance.
Please explain what is the benefit from having the Cas Viewer instead of
changing the Cas Editor.
Jörn
