Bug 105621 - [Wizards] It should be possible to define new wizards with enablement or/and visibility
Summary: [Wizards] It should be possible to define new wizards with enablement or/and ...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-29 18:48 EDT by Stefan Lötscher CLA
Modified: 2019-09-06 16:04 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Lötscher CLA 2005-07-29 18:48:27 EDT 
The extension point org.eclipse.ui.newWizards should provide an "enablement" section in order to 
define when a new wizard is accessable. The perspective shortcuts for new wizards in 
org.eclipse.ui.perspectiveExtensions.newWizardShortcut should be enabled/disabled as well, if the 
newWizard is enabled/disabled.

In RCP application wizards are very useful to define e.g. workflows. But the workflows are often 
dependent on a certain context, as e.g. the type of the active editor. If the active editor is for example a 
person, it should possible to add a new address to this person with a wizard. But if there is no person 
editor, the address wizard should be disabled.

RCP application uses wizard for many different purposes but seldom to create new resources such as 
files and folders.
Comment 1 Boris Bokowski CLA 2009-11-26 16:20:10 EST 
Prakash is now responsible for watching bugs in the [Wizards] component area.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:04:19 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.