You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <ui...@incubator.apache.org> on 2007/06/15 21:11:25 UTC
[jira] Created: (UIMA-458) For creating new UIMA descriptors in
Eclipse, make accelerator keys work better
For creating new UIMA descriptors in Eclipse, make accelerator keys work better
-------------------------------------------------------------------------------
Key: UIMA-458
URL: https://issues.apache.org/jira/browse/UIMA-458
Project: UIMA
Issue Type: Improvement
Components: Eclipse plugins
Affects Versions: 2.1
Reporter: Marshall Schor
Priority: Trivial
If you use keyboard shortcuts to create a new UIMA component, things don't quite work because many of the UIMA components get "filtered" by the keyboard keys. This may be fixable with proper accelerator key specifications.
Failing case for example:
1) select a Java project
2) press (assuming normal key bindings) ALT - f - n - o - u which is short for:
menu - File - New - Other - filter by "u". This shows the UIMA folder under "other", and also expands it, but filters it to only show strings containing words which start with a "u". So no component show up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Updated: (UIMA-458) For creating new UIMA descriptors
in Eclipse, make accelerator keys work better
Posted by Marshall Schor <ms...@schor.com>.
Possible 2.2 issues waiting some status change before we do a *vote*:
CVD issues: UIMA-420, UIMA-316, UIMA-307
Changing default for TypsSystemMgr.addFeature UIMA-395
Declaration of multiple externalResources with same name UIMA-346
If you know anything about these (such as - they've been fixed :-)
please update Jira.
Then, take a look at the test plan and see if you think we're ready to
vote....
-Marshall
Marshall Schor wrote:
> Good points - I'll keep both versions from now on. I was trying to
> clean up Jira
> a bit to see if we had any remaining issues that needed attention in
> this release.
>
> There are some which I didn't know anything about - so I left as
> affects 2.1 (only).
> These are mostly things Thilo and Adam might know the status of...
> please have a look :-)
>
> -Marshall
>
> Adam Lally wrote:
>> On 7/17/07, Thilo Goetz <tw...@gmx.de> wrote:
>>> I wonder: is it a good idea to change the "affects version" label
>>> for these issues? I mean, they do affect 2.1, and since they haven't
>>> been fixed it's reasonable to assume that they affect 2.2 also.
>>> Is there an advantage to changing this?
>>>
>>
>> I think you can actually select multiple versions for the "Affects
>> Version/s" label. So I definitely wouldn't remove 2.1.
>>
>> As to whether it's worth the effort to add 2.2, it might make sense to
>> do this to support using the JIRA search to search for issues
>> affecting a particular version. I'm assuming JIRA doesn't do the
>> inference that unresolved issues affecting 2.1 also affect 2.2.
>>
>> -Adam
>>
>>
>
>
>
Re: [jira] Updated: (UIMA-458) For creating new UIMA descriptors
in Eclipse, make accelerator keys work better
Posted by Thilo Goetz <tw...@gmx.de>.
I didn't know you could have multiple affected versions, that's even
better. I'll do some Jira housekeeping tomorrow as well.
--Thilo
Marshall Schor wrote:
> Good points - I'll keep both versions from now on. I was trying to
> clean up Jira
> a bit to see if we had any remaining issues that needed attention in
> this release.
>
> There are some which I didn't know anything about - so I left as affects
> 2.1 (only).
> These are mostly things Thilo and Adam might know the status of...
> please have a look :-)
>
> -Marshall
>
> Adam Lally wrote:
>> On 7/17/07, Thilo Goetz <tw...@gmx.de> wrote:
>>> I wonder: is it a good idea to change the "affects version" label
>>> for these issues? I mean, they do affect 2.1, and since they haven't
>>> been fixed it's reasonable to assume that they affect 2.2 also.
>>> Is there an advantage to changing this?
>>>
>>
>> I think you can actually select multiple versions for the "Affects
>> Version/s" label. So I definitely wouldn't remove 2.1.
>>
>> As to whether it's worth the effort to add 2.2, it might make sense to
>> do this to support using the JIRA search to search for issues
>> affecting a particular version. I'm assuming JIRA doesn't do the
>> inference that unresolved issues affecting 2.1 also affect 2.2.
>>
>> -Adam
>>
>>
Re: [jira] Updated: (UIMA-458) For creating new UIMA descriptors
in Eclipse, make accelerator keys work better
Posted by Marshall Schor <ms...@schor.com>.
Good points - I'll keep both versions from now on. I was trying to
clean up Jira
a bit to see if we had any remaining issues that needed attention in
this release.
There are some which I didn't know anything about - so I left as affects
2.1 (only).
These are mostly things Thilo and Adam might know the status of...
please have a look :-)
-Marshall
Adam Lally wrote:
> On 7/17/07, Thilo Goetz <tw...@gmx.de> wrote:
>> I wonder: is it a good idea to change the "affects version" label
>> for these issues? I mean, they do affect 2.1, and since they haven't
>> been fixed it's reasonable to assume that they affect 2.2 also.
>> Is there an advantage to changing this?
>>
>
> I think you can actually select multiple versions for the "Affects
> Version/s" label. So I definitely wouldn't remove 2.1.
>
> As to whether it's worth the effort to add 2.2, it might make sense to
> do this to support using the JIRA search to search for issues
> affecting a particular version. I'm assuming JIRA doesn't do the
> inference that unresolved issues affecting 2.1 also affect 2.2.
>
> -Adam
>
>
Re: [jira] Updated: (UIMA-458) For creating new UIMA descriptors in Eclipse, make accelerator keys work better
Posted by Adam Lally <al...@alum.rpi.edu>.
On 7/17/07, Thilo Goetz <tw...@gmx.de> wrote:
> I wonder: is it a good idea to change the "affects version" label
> for these issues? I mean, they do affect 2.1, and since they haven't
> been fixed it's reasonable to assume that they affect 2.2 also.
> Is there an advantage to changing this?
>
I think you can actually select multiple versions for the "Affects
Version/s" label. So I definitely wouldn't remove 2.1.
As to whether it's worth the effort to add 2.2, it might make sense to
do this to support using the JIRA search to search for issues
affecting a particular version. I'm assuming JIRA doesn't do the
inference that unresolved issues affecting 2.1 also affect 2.2.
-Adam
Re: [jira] Updated: (UIMA-458) For creating new UIMA descriptors
in Eclipse, make accelerator keys work better
Posted by Thilo Goetz <tw...@gmx.de>.
I wonder: is it a good idea to change the "affects version" label
for these issues? I mean, they do affect 2.1, and since they haven't
been fixed it's reasonable to assume that they affect 2.2 also.
Is there an advantage to changing this?
--Thilo
Marshall Schor (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/UIMA-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Marshall Schor updated UIMA-458:
> --------------------------------
>
> Affects Version/s: (was: 2.1)
> 2.2
>
> Won't be fixed for 2.2
>
>> For creating new UIMA descriptors in Eclipse, make accelerator keys work better
>> -------------------------------------------------------------------------------
>>
>> Key: UIMA-458
>> URL: https://issues.apache.org/jira/browse/UIMA-458
>> Project: UIMA
>> Issue Type: Improvement
>> Components: Eclipse plugins
>> Affects Versions: 2.2
>> Reporter: Marshall Schor
>> Priority: Trivial
>>
>> If you use keyboard shortcuts to create a new UIMA component, things don't quite work because many of the UIMA components get "filtered" by the keyboard keys. This may be fixable with proper accelerator key specifications.
>> Failing case for example:
>> 1) select a Java project
>> 2) press (assuming normal key bindings) ALT - f - n - o - u which is short for:
>> menu - File - New - Other - filter by "u". This shows the UIMA folder under "other", and also expands it, but filters it to only show strings containing words which start with a "u". So no component show up.
>
[jira] Updated: (UIMA-458) For creating new UIMA descriptors in
Eclipse, make accelerator keys work better
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor updated UIMA-458:
--------------------------------
Affects Version/s: (was: 2.1)
2.2
Won't be fixed for 2.2
> For creating new UIMA descriptors in Eclipse, make accelerator keys work better
> -------------------------------------------------------------------------------
>
> Key: UIMA-458
> URL: https://issues.apache.org/jira/browse/UIMA-458
> Project: UIMA
> Issue Type: Improvement
> Components: Eclipse plugins
> Affects Versions: 2.2
> Reporter: Marshall Schor
> Priority: Trivial
>
> If you use keyboard shortcuts to create a new UIMA component, things don't quite work because many of the UIMA components get "filtered" by the keyboard keys. This may be fixable with proper accelerator key specifications.
> Failing case for example:
> 1) select a Java project
> 2) press (assuming normal key bindings) ALT - f - n - o - u which is short for:
> menu - File - New - Other - filter by "u". This shows the UIMA folder under "other", and also expands it, but filters it to only show strings containing words which start with a "u". So no component show up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-458) For creating new UIMA descriptors in
Eclipse, make accelerator keys work better
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor updated UIMA-458:
--------------------------------
Affects Version/s: 2.3
defer beyond 2.3.0
> For creating new UIMA descriptors in Eclipse, make accelerator keys work better
> -------------------------------------------------------------------------------
>
> Key: UIMA-458
> URL: https://issues.apache.org/jira/browse/UIMA-458
> Project: UIMA
> Issue Type: Improvement
> Components: Eclipse plugins
> Affects Versions: 2.1, 2.2, 2.3
> Reporter: Marshall Schor
> Priority: Trivial
>
> If you use keyboard shortcuts to create a new UIMA component, things don't quite work because many of the UIMA components get "filtered" by the keyboard keys. This may be fixable with proper accelerator key specifications.
> Failing case for example:
> 1) select a Java project
> 2) press (assuming normal key bindings) ALT - f - n - o - u which is short for:
> menu - File - New - Other - filter by "u". This shows the UIMA folder under "other", and also expands it, but filters it to only show strings containing words which start with a "u". So no component show up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-458) For creating new UIMA descriptors in
Eclipse, make accelerator keys work better
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor updated UIMA-458:
--------------------------------
Affects Version/s: 2.1
> For creating new UIMA descriptors in Eclipse, make accelerator keys work better
> -------------------------------------------------------------------------------
>
> Key: UIMA-458
> URL: https://issues.apache.org/jira/browse/UIMA-458
> Project: UIMA
> Issue Type: Improvement
> Components: Eclipse plugins
> Affects Versions: 2.1, 2.2
> Reporter: Marshall Schor
> Priority: Trivial
>
> If you use keyboard shortcuts to create a new UIMA component, things don't quite work because many of the UIMA components get "filtered" by the keyboard keys. This may be fixable with proper accelerator key specifications.
> Failing case for example:
> 1) select a Java project
> 2) press (assuming normal key bindings) ALT - f - n - o - u which is short for:
> menu - File - New - Other - filter by "u". This shows the UIMA folder under "other", and also expands it, but filters it to only show strings containing words which start with a "u". So no component show up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.