Create  Edit  FrontPage  Index  Search  Changes  History  RSS  Back  Login

tut-treeview-renderer-renderer Diff - Ruby-GNOME2 Project Website

  • Added parts are displayed like this.
  • Deleted parts are displayed like this.

= Cell Renderers
{{link "tut-treeview-renderer", "tut-treeview-renderer", "tut-treeview", "tut-treeview-renderer-attributes"}}

Different cell renderers exist for different purposes:

* Gtk::CellRendererText renders strings or numbers or boolean values as text strings ("Joe", "99.32", "true")
* Gtk::CellRendererPixbuf is used to display images; either user-defined images, or one of the included stock icons.
* Gtk::CellRendererToggle displays a boolean value in form of a check box or as a radio button.
* Gtk::CellEditable is a special cell that implements editable cells (ie. Gtk::Entry or Gtk::SpinButton in a treeview)

We said that model and view have to be connected  (i.e. Gtk::TreeView has to be associated with Gtk::TreeStore or Gtk::ListStore). How the tree data types (strings, numbers and boolean) are handled in Gtk for this eventuality is best seen in the code which indirectly points out to the Gtk::CellRendererText's ability to separate the forementioned data types. Following is the example code (note that a renderer is not even shown here, though if it is to render certain column from model, it has to be made aware of that column with the pertinent data type):type, which is accomplished by

store =, TrueClass, Integer, FixNum, Float)
treeview =

Contrary to what one may think, a cell renderer does not render just one single cell, but is responsible for rendering part or whole of a tree view column for each single row. It basically starts in the first row and renders its part of the column there. Then it proceeds to the next row and renders its part of the column there again. And so on.

How does a cell renderer know what to render? A cell renderer object has certain 'properties' that are documented in the API reference (just like most other objects, and widgets). These properties determine what the cell renderer is going to render and how it is going to be rendered. Whenever the cell renderer is called upon to render a certain cell, it looks at its properties and renders the cell accordingly. This means that whenever you set a property or change a property of the cell renderer, this will affect all rows that are rendered after the change, until you change the property again.

Here is a silly and utterly useless little example that demonstrates this behaviour, and introduces some of the most commonly used properties of Gtk::CellRendererText:

  require 'gtk2'

  treestore =, String)
  # Append a toplevel row and leave it empty
  parent = treestore.append(nil)
  # Append a child to the toplevel row and fill in some data
  iter = treestore.append(parent)
  iter[0] = "Joe"
  iter[1] = "Average"
  # Append a second child to the toplevel row and fill in some data
  iter = treestore.append(parent)
  iter[0] = "Jane"
  iter[1] = "Common"
  view =
  view.selection.mode = Gtk::SELECTION_NONE                                                                                                                              
  # Create a renderer and set the 'text' property
  renderer =
  renderer.text = "Boooo!"
  # Add column using our renderer
  col ="First Name", renderer)
  # Create another renderer and set the 'background' property
  renderer =
  renderer.background = "orange"
  # Add column using the second renderer
  col ="Last Name", renderer)
  window =
  window.signal_connect("delete_event") { Gtk.main_quit; exit! }

{{image_right "renderer.png"}}

It looks like the tree view display is partly correct and partly incomplete. The tree view renders to the left, but it does not display any of the data that we have stored in the model. This is because we have made no connection between what the cell renderers should render and the data in the model. We have simply set some cell renderer properties on start-up, and the cell renderers adhere to those set properties meticulously.