ruby-****@sourc*****
ruby-****@sourc*****
2012年 9月 19日 (水) 10:32:01 JST
-------------------------
REMOTE_ADDR = 184.145.80.187
REMOTE_HOST =
URL = http://ruby-gnome2.sourceforge.jp/hiki.cgi?tut-gtk2-treev-parts
-------------------------
@@ -14,13 +14,17 @@
=== Gtk::TreeModel
+Based on the titles of this chapter (Tree View) and this paragraph, as well as its introduction discussions about the Gtk::TreeModel one may conclude that the fundamental data structure of both view and the model classes is that of a tree. This is only partially true, since the simplest form of a tree is a single branch or in computer parlance a list. Due to the fact that a list is also a tree, little or no effort has been made to separate the two, at least in the introductory paragraphs into this topic. Nevertheless, please keep in mind that our first program examples are about the one dimensional lists, and that unfortunately, we can nod avoid using word tree, when it comes to tree view or tree model for that matter. This situation is somewhat alleviated by the fact that Gtk+ comes with two built-in data stores or models, namely, Gtk::ListStore and Gtk::TreeStore. As the names imply, Gtk::ListStore is used for simple lists of data items where items have no hierarchical par
ent-child relationships, and the Gtk::TreeStore which is used for tree-like data structures, where items can have parent-child relationships.
+
+
+
+
The GTK+ provides four types of built-in tree model classes, but in our sessions here we will cover only two - the Gtk::TreeStore and the Gtk::ListStore. The Gtk::TreeModel interface defines a generic tree interface for use by the Gtk::TreeView widget. It is designed to be usable with any appropriate data structure. Data itself is stored in objects whose classes implement the Gtk::TreeModel interface.
The Gtk::TreeModel interface provides a standard set of methods for retrieving general information about the data that is stored. For example, it allows you to get the number of rows in the tree and the number of children of a certain row. The Gtk::TreeModel also gives you a way to retrieve the data that is stored in a specific row of the store.
It should be clear, that Gtk::TreeModel itself only provides a way to query the characteristics of a data store and to retrieve existing data, but it does not provide a way to remove or add rows to the store. This is done using the specific store's methods.
-Based on the titles of this chapter (Tree View) and this paragraph as well as its introduction discussing the Gtk::TreeModel one may conclude that the fundamental data structure of both view and the model classes is that of a tree. This is only partially true, since the simplest form of a tree is a single branch or in computer parlance a list. Due to the fact that a list is also a tree, little or no effort has been made to separate the two, at least in the introductory paragraphs into this topic. Nevertheless, please keep in mind that our first program examples are about the one dimensional lists, and that unfortunately, we can nod avoid using word tree, when it comes to tree view or tree model for that matter. This situation is somewhat alleviated by the fact that Gtk+ comes with two built-in data stores or models, namely, Gtk::ListStore and Gtk::TreeStore. As the names imply, Gtk::ListStore is used for simple lists of data items where items have no hierarchical parent-chil
d relationships, and the Gtk::TreeStore which is used for tree-like data structures, where items can have parent-child relationships.