+ window pop up, and then run testgtk.lisp in the example directory.
+
+
+
+Guidelines for using the GTK+ API documentation
+-----------------------------------------------
+
+Here are some brief guidelines for using the GTK+ API documentation. A
+lot of (both intentional and unintentional) inconsistencies exists,
+so it is also wise to check the source code.
+
+- library prefixes are stripped from all symbols
+
+- object properties should be available as virtual slots. A lot of
+ "missing" properties are manually defined as slots. Slots may be read
+ only or write only, but there later type are generally only
+ defined automatically through introspection
+
+- the get/set part are removed from regular accessors, but retained
+ in functions which set or retrieve multiple values
+
+- predicate functions follow the normal convention of ending
+ with '-P'
+
+- if there are multiple similar named functions which only differ in
+ the type of argument they accept, only one function accepting any
+ kind of valid argument types is provided
+
+- there are no gtk_*_new functions, use MAKE-INSTANCE to create widgets
+
+- use CHILD-PROPERTY-VALUE or automatically defined accessors to
+ access child properties
+
+- use STYLE-PROPERTY-VALUE to access style properties
+
+- the only function used to connect signals is SIGNAL-CONNECT
+
+- some additional initargs to make-instance:
+
+ - gtk:container
+
+ child -- adds a child to a container widget. This argument could
+ be a widget or a list who's first element is a widget and the rest
+ child properties. Multiple :child initargs may be specified
+
+ children -- list of children to be added
+
+ child-args -- default child properties used when adding children (during
+ construction only)
+
+ show-children -- automatically make children (and grandchildren)
+ visible. May be overridden in a child by explicit specifying :visible or
+ another :show-children
+
+
+ - gtk:button
+
+ stock -- equivalent to ":label stock :use-stock t :use-underline t"
+
+
+ - gtk:dialog