AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity
GTK is a multi-platform toolkit for creating graphical user interfaces.
754 Commits 969 Branches 749 Tags 504 MiB
C 90.4%
CSS 7.9%
Meson 0.5%
SCSS 0.4%
JavaScript 0.3%
Other 0.3%
218e61990c
Go to file
Tim Janik 218e61990c now what is this? whoi left a '>' in line 628???
1998-05-10 07:55:48 +00:00
debian Removed debian/files for real 1998-03-24 04:42:55 +00:00
docs update of Italian tutorial translation from Daniele Canazza 1998-05-09 15:35:18 +00:00
examples Changed LGPL address for FSF in all .h and .c files 1998-04-13 02:02:47 +00:00
gdk now what is this? whoi left a '>' in line 628??? 1998-05-10 07:55:48 +00:00
glib bugfixes, cleanups and macro reduction, nothing major though ;) 1998-05-10 07:44:43 +00:00
gtk bugfixes, cleanups and macro reduction, nothing major though ;) 1998-05-10 07:44:43 +00:00
tests Try to figure out if this is Digital Unix and we need -std1 to get the 1998-05-10 02:46:20 +00:00
.cvsignore Removed gtk+-xconfig added gtk-config 1998-03-13 01:52:51 +00:00
acconfig.h new file used as template for new file to define macros indicating newly 1998-05-09 01:17:03 +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 bugfixes, cleanups and macro reduction, nothing major though ;) 1998-05-10 07:44:43 +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 bugfixes, cleanups and macro reduction, nothing major though ;) 1998-05-10 07:44:43 +00:00
ChangeLog.pre-2-2 bugfixes, cleanups and macro reduction, nothing major though ;) 1998-05-10 07:44:43 +00:00
ChangeLog.pre-2-4 bugfixes, cleanups and macro reduction, nothing major though ;) 1998-05-10 07:44:43 +00:00
ChangeLog.pre-2-6 bugfixes, cleanups and macro reduction, nothing major though ;) 1998-05-10 07:44:43 +00:00
ChangeLog.pre-2-8 bugfixes, cleanups and macro reduction, nothing major though ;) 1998-05-10 07:44:43 +00:00
ChangeLog.pre-2-10 bugfixes, cleanups and macro reduction, nothing major though ;) 1998-05-10 07:44:43 +00:00
config.guess Initial revision 1997-11-24 22:37:52 +00:00
config.h.in bugfixes, cleanups and macro reduction, nothing major though ;) 1998-05-10 07:44:43 +00:00
config.sub Initial revision 1997-11-24 22:37:52 +00:00
configure.in Try to figure out if this is Digital Unix and we need -std1 to get the 1998-05-10 02:46:20 +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 Handle the -1.1 on libraries. 1998-05-07 18:33:29 +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 The auto_shrink policy of the floating window is now set to TRUE. This 1998-01-28 03:41:55 +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 Feature request ;) 1998-05-05 07:45:59 +00:00

README 

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