You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Joern Kottmann (JIRA)" <de...@uima.apache.org> on 2011/09/09 10:29:08 UTC
[jira] [Created] (UIMA-2225) Reusing of ICasEditor instances
doesn't surrounding update views
Reusing of ICasEditor instances doesn't surrounding update views
----------------------------------------------------------------
Key: UIMA-2225
URL: https://issues.apache.org/jira/browse/UIMA-2225
Project: UIMA
Issue Type: Bug
Components: CasEditor
Reporter: Joern Kottmann
Assignee: Joern Kottmann
Fix For: 2.3.2SDK
If the amount of editor in the workbench is restricted to a certain number, eclipse will reuse already existing editors and sets a new input.
In the case an editor input is change all the ICasEditor sensitive views are still bound to the old editor input.
To fix this introduce a new listener which can notify other views about an editor input change.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (UIMA-2225) Reusing of ICasEditor instances
doesn't surrounding update views
Posted by "Joern Kottmann (Reopened) (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joern Kottmann reopened UIMA-2225:
----------------------------------
There is one more issue with the action bars.
> Reusing of ICasEditor instances doesn't surrounding update views
> ----------------------------------------------------------------
>
> Key: UIMA-2225
> URL: https://issues.apache.org/jira/browse/UIMA-2225
> Project: UIMA
> Issue Type: Bug
> Components: CasEditor
> Reporter: Joern Kottmann
> Assignee: Joern Kottmann
> Fix For: 2.4.0SDK
>
>
> If the amount of editor in the workbench is restricted to a certain number, eclipse will reuse already existing editors and sets a new input.
> In the case an editor input is change all the ICasEditor sensitive views are still bound to the old editor input.
> The AnnotationEditor can be reused by the eclipse workbench, and also view switches can change the way an input CAS is displayed.
> The AnnotationEditor itself can deal with any type of CAS sofa, if it is a text it is displayed and if not an appropriate message page is displayed. The surrounding views don't have a mechanism to deal with changing editor input or changing CAS views.
> Therefore we should extend the page book style annotation editor views with a mechanism to have an additional layer of pages to cover the following cases:
> a) Show view implementation and cas contents (Maybe destroy it and re-create, reusable view
> pages are error prone to implement)
> b) View cannot be displayed because the document is not available (document failed to load)
> c) View cannot be displayed because the CAS view is incompatible with this view
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (UIMA-2225) Reusing of ICasEditor instances doesn't
surrounding update views
Posted by "Joern Kottmann (Closed) (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joern Kottmann closed UIMA-2225.
--------------------------------
Resolution: Fixed
Problem with duplicated actions bars is fixed, problem with selection handling from the wrong editor is fixed.
> Reusing of ICasEditor instances doesn't surrounding update views
> ----------------------------------------------------------------
>
> Key: UIMA-2225
> URL: https://issues.apache.org/jira/browse/UIMA-2225
> Project: UIMA
> Issue Type: Bug
> Components: CasEditor
> Reporter: Joern Kottmann
> Assignee: Joern Kottmann
> Fix For: 2.4.0SDK
>
>
> If the amount of editor in the workbench is restricted to a certain number, eclipse will reuse already existing editors and sets a new input.
> In the case an editor input is change all the ICasEditor sensitive views are still bound to the old editor input.
> The AnnotationEditor can be reused by the eclipse workbench, and also view switches can change the way an input CAS is displayed.
> The AnnotationEditor itself can deal with any type of CAS sofa, if it is a text it is displayed and if not an appropriate message page is displayed. The surrounding views don't have a mechanism to deal with changing editor input or changing CAS views.
> Therefore we should extend the page book style annotation editor views with a mechanism to have an additional layer of pages to cover the following cases:
> a) Show view implementation and cas contents (Maybe destroy it and re-create, reusable view
> pages are error prone to implement)
> b) View cannot be displayed because the document is not available (document failed to load)
> c) View cannot be displayed because the CAS view is incompatible with this view
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (UIMA-2225) Reusing of ICasEditor instances doesn't
surrounding update views
Posted by "Joern Kottmann (Closed) (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joern Kottmann closed UIMA-2225.
--------------------------------
Resolution: Fixed
All changes related to this issue have been done under UIMA-2273 which is very similar.
> Reusing of ICasEditor instances doesn't surrounding update views
> ----------------------------------------------------------------
>
> Key: UIMA-2225
> URL: https://issues.apache.org/jira/browse/UIMA-2225
> Project: UIMA
> Issue Type: Bug
> Components: CasEditor
> Reporter: Joern Kottmann
> Assignee: Peter Klügl
> Fix For: 2.4.0SDK
>
>
> If the amount of editor in the workbench is restricted to a certain number, eclipse will reuse already existing editors and sets a new input.
> In the case an editor input is change all the ICasEditor sensitive views are still bound to the old editor input.
> To fix this introduce a new listener which can notify other views about an editor input change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (UIMA-2225) Reusing of ICasEditor instances
doesn't surrounding update views
Posted by "Peter Klügl (Assigned JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Klügl reassigned UIMA-2225:
---------------------------------
Assignee: Peter Klügl (was: Joern Kottmann)
> Reusing of ICasEditor instances doesn't surrounding update views
> ----------------------------------------------------------------
>
> Key: UIMA-2225
> URL: https://issues.apache.org/jira/browse/UIMA-2225
> Project: UIMA
> Issue Type: Bug
> Components: CasEditor
> Reporter: Joern Kottmann
> Assignee: Peter Klügl
> Fix For: 2.4.0SDK
>
>
> If the amount of editor in the workbench is restricted to a certain number, eclipse will reuse already existing editors and sets a new input.
> In the case an editor input is change all the ICasEditor sensitive views are still bound to the old editor input.
> To fix this introduce a new listener which can notify other views about an editor input change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (UIMA-2225) Reusing of ICasEditor instances
doesn't surrounding update views
Posted by "Joern Kottmann (Updated) (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joern Kottmann updated UIMA-2225:
---------------------------------
Description:
If the amount of editor in the workbench is restricted to a certain number, eclipse will reuse already existing editors and sets a new input.
In the case an editor input is change all the ICasEditor sensitive views are still bound to the old editor input.
The AnnotationEditor can be reused by the eclipse workbench, and also view switches can change the way an input CAS is displayed.
The AnnotationEditor itself can deal with any type of CAS sofa, if it is a text it is displayed and if not an appropriate message page is displayed. The surrounding views don't have a mechanism to deal with changing editor input or changing CAS views.
Therefore we should extend the page book style annotation editor views with a mechanism to have an additional layer of pages to cover the following cases:
a) Show view implementation and cas contents (Maybe destroy it and re-create, reusable view
pages are error prone to implement)
b) View cannot be displayed because the document is not available (document failed to load)
c) View cannot be displayed because the CAS view is incompatible with this view
was:
If the amount of editor in the workbench is restricted to a certain number, eclipse will reuse already existing editors and sets a new input.
In the case an editor input is change all the ICasEditor sensitive views are still bound to the old editor input.
To fix this introduce a new listener which can notify other views about an editor input change.
> Reusing of ICasEditor instances doesn't surrounding update views
> ----------------------------------------------------------------
>
> Key: UIMA-2225
> URL: https://issues.apache.org/jira/browse/UIMA-2225
> Project: UIMA
> Issue Type: Bug
> Components: CasEditor
> Reporter: Joern Kottmann
> Assignee: Joern Kottmann
> Fix For: 2.4.0SDK
>
>
> If the amount of editor in the workbench is restricted to a certain number, eclipse will reuse already existing editors and sets a new input.
> In the case an editor input is change all the ICasEditor sensitive views are still bound to the old editor input.
> The AnnotationEditor can be reused by the eclipse workbench, and also view switches can change the way an input CAS is displayed.
> The AnnotationEditor itself can deal with any type of CAS sofa, if it is a text it is displayed and if not an appropriate message page is displayed. The surrounding views don't have a mechanism to deal with changing editor input or changing CAS views.
> Therefore we should extend the page book style annotation editor views with a mechanism to have an additional layer of pages to cover the following cases:
> a) Show view implementation and cas contents (Maybe destroy it and re-create, reusable view
> pages are error prone to implement)
> b) View cannot be displayed because the document is not available (document failed to load)
> c) View cannot be displayed because the CAS view is incompatible with this view
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (UIMA-2225) Reusing of ICasEditor instances
doesn't surrounding update views
Posted by "Joern Kottmann (Reopened) (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joern Kottmann reopened UIMA-2225:
----------------------------------
Assignee: Joern Kottmann (was: Peter Klügl)
We did fairly extensive changes in UIMA-2273 for this issue, but these changes need to be rolled back and done differently.
Changes will be checked in under this id, to ensure they can be distinguished easily from the rolled back changes.
> Reusing of ICasEditor instances doesn't surrounding update views
> ----------------------------------------------------------------
>
> Key: UIMA-2225
> URL: https://issues.apache.org/jira/browse/UIMA-2225
> Project: UIMA
> Issue Type: Bug
> Components: CasEditor
> Reporter: Joern Kottmann
> Assignee: Joern Kottmann
> Fix For: 2.4.0SDK
>
>
> If the amount of editor in the workbench is restricted to a certain number, eclipse will reuse already existing editors and sets a new input.
> In the case an editor input is change all the ICasEditor sensitive views are still bound to the old editor input.
> To fix this introduce a new listener which can notify other views about an editor input change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (UIMA-2225) Reusing of ICasEditor instances doesn't
surrounding update views
Posted by "Joern Kottmann (Closed) (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joern Kottmann closed UIMA-2225.
--------------------------------
Resolution: Fixed
It should work now.
> Reusing of ICasEditor instances doesn't surrounding update views
> ----------------------------------------------------------------
>
> Key: UIMA-2225
> URL: https://issues.apache.org/jira/browse/UIMA-2225
> Project: UIMA
> Issue Type: Bug
> Components: CasEditor
> Reporter: Joern Kottmann
> Assignee: Joern Kottmann
> Fix For: 2.4.0SDK
>
>
> If the amount of editor in the workbench is restricted to a certain number, eclipse will reuse already existing editors and sets a new input.
> In the case an editor input is change all the ICasEditor sensitive views are still bound to the old editor input.
> The AnnotationEditor can be reused by the eclipse workbench, and also view switches can change the way an input CAS is displayed.
> The AnnotationEditor itself can deal with any type of CAS sofa, if it is a text it is displayed and if not an appropriate message page is displayed. The surrounding views don't have a mechanism to deal with changing editor input or changing CAS views.
> Therefore we should extend the page book style annotation editor views with a mechanism to have an additional layer of pages to cover the following cases:
> a) Show view implementation and cas contents (Maybe destroy it and re-create, reusable view
> pages are error prone to implement)
> b) View cannot be displayed because the document is not available (document failed to load)
> c) View cannot be displayed because the CAS view is incompatible with this view
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira