NEWS in 0.7

* Gtk is only initialized if it hasn't been already.

* The define-func syntax in gtk.defs has changed.  It is now

    (define-func NAME RETURN-TYPE (PARAM ...))

  That is, the params are gathered into their own list and are no
  longer simply the tail of the whole form.

* New function to initialize libguilegtk: sgtk_init_argv

* We no longer link libguilegtk against the guile libs, on the
  assumption that they are already included in the base guile
  application.  In particular, the static libqt.a was causing problems
  on Solaris.

NEWS in 0.6

* Only bug fixes.

NEWS in 0.5

* Please apply the gtk-interp.patch, Guile-gtk will work much better.

* The Gtk function are now contained in a module, (toolkits gtk).
  Start your programs with something like

    (use-modules (toolkits gtk))

  This should even work for the vanilla Guile interpreter when dynamic
  linking of modules works for you.

  To statically link libguilegtk into your application and make it
  available as a module, use

    scm_init_toolkits_gtkstubs_module ();

  instead of

    sgtk_init (&argc, &argv);

  If you continue to use sgtk_init you will get the old behaviour but
  the event driven repl wont work.

* Guile-gtk can now run a event driven repl.  This means that you can
  interactively test your programs.

  The repl is only started when Guile-gtk enters `interactive' mode,
  that is, when it is not started with the `-c' or `-s' switches.  The
  event driven repl also starts the main event processing loop (aka
  gtk-main).

  Therefore, scripts that are run with the -s switch to Guile-gtk
  should contain their own call to gtk-main (because the repl is not
  running), but code that will be loaded with -l, or interactively
  with `load' or from Emacs, etc, should *not* contain a call to
  gtk-main.

  To compensate, you might want to write your programs like this

    #! /usr/local/bin/guile-gtk \
    -e main -s
    !#

    (use-modules (toolkits gtk))

    ...
    setup your gui
    ...

    (define (main args)
      (gtk-main))

  When dynamic linking of modules works for you, you can replace
  "guile-gtk" in the first line with just "guile".

  To make a vanilla Guile boot into the event driven repl, use this:

    % guile -c "(use-modules (toolkits gtk)) (gtk-repl)"

  Implemantarywise, there should be enough hooks to run arbitrary
  event driven repls, not just one on the terminal.

