Bug 65303 - [Wizards] Handling of new wizard extensions recreated new menu each time
Summary: [Wizards] Handling of new wizard extensions recreated new menu each time
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-02 09:46 EDT by Kim Horne CLA
Modified: 2019-09-06 16:14 EDT (History)
1 user (show)

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 Kim Horne CLA 2004-06-02 09:46:36 EDT 
Every time new wizards are needed (via the new wizard itself or from simply
popping up a context menu on a project) the entire new wizard registry is
re-evaluated.  This includes creation of new image descriptors and images.  This
strikes me as being bad, bordering on terrible, particularly for downstream
products that have zillions of wizards.
Comment 1 Tod Creasey CLA 2004-06-08 09:05:33 EDT 
Downgrading this one and moving to LATER for future consideration.

This is occuring because MainActionGroup creates a new NewWizardActionGroup 
everytime it is created in fillContextMenu().

The size of the list is determined by getNewWizardActionIds() in the 
perspective so I would not imagine this gets any bigger than 10 or so.
Comment 2 Tod Creasey CLA 2004-06-08 09:10:19 EDT 
Reopening to mark later. The issue is that we do not cache the new wizard 
entries.
Comment 3 Tod Creasey CLA 2004-06-08 09:10:41 EDT 
Marking later as this is not a significant performance issue at this time.
Comment 4 Tod Creasey CLA 2004-06-28 11:28:21 EDT 
Reopening now that 3.0 has shipped
Comment 5 Boris Bokowski CLA 2009-11-26 16:21:39 EST 
Prakash is now responsible for watching bugs in the [Wizards] component area.
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:14:27 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.