Bug 263466 - [Wizards] adding project nature filter for WizardNewFileCreationPage API
Summary: [Wizards] adding project nature filter for WizardNewFileCreationPage API
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2009-02-03 10:07 EST by Mircea Luchian CLA
Modified: 2019-09-06 16:13 EDT (History)
0 users

See Also:


Attachments
screenshot (97.24 KB, image/jpeg)
2009-02-03 10:07 EST, Mircea Luchian CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mircea Luchian CLA 2009-02-03 10:07:42 EST
Created attachment 124550 [details]
screenshot

Extending class WizardNewFileCreationPage does not allow filtering the project list by using project natures. As a requirement when building RCP products, some custom New File wizard pages that extend WizardNewFileCreationPage are valid for a certain type of projects, not all projects in the workspace. 
As a result, the list (see screenshot) in the page must display only the relevant projects in the workspace.

Besides importing in my own development environment the WizardNewFileCreationPage, ResourceAndContainerGroup and ContainerSelectionGroup in which the treeViewer is defined, I otherwise am unable to define a filter. Sure, I can override the validate() function in WizardNewFileCreationPage, however this does not provide filtering of the list.

It would be useful to allow the filtering of the projects through the project natures in the API.
Comment 1 Boris Bokowski CLA 2009-02-11 10:47:05 EST
http://wiki.eclipse.org/Platform_UI/How_to_Contribute
Comment 2 Boris Bokowski CLA 2009-11-26 16:19:44 EST
Prakash is now responsible for watching bugs in the [Wizards] component area.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:13:54 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.