This module provides all object for a widget displaying data organized in a table.

• There are two flavors: A simple list organizes data in rows and a tree which provides the possibility to impose a hierarchical structure on the entries of one column.
• The widget is composed of two parts: A database holding rows of data and the widget object itself which displays items based on the database. Several widgets may use a single storage object. The data in the database may be what is directly displayed like strings and images or it may be some meta information like the padding or color of an item. Several attributes in the storage object may be used to display one column in the widget. In contrast each row in the store corresponds to a row in the widget.
• The widget that displays the data and can be inserted like any other into a container is called TreeView. This widget is itself a container for TreeViewColumns which has a title at the top of the column. Each TreeViewColumn in turn can contain several Renderer. There are currently three Renderer, one for each of the following items: text, Pixbuf and ToggleButton.
• The database is called store, specifically for simple lists it is ListStore and for hierachical data it is called TreeStore. A store is created from a skeleton. '' Attributes can be added to an empty ListSkel or TreeSkel skeleton which yields a functions to access the attribute and an Association. After the skeleton is turned into a store by calling either newListStore or newTreeStore, Associations can be inserted together with an appropriate Renderer into a TreeViewColumn.

TODO

• Figure out if properties in the store have priority over global properties when both are set.

Reserve a new column in ListSkel to hold values for the given attribute.

• The type of the column is determined by the given Attribute of the ViewColumn which should be stored here. It is possible to associate this column with several ViewColumns.

Create a new ListStore database.

• This method throws an exception if the skeleton has been used before.

Reserve a new column in TreeSkel to hold values for the given attribute.

• The type of the column is determined by the given Attribute of the ViewColumn which should be stored here. It is possible to associate this column with several ViewColumns.

Create a new TreeStore database.

• This method throws an exception if the skeleton has been used before.

Create a new rederer showing text.

• There can be several Renderer in each TreeViewColumn. Each Renderer can reflect several Attributes from a ListStore or TreeStore.

Create a new renderer showing a Pixbuf.

• There can be several Renderer in each TreeViewColumn. Each Renderer can reflect several Attributes from a ListStore or TreeStore.

Create a new renderer showing a ToggleButton.

• There can be several Renderer in each TreeViewColumn. Each Renderer can reflect several Attributes from a ListStore or TreeStore.

Create a link between the store and this model.

• The results are undefined, if this TreeViewColumn was not created with the same TreeModel as the Associations.

Set an Attribute globally.

• An Attribute of a Renderer can either be set on a row-by-row basis using listSkelAddAttribute and treeSkelAddAttribute or globally through this function.

Emitted when the user finished editing a cell.

• This signal is not emitted when editing is disabled (see cellEditable) or when the user aborts editing.