Provides ErrorManager - the central place for logging and reproting failures in NetBeans based system.
A set of utility classes covering a few general infrastructure points in the Open APIs.
There are several types of standard actions that should be used for many user interactions within NetBeans.
NetBeans uses special extensions to data transfer.
This module contains general classes needed in NetBeans, extensions to basic JRE contepts, useful methods and other UtilitiesAPI classes.
It is now increasingly common for NetBeans to run on Windows, Linux, or MacOS machines with so-called "HiDPI" screens, aka. "retina" screens in the Apple world. These screens have about twice the physical pixel density of traditional screens, making it necessary to scale GUI graphics up by some amount, e.g. 150% or 200% (depending on OS and OS-level user settings), in order to remain readable. Since Java 9, this scaling is done automatically by AWT by means of a scaling default transform in each Component's Graphics2D instances. This makes text sharp on HiDPI screens, but leaves bitmap icons blurry.
This change introduces a new abstract class VectorIcon, which can be extended to create custom-painted Icon instances that will look sharp on HiDPI screens, regardless of scaling level. See VectorIcon's Javadoc for a discussion of appropriate use cases.
BooleanStateActiondeprecated in favour of
The BooleanStateAction base class was deprecated, as there's a programatic API in Actions and a declarative @ActionState annotation which fully supersede the deprecated class.
The SPI NetworkSettings.ProxyCredentialsProvider allows NetBeans Platform users to provide proxy and network credentials, but the according API should also provide the password, not only the username.
Only some platforms provide an audible notification when user
tries to invoke a disabled action. So instead of Toolkit.beep()
which always plays a sound a new method
Utilities.disabledActionSound() shoud be used instead.
The following classes were spinned of into org.openide.util.base module:
The class Utilities was also split and the client desktop indepenent parts landed in BaseUtilities. Although all the constants and methods are still available through Utilities class, it is advised to change the dependencies and reference them through BaseUtilities.
If you are interested in logging from inside your module, or in writing your own log handler or in configuring the whole system, then best place to start is the NetBeans logging guide.
The sources for the module are in the NetBeans Mercurial repositories.
Read more about the implementation in the answers to architecture questions.