| 1 | General Information |
|---|
| 2 | =================== |
|---|
| 3 | |
|---|
| 4 | This is GTK+ version 1.2.10. GTK+, which stands for the Gimp ToolKit, |
|---|
| 5 | is a library for creating graphical user interfaces for the X Window |
|---|
| 6 | System. It is designed to be small, efficient, and flexible. GTK+ is |
|---|
| 7 | written in C with a very object-oriented approach. |
|---|
| 8 | |
|---|
| 9 | The official ftp site is: |
|---|
| 10 | ftp://ftp.gtk.org/pub/gtk |
|---|
| 11 | |
|---|
| 12 | The official web site is: |
|---|
| 13 | http://www.gtk.org/ |
|---|
| 14 | |
|---|
| 15 | Information about mailing lists can be found at |
|---|
| 16 | http://www.gtk.org/mailinglists.html |
|---|
| 17 | |
|---|
| 18 | Installation |
|---|
| 19 | ============ |
|---|
| 20 | |
|---|
| 21 | See the file 'INSTALL' |
|---|
| 22 | |
|---|
| 23 | How to report bugs |
|---|
| 24 | ================== |
|---|
| 25 | |
|---|
| 26 | Bugs should be reported to the GNOME bug tracking system. |
|---|
| 27 | (http://bugzilla.gnome.org, product gtk+.) You will need |
|---|
| 28 | to create an account for yourself. |
|---|
| 29 | |
|---|
| 30 | In the bug report please include: |
|---|
| 31 | |
|---|
| 32 | * Information about your system. For instance: |
|---|
| 33 | |
|---|
| 34 | - What operating system and version |
|---|
| 35 | - What version of X |
|---|
| 36 | - For Linux, what version of the C library |
|---|
| 37 | |
|---|
| 38 | And anything else you think is relevant. |
|---|
| 39 | |
|---|
| 40 | * How to reproduce the bug. |
|---|
| 41 | |
|---|
| 42 | If you can reproduce it with the testgtk program that is built |
|---|
| 43 | in the gtk/ subdirectory, that will be most convenient. Otherwise, |
|---|
| 44 | please include a short test program that exhibits the behavior. |
|---|
| 45 | As a last resort, you can also provide a pointer to a larger piece |
|---|
| 46 | of software that can be downloaded. |
|---|
| 47 | |
|---|
| 48 | * If the bug was a crash, the exact text that was printed out |
|---|
| 49 | when the crash occured. |
|---|
| 50 | |
|---|
| 51 | * Further information such as stack traces may be useful, but |
|---|
| 52 | is not necessary. If you do send a stack trace, and the error |
|---|
| 53 | is an X error, it will be more useful if the stacktrace |
|---|
| 54 | is produced running the test program with the --sync command |
|---|
| 55 | line option. |
|---|
| 56 | |
|---|
| 57 | Patches |
|---|
| 58 | ======= |
|---|
| 59 | |
|---|
| 60 | Patches should also be submitted to bugzilla.gnome.org. If the |
|---|
| 61 | patch fixes an existing bug, add the patch as an attachment |
|---|
| 62 | to that bug report. |
|---|
| 63 | |
|---|
| 64 | Otherwise, enter a new bug report that describes the patch, |
|---|
| 65 | and attach the patch to that bug report. |
|---|
| 66 | |
|---|
| 67 | Bug reports containing patches should include the PATCH keyword |
|---|
| 68 | in their keyword fields. If the patch adds to or changes the GTK |
|---|
| 69 | programming interface, the API keyword should also be included. |
|---|
| 70 | |
|---|
| 71 | Patches should be in unified diff form. (The -u option to GNU |
|---|
| 72 | diff.) |
|---|
