Package org.knime.core.data.renderer

Interfaces and default implementations for renderer of DataValue objects.

See:
Description

Interface Summary

DataValueRenderer	General interface for classes that are able to render special derivatives of DataValue.
DataValueRendererFamily	Container for different DataValueRenderers which can be used to render one particular kind of DataValue.

Class Summary

AbstractPainterDataValueRenderer	Abstract implementation of a DataValueRenderer that renders more complex scenes than just ordinary text.
BitVectorValuePixelRenderer	Paints BitVectorValue elements.
BitVectorValueStringRenderer
BooleanValueRenderer	Boolean renderer.
ByteVectorValuePixelRenderer	Paints ByteVectorValue elements.
ByteVectorValueStringRenderer	Renderer for byte vector values showing the string representation.
ComplexNumberValueRenderer	Render to display a complex number value using a given NumberFormat.
DefaultDataValueRenderer	Default implementation for a renderer for DataValue objects.
DefaultDataValueRendererFamily	Default container for DataValueRenderer.
DoubleBarRenderer	Renderer for double cells that paints the whole range in a bar according to the cell's value.
DoubleGrayValueRenderer	Renderer for double cells that paints the whole range in gray color according to the cell's value.
DoubleValueRenderer	Render to display a double value using a given NumberFormat.
IntValueRenderer
LongValueRenderer	Renderer for long values that simply prints the value.
MultiLineBasicLabelUI	Label UI that respects the linebreaks in the label to be rendered.
MultiLineStringValueRenderer	This class renders strings that consist of more than one line.
SetOfRendererFamilies	Container for DataValueRendererFamily that is by itself a renderer family.
StringValueRenderer	Renderer for DataCells that are compatible with StringValue classes.

Enum Summary

BitVectorValueStringRenderer.Type

Possible types for string representation.

Package org.knime.core.data.renderer Description

Interfaces and default implementations for renderer of DataValue objects.

This package describes the general structure for renderer and renderer families of DataValue. Generally, each DataValue implementation can define its own set of renderer. These renderer are accumulated in a DataValueRendererFamily.

Here is what you should do if you implement your own DataValue and make one or more renderer available for it:

• Create your own renderer implementing the DataValueRenderer interface. (You might consider to derive from DefaultDataValueRenderer).
• Implement a DataValueRendererFamily that either uses singletons of the renderers above or creates them on request. As before: it is probably useful to extend the default implementation, i.e. DefaultDataValueRendererFamily. Such a family is responsible to handle multiple different renderers.
• Make a UtilityFactory in your DataValue implementation available as described in the manual methode getNativeRenderer() and return your newly created renderer family therein.