GTK is a multi-platform toolkit for creating graphical user interfaces.
Go to file
1999-01-13 19:24:20 +00:00
debian Argh. Missed one dumb space in rules file. Fixed. 1998-11-18 06:25:35 +00:00
docs Released GTK+ 1.1.12 1999-01-04 11:04:11 +00:00
examples Update the following sections to the current API: - Container Widgets - 1998-12-13 22:25:07 +00:00
gdk Add a drag_data_received handler for the label. 1999-01-12 23:27:30 +00:00
gdk-pixbuf Stuff I did last night while watching TV 1999-01-05 21:27:07 +00:00
gtk eliminate queue_clears or queue_draws where we know that expose events 1999-01-13 12:39:17 +00:00
po updated spanish language file 1999-01-13 19:24:20 +00:00
tests Add a drag_data_received handler for the label. 1999-01-12 23:27:30 +00:00
.cvsignore cvs be quiet 1999-01-13 19:17:08 +00:00
acconfig.h eliminate queue_clears or queue_draws where we know that expose events 1999-01-13 12:39:17 +00:00
acinclude.m4 Doah. libtool isn't the only thing in here. 1999-01-13 08:44:21 +00:00
AUTHORS s,Fedrerico Mena,Federico Mena, 1998-12-24 12:33:19 +00:00
autogen.sh rm -rf intl breaks --disable-nls, put it back 1998-12-17 05:21:45 +00:00
ChangeLog eliminate queue_clears or queue_draws where we know that expose events 1999-01-13 12:39:17 +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-2-0 eliminate queue_clears or queue_draws where we know that expose events 1999-01-13 12:39:17 +00:00
ChangeLog.pre-2-2 eliminate queue_clears or queue_draws where we know that expose events 1999-01-13 12:39:17 +00:00
ChangeLog.pre-2-4 eliminate queue_clears or queue_draws where we know that expose events 1999-01-13 12:39:17 +00:00
ChangeLog.pre-2-6 eliminate queue_clears or queue_draws where we know that expose events 1999-01-13 12:39:17 +00:00
ChangeLog.pre-2-8 eliminate queue_clears or queue_draws where we know that expose events 1999-01-13 12:39:17 +00:00
ChangeLog.pre-2-10 eliminate queue_clears or queue_draws where we know that expose events 1999-01-13 12:39:17 +00:00
config.guess acinclude.m4 ltconfig upgrade to libtool 1.2d (with fixes for irix6 and 1999-01-13 06:53:26 +00:00
config.sub acinclude.m4 ltconfig upgrade to libtool 1.2d (with fixes for irix6 and 1999-01-13 06:53:26 +00:00
configure.in added spanish language file 1999-01-10 18:32:14 +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 Add @INTLLIBS@. gtk-scier-981116-0.patch Sean Cier 1998-12-18 01:32:33 +00:00
gtk.m4 gtk.m4: When testing to see if glib exists, set LIBS="$GTK_LIBS $LIBS" NOT 1998-12-31 21:01:18 +00:00
gtk+.spec Released GTK+ 1.1.12 1999-01-04 11:04:11 +00:00
HACKING Added gettext-10.35 1998-12-14 17:39:58 +00:00
INSTALL Released GTK+ 1.1.12 1999-01-04 11:04:11 +00:00
install-sh updated to latest automake version 1998-09-18 02:07:42 +00:00
ltconfig acinclude.m4 ltconfig upgrade to libtool 1.2d (with fixes for irix6 and 1999-01-13 06:53:26 +00:00
ltmain.sh acinclude.m4 ltconfig upgrade to libtool 1.2d (with fixes for irix6 and 1999-01-13 06:53:26 +00:00
makecopyright Changed LGPL address for FSF in all .h and .c files 1998-04-13 02:02:47 +00:00
Makefile.am Released GTK+ 1.1.11 1998-12-31 02:25:58 +00:00
missing updated to latest automake version 1998-09-18 02:07:42 +00:00
mkinstalldirs updated to latest automake version 1998-09-18 02:07:42 +00:00
NEWS Released GTK+ 1.1.12 1999-01-04 11:04:11 +00:00
NEWS.pre-1-0 ooops, fogot this on my last commit... 1998-05-07 07:45:04 +00:00
README Released GTK+ 1.1.12 1999-01-04 11:04:11 +00:00
README.cvs-commits Fixed argument list and return type for non-XIM fallback. 1998-12-09 18:13:52 +00:00
sanity_check configure.in: require GLib 1.1.5 1998-11-23 03:07:50 +00:00
stamp-h.in eliminate queue_clears or queue_draws where we know that expose events 1999-01-13 12:39:17 +00:00
TODO reverted bogus and undocumented!!! changes from Jay Cox (98/11/23 1998-11-26 03:43:24 +00:00

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

This is GTK+ version 1.1.12.   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
==================

To report a bug, send mail either to gtk-list, as mentioned
above, or to gtk-bugs@gtk.org. If you send mail to gtk-list, you
must be subscribed yourself.

In the mail include:

* The version of GTK

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

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