GTK is a multi-platform toolkit for creating graphical user interfaces.
Go to file
Havoc Pennington 3a422541e3 Convert GdkPixbuf to GObject, leaving it opaque (i.e. derivation is not
2000-06-21  Havoc Pennington  <hp@pobox.com>

* gdk-pixbuf.c: Convert GdkPixbuf to GObject, leaving it opaque
(i.e. derivation is not allowed, and there are no virtual methods
anyway).
(gdk_pixbuf_preinit): Call g_type_init() here.
(gdk_pixbuf_init): Add a user-friendly init function, for users
of standalone gdk-pixbuf

* gdk-pixbuf-animation.c: Convert to GObject, in the same
way GdkPixbufAnimation was done.

* gdk-pixbuf.h: Remove gdk_pixbuf_set_unref_handler() and
gdk_pixbuf_finalize() from API, since these are broken and don't
make sense with new GObject stuff.

2000-06-21  Havoc Pennington  <hp@pobox.com>

* gdk/gdkwindow.c (_gdk_window_destroy_hierarchy): Fix bug where
we didn't check window->bg_pixmap != GDK_NO_BG.

* gtk/gdk-pixbuf-loader.c: Change to reflect GObject-ification of
gdk-pixbuf
2000-06-22 15:36:12 +00:00
debian Argh. Missed one dumb space in rules file. Fixed. 1998-11-18 06:25:35 +00:00
demos Convert GdkPixbuf to GObject, leaving it opaque (i.e. derivation is not 2000-06-22 15:36:12 +00:00
docs Move file to here. TODO: Update Makfile.am 2000-06-22 13:05:24 +00:00
examples New section on GtkCalendar Update example code 2000-02-23 10:59:21 +00:00
gdk Convert GdkPixbuf to GObject, leaving it opaque (i.e. derivation is not 2000-06-22 15:36:12 +00:00
gdk-pixbuf Convert GdkPixbuf to GObject, leaving it opaque (i.e. derivation is not 2000-06-22 15:36:12 +00:00
gtk Convert GdkPixbuf to GObject, leaving it opaque (i.e. derivation is not 2000-06-22 15:36:12 +00:00
modules .cvsignore additions 2000-06-21 16:21:15 +00:00
po Triditional Chinese PO File 2000/06/21 2000-06-21 07:06:01 +00:00
tests Use gunichar instead of gint when appropriate in the interfaces 2000-06-21 18:51:36 +00:00
.cvsignore .cvsignore additions 2000-01-21 21:57:14 +00:00
acconfig.h Welcome aboard, gdk-pixbuf. 2000-06-21 20:47:22 +00:00
acinclude.m4 Merges from gtk-1-2 2000-03-14 19:57:25 +00:00
AUTHORS Incremented version to 1.2.0. -Shawn <amundson@gtk.org> 1999-02-25 21:39:14 +00:00
autogen.sh [ Merges from gtk-1-2 ] 1999-09-28 20:19:13 +00:00
ChangeLog Convert GdkPixbuf to GObject, leaving it opaque (i.e. derivation is not 2000-06-22 15:36:12 +00:00
ChangeLog.pre-1-0 ChangeLog split up into ChangeLog.pre-1-0 and ChangeLog. 1998-04-17 01:07:36 +00:00
ChangeLog.pre-1-2 moved old ChangeLog to ChangeLog.pre-1-2, and started new one. 1999-02-27 00:26:30 +00:00
ChangeLog.pre-2-0 Convert GdkPixbuf to GObject, leaving it opaque (i.e. derivation is not 2000-06-22 15:36:12 +00:00
ChangeLog.pre-2-2 Convert GdkPixbuf to GObject, leaving it opaque (i.e. derivation is not 2000-06-22 15:36:12 +00:00
ChangeLog.pre-2-4 Convert GdkPixbuf to GObject, leaving it opaque (i.e. derivation is not 2000-06-22 15:36:12 +00:00
ChangeLog.pre-2-6 Convert GdkPixbuf to GObject, leaving it opaque (i.e. derivation is not 2000-06-22 15:36:12 +00:00
ChangeLog.pre-2-8 Convert GdkPixbuf to GObject, leaving it opaque (i.e. derivation is not 2000-06-22 15:36:12 +00:00
ChangeLog.pre-2-10 Convert GdkPixbuf to GObject, leaving it opaque (i.e. derivation is not 2000-06-22 15:36:12 +00:00
config.guess Merges from gtk-1-2 2000-03-14 19:57:25 +00:00
config.h.win32 Don't define HAVE_DIMM_H if MSC, as you have to get the Platform SDK to 1999-11-04 23:42:51 +00:00
config.sub Merges from gtk-1-2 2000-03-14 19:57:25 +00:00
configure.in Define version numbers for GDK_PIXBUF_*, as they get substituted into a 2000-06-22 03:06:30 +00:00
COPYING Changed LGPL address for FSF in all .h and .c files 1998-04-13 02:02:47 +00:00
gtk-config.in make it possible to configure gtk for different targets on the same 2000-06-07 16:44:29 +00:00
gtk.m4 Print out version when test succeeds. 2000-05-11 00:25:20 +00:00
gtk+.spec.in Added lib/gtk+/include/* to %files (bug #5178 - Peter Wainright) 2000-01-24 01:38:17 +00:00
HACKING - GNU autoconf 2.13 - GNU automake 1.4 (Beta releases are at 1999-01-17 16:54:58 +00:00
INSTALL Remove all references to offscreen flag which was no longer used. 2000-06-02 03:14:07 +00:00
INSTALL.in Adapt cast macros to standard. 1999-11-22 21:52:50 +00:00
ltconfig Merges from gtk-1-2 2000-03-14 19:57:25 +00:00
ltmain.sh Merges from gtk-1-2 2000-03-14 19:57:25 +00:00
makecopyright Changed LGPL address for FSF in all .h and .c files 1998-04-13 02:02:47 +00:00
Makefile.am Welcome aboard, gdk-pixbuf. 2000-06-21 20:47:22 +00:00
NEWS Adapt cast macros to standard. 1999-11-22 21:52:50 +00:00
NEWS.pre-1-0 ooops, fogot this on my last commit... 1998-05-07 07:45:04 +00:00
README Remove all references to offscreen flag which was no longer used. 2000-06-02 03:14:07 +00:00
README.cvs-commits Fixed argument list and return type for non-XIM fallback. 1998-12-09 18:13:52 +00:00
README.in Adapt cast macros to standard. 1999-11-22 21:52:50 +00:00
README.nanox make it possible to configure gtk for different targets on the same 2000-06-07 16:44:29 +00:00
README.win32 Large changes to the Win32 backend, partially made necessary by the 2000-05-01 22:06:49 +00:00
sanity_check [ Merges from gtk-1-2 ] 1999-09-28 20:19:13 +00:00
TODO Spelling/grammar fixes from Martin Buchholz <martin@xemacs.org> 2000-02-29 13:15:10 +00:00
TODO.xml Change 1.4 version numbers to 2.0. 2000-06-21 23:45:41 +00:00

General Information
===================

This is GTK+ version 1.3.0. GTK+, which stands for the Gimp ToolKit, 
is a library for creating graphical user interfaces for the X Window 
System. It is designed to be small, efficient, and flexible. GTK+ is 
written in C with a very object-oriented approach.

The official ftp site is:
  ftp://ftp.gtk.org/pub/gtk

The official web site is:
  http://www.gtk.org/

A mailing list is located at:
  gtk-list@redhat.com

To subscribe: mail -s subscribe gtk-list-request@redhat.com < /dev/null
(Send mail to gtk-list-request@redhat.com with the subject "subscribe")

Installation
============

See the file 'INSTALL'

How to report bugs
==================

Bugs should be reported to the GNOME bug tracking
system. (http://bugs.gnome.org). To report a problem
about GTK+, send mail to submit@bugs.gnome.org.

The subject of the mail should describe your problem.
In the body of the mail, you should first include
a "pseudo-header" that gives the package and 
version number. This should be separated by a blank
line from the actual headers.

 Package: gtk+
 Version: 1.3.0

[ Please substitute 1.3.0 with the version of GTK+ that
  you have installed ]

Then describe the bug. Include:

* Information about your system. For instance:

   - What operating system and version
   - What version of X
   - For Linux, what version of the C library

  And anything else you think is relevant.

* How to reproduce the bug. 

  If you can reproduce it with the testgtk program that is built 
  in the gtk/ subdirectory, that will be most convenient.  Otherwise, 
  please include a short test program that exhibits the behavior. 
  As a last resort, you can also provide a pointer to a larger piece 
  of software that can be downloaded.

  (Bugs that can be reproduced within the  GIMP are almost as good 
  as bugs that can be reproduced in testgtk. If you are reporting a 
  bug found with the GIMP, please include the version number of the GIMP 
  you are using)

* If the bug was a crash, the exact text that was printed out
  when the crash occured.

* Further information such as stack traces may be useful, but
  is not necessary. If you do send a stack trace, and the error
  is an X error, it will be more useful if the stacktrace
  is produced running the test program with the --sync command
  line option.

An example of a bug report:

====
To: submit@bugs.gnome.org
From: yourname@your.address.org
Subject: handlebox test in testgtk is misnamed.

Package: gtk+
Version: 1.3.0

When I run gtk/testgtk, the button "handle box"
is misnamed. There are multiple handle boxes in
the demo, so it should be "handle boxes", to
be like "buttons" or "check buttons".
===

Patches
=======

Patches can be uploaded to the incoming/ directory on
ftp.gtk.org.  Please follow the instructions there, and include
your name and email address in the README file.

If the patch fixes a bug, it is usually a good idea to include
all the information described in "How to Report Bugs".