4 This is GTK+ version @GTK_VERSION@. 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 * GTK+ 2.6 supports clipboard persistency. To make use of this feature,
32 a clipboard manager following the specification at
33 http://www.freedesktop.org/wiki/Standards/clipboard-manager-spec
34 must be running. A sample implementation of such a clipboard manager
36 http://people.imendio.com/andersca/archives/clipboard-manager-0.3.tar.gz
37 Applications can use the function gdk_display_supports_clipboard_persistence()
38 to find out if clipboard persistence is available.
40 * Notification on clipboard ownership changes via GdkOwnerChange events
41 requires the XFIXES X extension. Applications can use the function
42 gdk_display_supports_selection_notification() to find out if ownerchip
43 change notification is available.
45 * The icon theme code in GTK+ 2.6 follows the freedesktop.org icon theme
46 specification. Setting the XDG_DATA_DIRS environtment variable may be
47 necessary if your icons aren't installed in the default location
50 * The icon theme code in GTK+ 2.6 can make use of mmap()able cache files
51 to avoid a lot of disk searching overhead. GTK+ includes a utility named
52 gtk-update-icon-cache to generate these cache files. For further details,
53 see the gtk-update-icon-cache man page or the GTK+ documentation.
55 * To reduce code size and improve efficiency, GTK+, when compiled
56 with the GNU toolchain, has separate internal and external entry
57 points for exported functions. The internal names, which begin with
58 IA__, may be seen when debugging a GTK+ program.
60 * The following functions have been deprecated in GTK+ 2.6:
61 gdk_pango_context_set_colormap
62 gtk_cell_renderer_editing_canceled
64 * The new GtkFileChooser widget emphasizes simplicity and thus does
65 not provide a navigation entry by default when opening files.
66 Experienced command line users will likely want to make heavy use of
67 the location dialog brought up by the Control-L key shortcut.
69 * The GTK+ libraries use an '_' prefix to indicate private symbols that
70 must not be used by applications. On some platforms, symbols beginning
71 with prefixes such as _gtk, _gdk, and _pango will be exported
72 from the library, on others not. In no case can applications
73 use these private symbols. In addition to that, GTK+ 2.6 makes several
74 symbols private which were not in any installed header files and
75 were never intended to be exported.
77 * The gdk_pixbuf_xlib library included in the contrib/ directory
78 and the framebuffer GDK backend included in the gdk/linux-fb directory
79 of GTK+ are provided on an as-is basis and have not been tested at all.
80 No guarantees about the degree of workingness or about future
81 compatibility are provided.
83 * On Unix, the assumption of GLib and GTK+ by default is that filenames on
84 the filesystem are encoded in UTF-8 rather than the encoding of the locale;
85 the GTK+ developers consider that having filenames whose interpretation
86 depends on the current locale is fundamentally a bad idea.
88 If you have filenames encoded in the encoding of your locale, then you
89 may want to set the G_FILENAME_ENCODING environment variable:
91 G_FILENAME_ENCODING=@locale
92 export G_FILENAME_ENCODING
94 (Earlier versions of GLib 2.x required a different environment variable
95 setting; G_BROKEN_FILENAMES=1 to achieve the same effect; this
96 is still supported, but G_FILENAME_ENCODING is preferred.)
97 Best integration of GTK+ 2.6 with the environment is achieved by
100 On Windows, filenames passed to GTK+ should always be in UTF-8, as
101 in GLib 2.6. This is different than in previous versions of GTK+
102 where the system codepage was used. As in GLib, for DLL ABI
103 stability, applications built against previous versions of GTK+ will
104 use entry points providing the old semantics.
106 When compiling against GTK+ 2.6, applications intended to be
107 portable to Windows must take the UTF-8 file name encoding into
108 consideration, and use the gstdio wrappers to access files whose
109 names have been constructed from strings returned from GTK+ or GLib.
114 Bugs should be reported to the GNOME bug tracking system.
115 (http://bugzilla.gnome.org, product gtk+.) You will need to create an
116 account for yourself.
118 In the bug report please include:
120 * Information about your system. For instance:
122 - What operating system and version
124 - For Linux, what version of the C library
126 And anything else you think is relevant.
128 * How to reproduce the bug.
130 If you can reproduce it with one of the tests or demos built with GTK+,
131 such as demos/gtk-demo/gtk-demo, that would be most convenient. Otherwise,
132 please include a short test program that exhibits the behavior. As a
133 last resort, you can also provide a pointer to a larger piece of software
134 that can be downloaded.
136 * If the bug was a crash, the exact text that was printed out when the
139 * Further information such as stack traces may be useful, but is not
140 necessary. If you do send a stack trace, and the error is an X error,
141 it will be more useful if the stacktrace is produced running the test
142 program with the --sync command line option.
147 Patches should also be submitted to bugzilla.gnome.org. If the patch
148 fixes an existing bug, add the patch as an attachment to that bug
151 Otherwise, enter a new bug report that describes the patch, and attach
152 the patch to that bug report.
154 Bug reports containing patches should include the PATCH keyword in their
155 keyword fields. If the patch adds to or changes the GTK+ programming
156 interface, the API keyword should also be included.
158 Patches should be in unified diff form. (The -u option to GNU diff.)