diff --git a/docs/reference/ChangeLog b/docs/reference/ChangeLog index f3b63f279c..f7f9929bfb 100644 --- a/docs/reference/ChangeLog +++ b/docs/reference/ChangeLog @@ -1,3 +1,7 @@ +2004-10-16 Matthias Clasen + + * gtk/glossary.xml: Additions. + 2004-10-15 Matthias Clasen * gtk/tmpl/gtkaboutdialog.sgml: More short description diff --git a/docs/reference/gtk/glossary.xml b/docs/reference/gtk/glossary.xml index a79951af99..82d274aa85 100644 --- a/docs/reference/gtk/glossary.xml +++ b/docs/reference/gtk/glossary.xml @@ -153,9 +153,10 @@ model column - A column in a tree model, holding data of a certain type. The types which - can be stored in the columns of a model have to be specified when the model - is constructed, see e.g, gtk_list_store_new(). + A column in a tree model, holding data of a certain type. + The types which can be stored in the columns of a model + have to be specified when the model is constructed, see + e.g. gtk_list_store_new(). view column @@ -167,17 +168,18 @@ model-view widget - These widgets follow the well-known model-view pattern, which separates the - data (the model) to be displayed from the component which does the actual - visualization (the view). Examples of this pattern in GTK+ are the - GtkTreeView/GtkTreeModel + These widgets follow the well-known model-view pattern, which separates + the data (the model) to be displayed from the component which does the + actual visualization (the view). Examples of this pattern in GTK+ are + the GtkTreeView/GtkTreeModel and GtkTextView/GtkTextBuffer - One important advantage of this pattern is that it is possible to display the - same model in multiple views; another one that the separation of the model - allows a great deal of flexibility, as demonstrated by e.g. + One important advantage of this pattern is that it is possible to + display the same model in multiple views; another one that the + separation of the model allows a great deal of flexibility, as + demonstrated by e.g. GtkTreeModelSort or GtkTreeModelFilter. @@ -194,7 +196,7 @@ GTK_NO_WINDOW flag set, and can be tested with the GTK_WIDGET_NO_WINDOW() + linkend="gtk-widget-no-window:caps">GTK_WIDGET_NO_WINDOW() macro. @@ -231,7 +233,7 @@ Widgets that don't own the GdkWindow on which they draw are called no-window widgets. This can be tested with the GTK_WIDGET_NO_WINDOW() + linkend="gtk-widget-no-window:caps">GTK_WIDGET_NO_WINDOW() macro. Normally, these widgets draw on their parent's GdkWindow. @@ -270,11 +272,11 @@ GDK inherited the concept of screen from the X window system, which considers a screen to be a rectangular area, on which - applications may place their windows. Each screen has a - root window which - defines the area of the screen. Screens under X may have quite - dissimilar visuals. + applications may place their windows. Screens under X may have + quite dissimilar visuals. Each screen can stretch across multiple physical monitors. + + In GDK, screens are represented by GdkScreen objects. @@ -286,8 +288,8 @@ A style encapsulates what GTK+ needs to know in order to draw - a widget. Styles can be modified with resource - files. + a widget. Styles can be modified with + resource files. @@ -298,8 +300,8 @@ A widget that does not require a parent - container. The only toplevel widget in GTK+ is GtkWindow. + container. The only toplevel widgets in GTK+ are GtkWindow and widgets derived from it. container @@ -329,7 +331,25 @@ - + + + visual + + + A visual describes how color information is stored in pixels. + A screen may support + multiple visuals. On modern hardware, the most common visuals + are truecolor visuals, which store a fixed number of bits + (typically 8) for the red, green and blue components of a color. + + + On ancient hardware, one may still meet indexed visuals, which + store color information as an index into a color map, or even + monochrome visuals. + + + + widget