[
https://issues.apache.org/jira/browse/UIMA-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörn Kottmann updated UIMA-1887:
--------------------------------
Summary: It should be possible to open a CAS file from a non Cas
Editor project (was: Should be possible to open a CAS from a non Cas Editor
project with the CAS Editor)
Assignee: Jörn Kottmann
Fix Version/s: 2.3.1SDK
Description:
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 spending more time on the issue the plan how to implement it changed
again.
The previous idea of having an additional plugin for this functionality is
dropped and the change is directly
integrated into the Cas Editor plugin.
There are two changes which must be performed for this issue:
1. The Document Provider is extended with a custom logic to open a CAS file
from a non Cas Editor Project.
Its assumed that the type system is placed in a certain location, if it cannot
find in this location the
user if prompted by a dialog to provide a valid type system for the CAS.
This mechanism should be improved in the future to play nicely together with
all other plugins wich also need
access to a type system, like the description editors.
2.
The UI to configure the annotation styles must be moved to the editor and away
from the Cas Editor Project
handling code. To accomplish this the Document Provider should be responsible
for accessing/modifying
the styling information. A new view is added to the editor which can display
the styling information and
gives access to the annotation property dialog to modify the styling.
The styling information is shared between all editors type system wide, if the
style is changed in one editor
its changed in all other editors which display a CAS with the same type system.
The goal of this issue is to create an initial solution which can then be
refined
by input from users and other uima developers.
was:
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.
Component/s: CasEditor
(was: Eclipse plugins)
> It should be possible to open a CAS file from a non Cas Editor project
> ----------------------------------------------------------------------
>
> Key: UIMA-1887
> URL: https://issues.apache.org/jira/browse/UIMA-1887
> Project: UIMA
> Issue Type: New Feature
> Components: CasEditor
> Reporter: Jörn Kottmann
> Assignee: Jörn Kottmann
> Fix For: 2.3.1SDK
>
>
> 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 spending more time on the issue the plan how to implement it changed
> again.
> The previous idea of having an additional plugin for this functionality is
> dropped and the change is directly
> integrated into the Cas Editor plugin.
> There are two changes which must be performed for this issue:
> 1. The Document Provider is extended with a custom logic to open a CAS file
> from a non Cas Editor Project.
> Its assumed that the type system is placed in a certain location, if it
> cannot find in this location the
> user if prompted by a dialog to provide a valid type system for the CAS.
> This mechanism should be improved in the future to play nicely together with
> all other plugins wich also need
> access to a type system, like the description editors.
> 2.
> The UI to configure the annotation styles must be moved to the editor and
> away from the Cas Editor Project
> handling code. To accomplish this the Document Provider should be responsible
> for accessing/modifying
> the styling information. A new view is added to the editor which can display
> the styling information and
> gives access to the annotation property dialog to modify the styling.
> The styling information is shared between all editors type system wide, if
> the style is changed in one editor
> its changed in all other editors which display a CAS with the same type
> system.
> The goal of this issue is to 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.
