/
Renderer Component Types

Documentation for a historical release of Infusion: 1.3
Please view the Infusion Documentation site for the latest documentation.
If you're looking for Fluid Project coordination, design, communication, etc, try the Fluid Project Wiki.

Renderer Component Types

Jan 20, 2011

The Renderer categorizes component into different types depending on the nature of the data that is to be rendered. Different component types will have different fields, but in general, the tree for a component will contain either the actual data or a reference to a data model containing the data (see Renderer Data Binding for more information). The component types are not stated explicitly in the object, but the type is inferred by the Renderer based on the presence of the require fields.

The following tables describe the different types of components and the fields used by each component. In these tables, field names shown in bold text are the definitive fields that will indicate which type of component is being described.

Bound A control which holds a single value

Link A reference to a URL

Select A selection control where a user chooses either one or many options from a set of alternatives. May be rendered as a set of checkboxes or a <select> tag.

SelectChoice An isolated choice from a parent Select control
Note that these objects will always be used in conjuction with a Select object.

InitBlock A script block containing a single function call

Container A component that contains other components in a free-form way

Joint Container A point in the component tree representing a forced branch in the template, between two tags given different IDs

Message A component that encapsulates the data needed to resolve a localised message

Verbatim A text node in the resulting document, to be output without any escaping