You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Peter Klügl (JIRA)" <de...@uima.apache.org> on 2012/08/28 11:19:07 UTC
[jira] [Created] (UIMA-2463) Improve default annotation style
assignment of CAS Editor
Peter Klügl created UIMA-2463:
---------------------------------
Summary: Improve default annotation style assignment of CAS Editor
Key: UIMA-2463
URL: https://issues.apache.org/jira/browse/UIMA-2463
Project: UIMA
Issue Type: Bug
Components: CasEditor
Affects Versions: 2.4.1SDK
Reporter: Peter Klügl
Assignee: Peter Klügl
Priority: Minor
Fix For: 2.4.1SDK
DefaultColors.assignColors() assigns style background with somewhat random but different bright colors to all types. This method is called when is type system is not known yet.
AnnotationStyle.getAnnotationStyleFromStore() tries to read to stored style. If there is no information, then the style is set underlined red.
The situation in my use case is the following: I create a script with some type definitions resulting in a type system. I write some rules and test the result by taking a look at the xmi with the CAS Editor. Here, the first method is applied, because the type system is new. Then I write additional rules and add some other types. If I now review the result, the new types in the known types system are all set to red/underlined, because if the second method. Thus, it's harder to distinguish them.
A solution is the assignment of a random bright background color as default in AnnotationStyle.getAnnotationStyleFromStore(). However, the colors should
not change randomly if the type system changes. So after a style is assigned, this style should be stored inside the configuration, instead of repeating the process the next time the CAS is loaded. If the process is repeated and a change occurs to the type system, then the style assigning code might choose a different color.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (UIMA-2463) Improve default annotation style
assignment of CAS Editor
Posted by "Peter Klügl (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443130#comment-13443130 ]
Peter Klügl commented on UIMA-2463:
-----------------------------------
I committed the proposed changes that are probably not the best way to solve the problem but should do the trick. Jörn, are the changes ok?
> Improve default annotation style assignment of CAS Editor
> ----------------------------------------------------------
>
> Key: UIMA-2463
> URL: https://issues.apache.org/jira/browse/UIMA-2463
> Project: UIMA
> Issue Type: Bug
> Components: CasEditor
> Affects Versions: 2.4.1SDK
> Reporter: Peter Klügl
> Assignee: Peter Klügl
> Priority: Minor
> Fix For: 2.4.1SDK
>
>
> DefaultColors.assignColors() assigns style background with somewhat random but different bright colors to all types. This method is called when is type system is not known yet.
> AnnotationStyle.getAnnotationStyleFromStore() tries to read to stored style. If there is no information, then the style is set underlined red.
> The situation in my use case is the following: I create a script with some type definitions resulting in a type system. I write some rules and test the result by taking a look at the xmi with the CAS Editor. Here, the first method is applied, because the type system is new. Then I write additional rules and add some other types. If I now review the result, the new types in the known types system are all set to red/underlined, because if the second method. Thus, it's harder to distinguish them.
> A solution is the assignment of a random bright background color as default in AnnotationStyle.getAnnotationStyleFromStore(). However, the colors should
> not change randomly if the type system changes. So after a style is assigned, this style should be stored inside the configuration, instead of repeating the process the next time the CAS is loaded. If the process is repeated and a change occurs to the type system, then the style assigning code might choose a different color.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira