Rendering Models

Page restrictions apply
Added by Barbara Weinstein, last edited by Barbara Weinstein on Jul 05, 2009

The Matrix component displays CDF data on-screen using a rendering model. The rendering model uses a context node, which is the reference or starting point, to begin rendering. The context node itself isn't rendered, but its children or its descendants are painted.

In this CDF example, the default context node would be the data element, because it has a value of jsxroot for the jsxid attribute. The children, record elements, would be rendered to the screen. Specifying a context different than jsxroot will change which element in the CDF will be used as the context.

<data jsxid="jsxroot" xmax="50" ymax="50">
  <record jsxid="1"  x="4"  y="2"  m="5"/>
  <record jsxid="2"  x="14" y="40" m="15"/>
  <record jsxid="3"  x="42" y="24" m="3"/>
</data>

There are three rendering models: shallow, deep, and hierarchical. Shallow and deep are flat models, while the hierarchical model is rendered as a tree. Shallow only paints direct children of the context node. Deep paints all descendants. Hierarchical paints all children, but can also be performance-tuned to paint a given number of generations at a time. Because this allows nodes to be fetched only when a user expands a given branch, application performance is faster.

Use the lightweight Tree component (Miscellaneous > Tree) instead of the Matrix when your tree does not need multiple columns, formatters, and edit masks. For example, GI Builder uses a Matrix tree for the Properties Editor palette while using a simple tree for the Component Libraries palette.

Introduction to Matrix Components

Chapter 9 Using Matrix Components

Paging Models

Expand all Collapse all

Rendering Models

Contents

Labels