Go to file
2001-03-06 00:33:07 +00:00
contrib Commit missed changelog entry bit. 2001-01-17 19:32:55 +00:00
debian
demos Added new menu separator item. The drawing and size handling is still done 2001-02-21 09:29:01 +00:00
docs You can't use + as a metacharacter for basic regular expressions. (This 2001-03-03 23:29:50 +00:00
examples Make gdk_colormap_sync private since it was never exported in a header 2001-02-02 22:19:31 +00:00
gdk Added GdkWindowTypeHint type. Added modal_hint field to GdkWindindow. New 2001-03-05 15:09:02 +00:00
gdk-pixbuf shut up CVS 2001-03-05 19:56:46 +00:00
gtk Updated docs to be sane 2001-03-06 00:33:07 +00:00
m4macros Really release 1.3.1 2000-07-15 01:07:42 +00:00
modules made the "parent_class" pointer static. 2001-03-05 16:44:18 +00:00
po Updated Norwegian translation. 2001-03-02 21:08:41 +00:00
tests renamed "child_toggled" to "has_child_toggled". 2001-03-05 19:43:24 +00:00
.cvsignore shut up CVS 2001-03-05 19:56:46 +00:00
acconfig.h Added ENABLE_SHADOW_FB 2001-01-11 16:39:21 +00:00
acinclude.m4 Merges from gtk-1-2 2000-03-14 19:57:25 +00:00
AUTHORS
autogen.sh When doing sanity checking on ACLOCAL_FLAGS, look for glib-2.0.m4 not 2000-11-04 15:14:34 +00:00
ChangeLog fix busted /* comment */ 2001-03-06 00:09:28 +00:00
ChangeLog.pre-1-0
ChangeLog.pre-1-2
ChangeLog.pre-2-0 fix busted /* comment */ 2001-03-06 00:09:28 +00:00
ChangeLog.pre-2-2 fix busted /* comment */ 2001-03-06 00:09:28 +00:00
ChangeLog.pre-2-4 fix busted /* comment */ 2001-03-06 00:09:28 +00:00
ChangeLog.pre-2-6 fix busted /* comment */ 2001-03-06 00:09:28 +00:00
ChangeLog.pre-2-8 fix busted /* comment */ 2001-03-06 00:09:28 +00:00
ChangeLog.pre-2-10 fix busted /* comment */ 2001-03-06 00:09:28 +00:00
config.guess Merges from gtk-1-2 2000-03-14 19:57:25 +00:00
config.h.win32.in gtk/gtkmain.c Use the new 2001-01-17 22:26:19 +00:00
config.sub Merges from gtk-1-2 2000-03-14 19:57:25 +00:00
configure.in Remove gdkcc.h reference. 2001-02-13 04:56:07 +00:00
COPYING
gdk-2.0.pc.in Adapt to uscore-ification of gtktextiterprivate 2001-01-04 17:48:43 +00:00
gdk-pixbuf-2.0.pc.in Remove spurious const. 2001-03-03 18:39:33 +00:00
gtk-2.0.m4 Really release 1.3.1 2000-07-15 01:07:42 +00:00
gtk-config-2.0.in Really release 1.3.1 2000-07-15 01:07:42 +00:00
gtk+-2.0.pc.in Remove spurious const. 2001-03-03 18:39:33 +00:00
gtk+.spec.in Move gtk-config to gtk-config-2.0 move gtk_.m4 to gtk-2.0.m4 2000-07-14 20:08:10 +00:00
HACKING
INSTALL Fix link to PNG home, remove reference to fribidi. 2000-12-05 20:53:30 +00:00
INSTALL.in Add check for db2html 2000-07-06 21:09:25 +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
Makefile.am gtk/gtkmain.c Use the new 2001-01-17 22:26:19 +00:00
NEWS Released 1.3.2 2000-11-18 01:49:13 +00:00
NEWS.pre-1-0
README Fix srcdir != builddir 2000-11-14 16:38:04 +00:00
README.cvs-commits
README.in
README.nanox make it possible to configure gtk for different targets on the same 2000-06-07 16:44:29 +00:00
README.win32 Update. Mention the gtk-1-3-win32-production branch. 2001-02-23 03:51:41 +00:00
sanity_check
TODO Spelling/grammar fixes from Martin Buchholz <martin@xemacs.org> 2000-02-29 13:15:10 +00:00
TODO.xml Another test commit TODO.xml 2000-10-29 02:44:07 +00:00

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

This is GTK+ version 1.3.2. 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.2

[ Please substitute 1.3.2 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.2

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".