Bug 161486 - [Palette] Performance: Look for ways to lazily initialize palette
Summary: [Palette] Performance: Look for ways to lazily initialize palette
Status: NEW
Alias: None
Product: GEF
Classification: Tools
Component: GEF-Legacy GEF (MVC) (show other bugs)
Version: 3.2.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: gef-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-18 17:45 EDT by Dan Lee CLA
Modified: 2010-11-04 17:39 EDT (History)
3 users (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 Dan Lee CLA 2006-10-18 17:45:51 EDT 
From what I understand, the GEF palette requires the entire palette definition to be passed to it upon initialization. For large products that have hundreds of palette items, it can take substantial amounts of time to create this palette definition. (Especially if the palette definition is built from parsing extension points).

I would like this bug to serve as a placeholder for investigating ways that GEF could lazily initialize the palette, instead of requiring the entire definition be passed to it on creation.
Comment 1 Randy Hudson CLA 2006-10-18 21:35:54 EDT 
I thought the purpose of extension points is that they are fast, since they avoid plugin activation. Isn't the workbench's New Wizard Dialog populated using extension points? It is also a tree structure that probably contains hundreds of items. Is the tree lazily populated?

You can share your palette root across all instances of the same editor type.