GTK is a multi-platform toolkit for creating graphical user interfaces.
Go to file
Elliot Lee bcecbbd1be Add \n's on the end of g_prints in the mem profiling code.
Add \n's on the end of g_prints in the mem profiling code.
1998-06-05 21:00:15 +00:00
debian Removed debian/files for real 1998-03-24 04:42:55 +00:00
docs minor changes to support auto extraction of example code 1998-06-02 12:08:14 +00:00
examples New files to automagically extract code examples from the tutorial. 1998-06-04 11:15:55 +00:00
gdk New enumeration for the "mode" field of crossing events. (struct 1998-05-27 02:01:40 +00:00
glib Add \n's on the end of g_prints in the mem profiling code. 1998-06-05 21:00:15 +00:00
gtk reversed test sequence for GTK_WIDGET_CAN_FOCUS and GTK_IS_CONTAINER 1998-06-02 19:32:33 +00:00
tests Added function gtk_clist_swap to swap two rows in a clist; I also have 1998-06-02 02:51:46 +00:00
.cvsignore Removed gtk+-xconfig added gtk-config 1998-03-13 01:52:51 +00:00
acconfig.h Basic thread-awareness: 1998-05-16 02:13:12 +00:00
AUTHORS removed unneeded GtkCTree::draw_lines (gtk_ctree_get_node_info): New 1998-05-01 23:45:18 +00:00
autogen.sh I got sick of typing in the same commands over and over, so borrowed 1998-01-31 17:43:56 +00:00
ChangeLog New files to automagically extract code examples from the tutorial. 1998-06-04 11:15:55 +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 New files to automagically extract code examples from the tutorial. 1998-06-04 11:15:55 +00:00
ChangeLog.pre-2-2 New files to automagically extract code examples from the tutorial. 1998-06-04 11:15:55 +00:00
ChangeLog.pre-2-4 New files to automagically extract code examples from the tutorial. 1998-06-04 11:15:55 +00:00
ChangeLog.pre-2-6 New files to automagically extract code examples from the tutorial. 1998-06-04 11:15:55 +00:00
ChangeLog.pre-2-8 New files to automagically extract code examples from the tutorial. 1998-06-04 11:15:55 +00:00
ChangeLog.pre-2-10 New files to automagically extract code examples from the tutorial. 1998-06-04 11:15:55 +00:00
config.guess Initial revision 1997-11-24 22:37:52 +00:00
config.h.in Basic thread-awareness: 1998-05-16 02:13:12 +00:00
config.sub Initial revision 1997-11-24 22:37:52 +00:00
configure.in Bombo out with a moderately helpful message if detection of X libraries 1998-05-24 02:48:09 +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 postfix -lg* libraries with LT_RELEASE. 1998-05-07 04:04:15 +00:00
gtk.m4 minor cleanups and merges 1998-05-10 05:19:00 +00:00
gtk+.spec Set package version to 1.0.4 in anticipation of upcoming release. 1998-06-04 16:04:09 +00:00
HACKING Updated package versions 1998-04-14 01:10:04 +00:00
INSTALL postfix -lg* libraries with LT_RELEASE. 1998-05-07 04:04:15 +00:00
install-sh Initial revision 1997-11-24 22:37:52 +00:00
ltconfig Merged changes from gtk-1-0. Check ChangeLog for details. 1998-05-01 04:23:59 +00:00
ltmain.sh postfix -lg* libraries with LT_RELEASE. 1998-05-07 04:04:15 +00:00
makecopyright Changed LGPL address for FSF in all .h and .c files 1998-04-13 02:02:47 +00:00
Makefile.am ooops, fogot this on my last commit... 1998-05-07 07:45:04 +00:00
Makefile.in Define GTK_HAVE_RC_SET_IMAGE_LOADER, to be used in gnome-libs 1998-05-22 23:43:03 +00:00
missing Initial revision 1997-11-24 22:37:52 +00:00
mkinstalldirs Initial revision 1997-11-24 22:37:52 +00:00
NEWS bugfixes, cleanups and macro reduction, nothing major though ;) 1998-05-10 07:44:43 +00:00
NEWS.pre-1-0 ooops, fogot this on my last commit... 1998-05-07 07:45:04 +00:00
README postfix -lg* libraries with LT_RELEASE. 1998-05-07 04:04:15 +00:00
stamp-h.in Initial revision 1997-11-24 22:37:52 +00:00
TODO new file, gdatasets implement the object data mechanism from GtkObject. a 1998-05-11 00:48:44 +00:00

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

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

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