[
https://issues.apache.org/jira/browse/UIMA-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916159#action_12916159
]
Jörn Kottmann commented on UIMA-1887:
-------------------------------------
Right now the Cas Editor defines an extension point which can be used to set
the Document Provider.
The Document Provider int he Cas Editor is responsible to find a type system
and styling information for
a CAS file which should be opened.
My initial intention was just have to another plugin which extends the Cas
Editor to define the Document Provider in order to embed it into an eclipse
application. This approach has the disadvantage that there can only be one
Document Provider per CAS Editor plugin instance,
that might not work well anyway.
To your question, yes it would be possible to have this functionally directly
in the Cas Editor but then we
have to change the way it looks up the type system and styling information for
a CAS.
Putting it directly into the Cas Editor plugin also has the advantage that the
feature is
directly available to all our users with the next release.
> Should be possible to open a CAS from a non Cas Editor project with the CAS
> Editor
> ----------------------------------------------------------------------------------
>
> Key: UIMA-1887
> URL: https://issues.apache.org/jira/browse/UIMA-1887
> Project: UIMA
> Issue Type: New Feature
> Components: Eclipse plugins
> Reporter: Jörn Kottmann
>
> It should be possible to open a CAS files which are inside an eclipse java
> project (and not an eclipse CAS Editor project) with the CAS Editor.
> After a short discussion with Marshall (see comments below) the issue is
> changed and now includes the
> creation of an eclipse uima development plugin which will host the extension
> to the Cas Editor.
> Until this new plugin is mature is will be located in the sandbox and named
> uimaj-ep-dev.
> In this proposed solution the Development Plugin extends the CAS Editor with
> a Document Provider which can load a type system and styling information from
> a non Cas Editor project. The Development Plugin can assume that the type
> system file is
> placed in a certain location, for example at the top level of the project
> folder and is named TypeSystem.xml.
> Additionally the Development Plugin should offer a file dialog to specify the
> type system in case it cannot be found
> or is not compatible with the CAS the user wants to open.
> The Development Plugin also provides a new view to edit the styling of the
> annotations.
> The goal of this issue is to quickly create an initial solution which can
> then be refined
> by input from users and other uima developers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
