callisto-debian/gtk3 - gtk3 - Gitea: A self-hosted lightweight software forge

Go to file

Hans Breuer f0ee2996e1 updated externals 2001-06-22 Hans Breuer <hans@breuer.org> * gdk/gdk.def : updated externals * gdk/win32/gdkdrawable-win32.c : corrected some casts in GDK_NOTEs * gdk/win32/gdkevents-win32.c : use _gdk_windowing_window_get_offsets to translate coordinates to the internal > 16 bit system Try to handle WM_WINDOWPOSCHANGED to get better performance for when moving/resizing * gdk/win32/gdkkeys-win32.c : implement gdk_keymap_get_default () and gdk_keymap_get_direction (). The latter is untested for the RTL case * gtk/gtk.def : updated externals * gtk/gtkmain.c : gtk_get_default_language () should reurn the result from pango_language_from_string (), not an already freed pointer * gtk/stock-icons/stock_menu_sort_ascending.png : PNGs need to be binary (-kb) to be useable on windoze		2001-06-22 14:08:51 +00:00
contrib
debian
demos	fix bug identified by warnings I just added to gtktextbuffer	2001-06-14 22:29:48 +00:00
docs	Handle the case without XKB properly.	2001-06-21 17:45:26 +00:00
examples
gdk	updated externals	2001-06-22 14:08:51 +00:00
gdk-pixbuf
gtk	updated externals	2001-06-22 14:08:51 +00:00
m4macros
modules
po	updated Azeri file	2001-06-21 20:07:21 +00:00
tests	fix PROP_EVENTS.	2001-06-19 12:54:10 +00:00
.cvsignore
acconfig.h
acinclude.m4
AUTHORS
autogen.sh
ChangeLog	updated externals	2001-06-22 14:08:51 +00:00
ChangeLog.pre-1-0
ChangeLog.pre-1-2
ChangeLog.pre-2-0	updated externals	2001-06-22 14:08:51 +00:00
ChangeLog.pre-2-2	updated externals	2001-06-22 14:08:51 +00:00
ChangeLog.pre-2-4	updated externals	2001-06-22 14:08:51 +00:00
ChangeLog.pre-2-6	updated externals	2001-06-22 14:08:51 +00:00
ChangeLog.pre-2-8	updated externals	2001-06-22 14:08:51 +00:00
ChangeLog.pre-2-10	updated externals	2001-06-22 14:08:51 +00:00
config.guess
config.h.win32.in
config.sub
configure.in
COPYING
gdk-2.0-uninstalled.pc.in
gdk-2.0.pc.in
gdk-pixbuf-2.0-uninstalled.pc.in
gdk-pixbuf-2.0.pc.in
gtk-config-2.0.in
gtk+-2.0-uninstalled.pc.in
gtk+-2.0.pc.in
gtk+.spec.in
HACKING
INSTALL
INSTALL.in
makecopyright
Makefile.am
NEWS
NEWS.pre-1-0
README
README.cvs-commits
README.in
README.nanox
README.win32
sanity_check
TODO
TODO.xml

README

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

This is GTK+ version 1.3.6. 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/

Information about mailing lists can be found at
  http://www.gtk.org/mailinglists.html

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

See the file 'INSTALL'

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

Bugs should be reported to the GNOME bug tracking system. 
(http://bugzilla.gnome.org, product gtk+.) You will need
to create an account for yourself.
  
In the bug report please 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.

* 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 should also be submitted to bugzilla.gnome.org. If the
patch fixes an existing bug, add the patch as an attachment
to that bug report.

Otherwise, enter a new bug report that describes the patch,
and attach the patch to that bug report.

Bug reports containing patches should include the PATCH keyword
in their keyword fields. If the patch adds to or changes the GTK
programming interface, the API keyword should also be included.
  
Patches should be in unified diff form. (The -u option to GNU
diff.)