Bug 68752 - Do not enforce too many classes with Palette SPI
Do not enforce too many classes with Palette SPI
Status: NEW
Product: platform
Classification: Unclassified
Component: Palette
5.x
All All
: P3 (vote)
: TBD
Assigned To: Stanislav Aubrecht
issues@platform
: API, PERFORMANCE
Depends on:
Blocks: 90211
  Show dependency treegraph
 
Reported: 2005-11-15 16:54 UTC by _ rkubacki
Modified: 2008-12-23 00:28 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ rkubacki 2005-11-15 16:54:44 UTC
Current SPI for adding palette items requires new class for each item that
exists in palette. This is often followed by special class for customizer. This
is expensive pattern from performance point of view.

The alternative can be allowing of factory method in the XML declaration that
will return proper instance of ActiveEditorDrop. Another possibility is to
provide context (for example resource path in SFS) when calling constructor of
given object.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo