A renderer is used to render the table cells of the document table view in the Explorer, Workflow, Query and ResourceChooser window.

Class to subclass

In order to create your own renderer class you need to subclass the abstract hox.corem.editor.toolkit.table.columnrenderer.LayoutColumnRenderer class and implement the following two methods:

Integrate your renderer into the Site Manager using editor.xml

You can integrate your renderer into the Site Manager using the element Renderer which can be used within the element ColumnDefinition. ColumnDefinition can be used within TableDefinition which can be used within the elements Explorer, Query, Workflow and ResourceChooser.

<Explorer name="configurable-explorer">
 	...
	<TableDefinition>
	..
		<ColumnDefinition class="StringColumn" 
		name="" width="40" weight="0.0">
			<Renderer class=
			"com.customer.example.editor.ConstantLayoutColumnRenderer"/>
		</ColumnDefinition>
		...
	</TableDefinition>
</Explorer>

Example

The following example shows a very simple renderer which inserts a JLabel saying "Hello" in each cell of the table column independent of the column type.

package com.customer.example.editor;

import javax.swing.JComponent;
import javax.swing.JLabel;
import 
hox.corem.editor.toolkit.table.columnrenderer.LayoutColumnRenderer;

public class ConstantLayoutColumnRenderer extends 
		LayoutColumnRenderer {
    
	public JComponent getComponent() {
		return new JLabel();
	}	

	public void customizeComponent(JComponent component, Object data) 
	{
		JLabel label = (JLabel)component;
		label.setOpaque(true);
		label.setText("Hello");
	}
} 

Why returning the JLabel first and entering the text ("Hello") later? This is because customizeComponent will be called later, short before the rendering. It is good practice to execute "expensive" operations at this place.