public interface Renderer
Block. Currently every block has two renderers,
which are identified by the renderer 'type' (see getType()). Every block also has a
Processor, which is similar to a Renderer, but a processor never generates content, only
handles interaction.
A Renderer is stateless.
Rendering itself happens with the render(org.mmbase.util.functions.Parameters, java.io.Writer, org.mmbase.framework.RenderHints) method, which is typically done using Framework.render(org.mmbase.framework.Renderer, org.mmbase.util.functions.Parameters, org.mmbase.util.functions.Parameters, java.io.Writer, org.mmbase.framework.WindowState).| Modifier and Type | Interface and Description |
|---|---|
static class |
Renderer.Type |
| Modifier and Type | Method and Description |
|---|---|
Block |
getBlock()
Every renderer renders for a certain block.
|
Parameter<?>[] |
getParameters()
A renderer may need certain parameters.
|
Renderer.Type |
getType()
Describes what kind of renderer this is
|
URI |
getUri()
An URI which may identify the implementation of this Renderer.
|
URI |
getUri(Parameters blockParameters,
RenderHints hints)
Ann URL which may identify a specific rendition
|
void |
render(Parameters blockParameters,
Writer w,
RenderHints hints)
Renders to a writer.
|
Renderer.Type getType()
Block getBlock()
Parameter<?>[] getParameters()
void render(Parameters blockParameters, Writer w, RenderHints hints) throws FrameworkException
FrameworkExceptionURI getUri()
URI getUri(Parameters blockParameters, RenderHints hints)
MMBase 1.9-SNAPSHOT - ${javadoctimestamp}