Commit f83daad6 authored by James Henstridge's avatar James Henstridge Committed by James Henstridge
Browse files

increment version number.

2002-06-06  James Henstridge  <james@daa.com.au>

	* configure.in: increment version number.

	* libglade.spec.in (Requires): set versions right.

	* NEWS: add news items.
parent 10c16c14
2002-06-06 James Henstridge <james@daa.com.au>
* configure.in: increment version number.
* libglade.spec.in (Requires): set versions right.
* NEWS: add news items.
2002-06-01 James Henstridge <james@daa.com.au>
* doc/tmpl/glade-init.sgml: copy info from tmpl/glade.sgml.
......
libglade-2.0.0: 6-January-2002
- fix up docs build, and make docbook files mostly XML
compatible in preparation for XMLised gtk-doc.
- bump version number up to 2.0.0.
libglade-1.99.12: 12-May-2002
- more changes to help with Murray's C++ bindings.
- check whether GTK has a GtkPlug implementation to help with
......
......@@ -3,30 +3,24 @@ LIBGLADE
Author: James Henstridge <james@daa.com.au>
This library allows you to load glade interface files in a program at runtime.
It doesn't require GLADE to be used, but GLADE is by far the easiest way to
create the interface files.
This library allows you to load glade interface files in a program at
runtime. It doesn't require GLADE to be used, but GLADE is by far the
easiest way to create the interface files.
For an idea of how to use the library, see test-libglade.c and
glade/glade-xml.h.
To compile, you will need the libxml package (aka the gnome-xml module in CVS)
which can be found on the GNOME FTP site or its mirrors. If you want GNOME
support, you will also need the gnome-libs package installed.
When I started developing this library, I was using a 486, and did not have
any problems with the speed. Since then, I have reduced its memory usage
and increased its speed a bit, so you should not have problems with the
library's speed :)
I would like to thank Damon Chaplin for writing GLADE, which is one of the
best user interface builders I have used.
To compile, you will need the libxml2 package (aka the gnome-xml
module in CVS) which can be found on the GNOME FTP site or its
mirrors. If you want GNOME support, you will also need the gnome-libs
package installed.
LIBGLADE INTERNALS
==================
If you are interested in how libglade works, here is a small description:
If you are interested in how libglade works, here is a small
description:
When glade_xml_new is called, the XML file is loaded using libxml.
Libglade uses the SAX interface because it is faster and allows me to
......@@ -35,10 +29,6 @@ file is cached, so that if you load the interface again, the file does
not need to be reparsed. If the file has changed though, it will be
reparsed.
The styles in the glade file are first passed to the GTK RC system, so
they can be applied to the widgets when the interface is built. Note
that newer versions of GLADE have removed the widget style code.
Now glade_xml_build_widget is called for all the toplevel widgets in
the interface (or if the second argument to glade_xml_new was non
NULL, the widget it refers to is treated as the toplevel).
......@@ -49,14 +39,15 @@ child widget, which is then packed into its parent. This is done
recursively, so the whole interface is constructed.
New widget types are added to the widget class hash with the
glade_register_widgets function. For an example, see the end of glade-gtk.c.
The automatic signal connection system uses the introspective capabilities of
dynamic linking. By openning a handle on NULL, we can get at all the global
symbols (global functions, global variables) in the executable, and the
libraries it is linked against. This is used to find the address of a signal
handler from its name, so that gtk_signal_connect can be called automatically
for you.
Of course, there are other ways of connecting the signals if your platform
doesn't support this feature.
\ No newline at end of file
glade_register_widgets function. For an example, see the end of
glade-gtk.c.
The automatic signal connection system uses the introspective
capabilities of dynamic linking. By openning a handle on NULL, we can
get at all the global symbols (global functions, global variables) in
the executable, and the libraries it is linked against. This is used
to find the address of a signal handler from its name, so that
gtk_signal_connect can be called automatically for you.
Of course, there are other ways of connecting the signals if your
platform doesn't support this feature.
-*- mode: autoconf -*-
AC_PREREQ(2.52)
AC_INIT(libglade, 1.99.12,
AC_INIT(libglade, 2.0.0,
[http://bugzilla.gnome.org/enter_bug.cgi?product=libglade])
AC_CONFIG_SRCDIR([test-libglade.c])
......
......@@ -9,7 +9,7 @@ BuildRoot: /var/tmp/%{name}-root
Packager: James Henstridge <james@daa.com.au>
URL: http://www.gnome.org
Requires: gtk+ >= 1.3.15
Requires: gtk+ >= 2.0.0
Requires: libxml2 >= 2.4.10
%description
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment