ecc13fb5a5
2001-09-08 Havoc Pennington <hp@pobox.com> * gtk/gtk-docs.sgml: remove CellRendererTextPixbuf * gtk/resources.sgml: add section on mailing lists, bugzilla, etc. * gtk/tmpl/gtkaccelgroup.sgml: add long description * gtk/gtk-sections.txt: reorder accel group section; probably need to delete most of it * gtk/tmpl/gtkmain.sgml: Clean it up a little bit * gtk/gtk-docs.sgml: rearrange the list of "core/misc" sections so that useful things are near the top and stupid junk is near the bottom. * gtk/tmpl/gtkfeatures.sgml: fix/finish this section * gtk/gtk-docs.sgml: create a separate section for overview/tutorial material and special notes, and put the reference docs for the "misc non-widget" stuff into its own section. * gtk/compiling.sgml: write this section * gtk/gtk-docs.sgml: The intro section weirdly had two paragraphs that said the same thing. Delete one of them.
General Information =================== This is GTK+ version 1.3.7. 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.)