[
https://issues.apache.org/jira/browse/UIMA-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Zhu updated UIMA-3374:
----------------------------
Attachment: UIMA-3374 patch 2015-04-23.txt
In this patch, I did the following changes (the patch should be applied to the
uimaj-tools project only):
1. Renamed class variables by removing the "m" prefix. This naming convention
of using "m" prefix is not consistent with other places in the uimaj-core
project etc, and not consistent within the same class itself. In most other
places, the "m" prefix is not used.
2. Avoided warnings by adding types to the generics variables. The code is more
readable as it is easier to see what type of objects are stored in the
collections. Avoided unnecessary cast subsequently when iterating through the
generics collection.
3. Applied best practice of programming against interface. For instance,
instead of declaring variable with "ArrayList<String> names = new
ArrayList<String>();", use "List<String> names = new ArrayList<String>();",
instead of "public ArrayList<String> getNames() { return names;}", do "public
List<String> getNames() {return names;}".
These changes should have no impact to the functionality. Please review and let
me know if you have any concerns about these changes. Thanks.
> A new mode for annotation viewer based on feature values
> --------------------------------------------------------
>
> Key: UIMA-3374
> URL: https://issues.apache.org/jira/browse/UIMA-3374
> Project: UIMA
> Issue Type: Improvement
> Components: InternalTools
> Affects Versions: 2.5.0SDK
> Reporter: James Zhu
> Assignee: Marshall Schor
> Priority: Minor
> Labels: annotation, feature, filter, type, value, viewer
> Attachments: UIMA-3374 patch 2015-04-21.txt, UIMA-3374 patch
> 2015-04-23.txt, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg,
> screenshot-4.jpg
>
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> I'd like to propose adding a new "view mode" in the UIMA Annotation Viewer so
> that user can pick a specific type of annotations, and then pick a specific
> feature, and pick specific feature values available so user can see a subset
> of those annotation objects that have the specific feature values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)