Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 328474 - Inconsistencies in editor workflows
Summary: Inconsistencies in editor workflows
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-22 09:15 EDT by Jeff McAffer CLA
Modified: 2019-09-09 02:46 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff McAffer CLA 2010-10-22 09:15:34 EDT
I've been working a lot with products and features lately and there is are some inconsistencies in the editor workflows.

Deleting:
- In the product editor Dependencies list there is a Remove (and Remove All) button and context menu entry
- In the feature editor lists there is only the context menu and it is called Delete
*** Suggest adding a Remove button to the Feature editor since is has an Add button as well.


Add dialog filtering
- In the feature editor if you add a plugin (Plugin or Dependencies tab) you do NOT need a * in the filter text in the Plugin Selection dialog
- In the feature editor adding a feature you DO need a *
- in the product editor adding a feature or a plugin you DO need a *
*** Suggest all Selection dialogs NOT require * as 99% of the time the thing being selected is org.<something long>.<something interesting for filtering>.  That is, 99% of the time * is needed so just make it implicit.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:17:26 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 2 Julian Honnen CLA 2019-09-09 02:46:10 EDT
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.