Package | Description |
---|---|
org.openide.windows |
Interfaces for working with input/output tabs.
|
Just an API/SPI for defining the output window.
Added methods that provide better info about state of fold handles, and methods that handle unexpected situations silently instead of throwing exceptions.
Added enum elements LOG_SUCCESS, LOG_FAILURE, LOG_WARNING
and LOG_DEBUG
into IOColors.OutputType
that can be passed to get/setColor methods to have access
to color of standard logging messages.
Added enum element IOColors.OutputType.INPUT
that can be passed to get/setColor methods to set a color of the
input text.
Adding class IOFolding for checking that folding is supported and for creating folds in output window, and class FoldHandle for finishing the folds and creation of nested folds.
See
IOFolding,
FoldHandle.
Added method IOProvider.getIO
that takes all
4 supported parameters and that complements other
getIO
methods. See
IOProvider
The original mapping from IO name to IO object has been replaced with mapping from pair [IO container, IO name] to IO object. This mapping is used for reusing of IO objects.
There is an SPI but additional implementations are not expected. The API is most important.
Simple usage example:
InputOutput io = IOProvider.getDefault().getIO("My Window", true); io.select(); OutputWriter w = io.getOut(); w.println("Line of plain text."); OutputListener listener = new OutputListener() { public void outputLineAction(OutputEvent ev) { StatusDisplayer.getDefault().setStatusText("Hyperlink clicked!"); } public void outputLineSelected(OutputEvent ev) { // Let's not do anything special. } public void outputLineCleared(OutputEvent ev) { // Leave it blank, no state to remove. } }; w.println("Line of hyperlinked text.", listener, true);
|
You will very likely also want to declare
OpenIDE-Module-Requires: org.openide.windows.IOProvider
to ensure that an Output Window implementation is in fact enabled.
Read more about the implementation in the answers to architecture questions.