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: | DataObject editor: provide default handling | ||
---|---|---|---|
Product: | platform | Reporter: | Rochelle Raccah <raccah> |
Component: | Property Editors | Assignee: | Jiri Rechtacek <jrechtacek> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 19851 |
Description
Rochelle Raccah
2002-01-11 05:28:44 UTC
Target milestone -> 3.4 Target milestone -> 3.4 Target milestone -> 3.4 Target milestone -> 3.4 Target milestone was changed from '3.4' to TBD. Target milestone was changed from '3.4' to TBD. reassigne to Tim, new owner of property editors. Rochelle, what is the status of this request? From the thread on nbdev, it sounds like there are some very specific requirements (different behaviors for class nodes, etc.) that might not be appropriate for core, but some kind of pluggable filtration might do the trick? Also, it sounds like you have an implementation of what you want, but you would like to eliminate it and just use the core editor. Is there an impl of what you're after that you could attach? Yes, I think some kind of support in the core would be best, though it wouldn't exactly match my implementation. The goal would be to rewrite some of my code to use a core editor and provide this useful functionality to others. My code is in the closed source, so I can't attach it, but I can probably work with you offline and provide you with some more info. Passing property editor issues to new owner, Jirka It's not planned for long time. It's fair to close as WONTFIX |