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.
User problem: ----------------------------------- The concept of immediate changes without hitting OK or Apply button is counterintuitive and does not allow the user to Cancel changes. User need: ----------------------------------- User needs an intuitive and consistent way how to enter data in the IDE's dialogs. Product requirement: ----------------------------------- OK/Cancel approach to all dialogs in the IDE.
Difficulty: 9 Hack factor: ? One main source of dialogs, and unfortunately, a thing that makes this issue almost literally impossible to solve: java.beans.PropertyEditor.getCustomEditor() The problems: 1. An under-specified (afterthought?) API that defines no contract for how a custom editor should behave 2. Custom editors commonly implemented as inner classes of property editors (or PropertyEditor implemented on the custom editor component class) - these often do their own updating of the underlying property/property editor. There is no way to enforce OK/Cancel semantics (there's no way to even enforce that the component is a component, not a window). See http://openide.netbeans.org/proposals/property-infrastructure.html for a detailed exposition of some of the issues. Solution: - Deprecate/discontinue usage of getCustomEditor - Provide a separate registry of custom editors which map to properties. Define an interface that must be used, which defines the contract required by the infrastructure
Re-assigning Tim's issues to Dafe.
Right, but should be divided into specific enhancements for specific dialogs, make no sense to have such overall not specific enh in IZ. Please enter specific defects where things are broken.
I think that this issue might be an umbrella issue for all specific issues. It could be tracked better. What do you think?
Yes, but we should have specific issues first, for umbrella to make sense.