4 This is GTK+ version 2.4.0. GTK+ is a multi-platform toolkit for
5 creating graphical user interfaces. Offering a complete set of widgets,
6 GTK+ is suitable for projects ranging from small one-off projects to
7 complete application suites.
9 GTK+ is free software and part of the GNU Project. However, the
10 licensing terms for GTK+, the GNU LGPL, allow it to be used by all
11 developers, including those developing proprietary software, without any
12 license fees or royalties.
14 The official ftp site is:
15 ftp://ftp.gtk.org/pub/gtk
17 The official web site is:
20 Information about mailing lists can be found at
21 http://www.gtk.org/mailinglists.html
26 See the file 'INSTALL'
31 * The new GtkFileChooser widget emphasizes simplicity and thus does
32 not provide a navigation entry by default when opening files.
33 Experienced command line users will likely want to make heavy use of
34 the location dialog brought up by the Control-L key shortcut.
36 * As compared to GTK+-1.2, the default configuration of GTK+-2 has been
37 stream-lined to reduce confusion on the part of new users or users
38 coming from other environments. Users used to older versions of
39 GTK+ may want to make some adjustments to the default configuration.
41 - Emacs keybindings such as Control-A and Control-E to move to the
42 ends of lines are not enabled by default in the editing widgets. To
43 turn on Emacs keybindings, add the line:
45 gtk-key-theme-name = "Emacs"
49 - Editing of menu accelerators by pressing an accelerator over the
50 menu item is disabled by default. To enable, it, add:
52 gtk-can-change-accels = 1
56 - To improve useability for keyboard operation, GTK+ now selects the
57 contents of an entry when tabbing into it or when it is focused on
58 initial window map. To disable this behavior, add:
60 gtk-entry-select-on-focus = 0
64 * The GTK+ libraries use an '_' prefix to indicate private symbols that
65 must not be used by applications. On some platforms, symbols beginning
66 with prefixes such as _gtk, _gdk, and _pango will be exported
67 from the library, on others not. In no case can applications
68 use these private symbols.
70 * GTK+-2.4 now requires version 2 of Xft; old fashioned core X
71 fonts are no longer supported.
73 * There is a bug in the Xft library in XFree86-4.1 and possibly previous
74 versions that causes random crashes when using the Pango Xft
75 backend. If you want to use Xft fonts, you should upgrade to
78 * The gdk_pixbuf_xlib library included in the contrib/ directory of GTK+
79 is provided on a as-is basis and has not been tested at all. No
80 guarantees about the degree of workingness or about future
81 compatibility are provided.
83 * While efforts have been made to make gdk-pixbuf robust against
84 invalid images, using gdk-pixbuf to load untrusted data
85 is not recommended, due to the likelyhood that there are
86 additional problems where an invalid image could cause
87 gdk-pixbuf to crash or worse.
89 * The assumption of GLib and GTK+ by default is that filenames on the
90 filesystem are encoded in UTF-8 rather than the encoding of the locale;
91 the GTK+ developers consider that having filenames whose interpretation
92 depends on the current locale is fundamentally a bad idea.
94 If you have filenames encoded in the encoding of your locale, then
95 you may want to set the G_FILENAME_ENCODING environment variable:
97 G_FILENAME_ENCODING=@local
98 export G_FILENAME_ENCODING
100 (Earlier versions of GLib-2.x required a different environment variable
101 setting; G_BROKEN_FILENAMES=1 to achieve the same effect; this
102 is still supported, but G_FILENAME_ENCODING is preferred.)
103 Best integration of GTK+-2.4 with the environment is achieved by
104 using a UTF-8 locale.
109 Bugs should be reported to the GNOME bug tracking system.
110 (http://bugzilla.gnome.org, product gtk+.) You will need to create an
111 account for yourself.
113 In the bug report please include:
115 * Information about your system. For instance:
117 - What operating system and version
119 - For Linux, what version of the C library
121 And anything else you think is relevant.
123 * How to reproduce the bug.
125 If you can reproduce it with the testgtk program that is built in the
126 gtk/ subdirectory, that will be most convenient. Otherwise, please
127 include a short test program that exhibits the behavior. As a last
128 resort, you can also provide a pointer to a larger piece of software
129 that can be downloaded.
131 * If the bug was a crash, the exact text that was printed out when the
134 * Further information such as stack traces may be useful, but is not
135 necessary. If you do send a stack trace, and the error is an X error,
136 it will be more useful if the stacktrace is produced running the test
137 program with the --sync command line option.
142 Patches should also be submitted to bugzilla.gnome.org. If the patch
143 fixes an existing bug, add the patch as an attachment to that bug
146 Otherwise, enter a new bug report that describes the patch, and attach
147 the patch to that bug report.
149 Bug reports containing patches should include the PATCH keyword in their
150 keyword fields. If the patch adds to or changes the GTK programming
151 interface, the API keyword should also be included.
153 Patches should be in unified diff form. (The -u option to GNU diff.)