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.
Summary: | XYZ could be hidden by PropertyPanel | ||
---|---|---|---|
Product: | projects | Reporter: | Jaroslav Tulach <jtulach> |
Component: | Generic Infrastructure | Assignee: | Petr Hrebejk <phrebejk> |
Status: | CLOSED WONTFIX | ||
Severity: | blocker | CC: | dkonecny, jglick, tboudreau, tzezula |
Priority: | P3 | ||
Version: | 4.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 40703 |
Description
Jaroslav Tulach
2004-03-17 15:05:43 UTC
There was a discussion about usage of PropertyPanel on nbdev (http://www.netbeans.org/servlets/ReadMsg?msgId=715504&listName=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. 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. 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. Dedcided not to use the property editor paradigm. closed |