This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 41071 - XYZ could be hidden by PropertyPanel
Summary: XYZ could be hidden by PropertyPanel
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Infrastructure (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: Petr Hrebejk
Depends on:
Blocks: 40703
  Show dependency tree
Reported: 2004-03-17 15:05 UTC by Jaroslav Tulach
Modified: 2006-03-24 09:43 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Tulach 2004-03-17 15:05:43 UTC
In general it would be nice to have working
PropertyEditors for various types defined by
project APIs. During my work on webstart module
needed a UI component to select list of
AntArtefacts from other modules. If there was a
(ex) property editor for AntArtefact[], I could
just reuse it (via PropertyPanel right now) and I
would not need to bother. The same applies to
LibraryCustomizer, that could disappear from api
if turned into PropertyEditor and probably
ProjectChooser which could be editor for Project

I understand that this may not be the highest
priority, but I consider such cobundle of UI with
API good practice which shall be addressed as time
permits at least in the most obvious cases
Project, AntArtefact[], ReferenceHelper which
nearly every project type needs to provide UI for.
Comment 1 Jaroslav Tulach 2004-03-17 15:10:57 UTC
There was a discussion about usage of PropertyPanel on nbdev
which questioned its usefulness, but as it seems right now, this was
more comment about the API which can be replaced, the SPI -
ExPropertyEditor - seemed reasonably ok to be used and useful.
Comment 2 Jesse Glick 2004-03-18 10:02:55 UTC
This is actually multiple requests, so feel free to split up into
multiple issues. Based on what I have heard mentioned so far, some may
be WONTFIX, but I don't really understand the property sheet API (does
anyone except Tim?) so I won't comment further.
Comment 3 _ tboudreau 2004-03-18 10:51:29 UTC
As I mentioned to Jarda last night, ExPropertyEditor is not so good and useful - that is, its 
main problems are that:
 - Nobody understands it
 - PropertyEnv munges together all sorts of totally orthagonal things - managing OK 
buttons, finding feature descriptors, etc...
 - The design is optimized for ease of maintenance, at the cost of a cryptic API.  In other 
words, it makes things easier for us by making it harder for anyone actually using it

That said, go ahead and use it if you want.
Comment 4 Petr Hrebejk 2004-05-03 13:24:27 UTC
Dedcided not to use the property editor paradigm.
Comment 5 Marian Mirilovic 2005-07-12 10:01:25 UTC