clg-fireproof Code
A fork of CLG project (Common Lisp bindings to GTK+ v2.x)
Status: Beta
Brought to you by:
ampy
This package contains fork to the Common Lisp bindings to GTK+ v2.x. The
goal of the fork is to make the package working with current (stable) Debian
versions of the libraries and SBCL. It currently works with SBCL 1.3.14.
Ports to other CL implementations may be added later.
New versions
------------
The most recent version of this fork can be downloaded from
http://sourceforge.net/projects/clgfireproof.
Build instructions
------------------
1. For the old version of the instructions see original clg package.
The clg bindings require recent SBCL with asdf installed, the system
must have pkgconfig and libgtk2.0-dev, obviously.
2. Set up paths to match your system:
- Set the correct pkg-config search path if your Gtk+ installation
is in an unusual place, by adding it to the PKG_CONFIG_PATH
environment variable before starting lisp.
- Make sure ASDF finds the system definition files:
have a directory where those files reside. If you don't have one -
create it: mkdir /path/to/my/systems/.
Add this in the .sbclrc:
(require :asdf)
(push "/path/to/my/systems/" asdf:*central-registry*)
Link the system definition files from the clg subdirectories
to this directory. For example:
$ cd <clg toplevel>
$ find .. -name '*.asd' -exec ln -s {} /path/to/my/systems/ \;
3. Compile and load the system:
(require :gtk) ; for the cairo, pango, rsvg use the appropriate symbols
If you are running SBCL with Slime you need to put the following
in ~/.swank.lisp to prevent Slime from spawning multiple
threads, since GTK+ is not really thread safe:
#+sbcl(setq swank:*communication-style* :fd-handler)
CLISP needs to be started with the option '-ansi' for clg to
compile and load.
4. If everything worked, try (load "hello-world") to see a small
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, use the #'apropos and
#'describe.
- 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
button -- button specification applied to dialog-add-button. Multiple
:button initargs may be specified
buttons -- list of button specifications
Send comments and patches to clg-devel@lists.sourceforge.net or
ampy@users.sourceforge.net.