]> git.saurik.com Git - wxWidgets.git/blame_incremental - docs/html/faqgtk.htm
SWIGged updates for wxGTK
[wxWidgets.git] / docs / html / faqgtk.htm
... / ...
CommitLineData
1
2<HTML>
3
4<HEAD>
5<TITLE>wxWindows 2 for GTK FAQ</TITLE>
6</HEAD>
7
8<BODY BGCOLOR=#FFFFFF TEXT=#000000 VLINK="#00376A" LINK="#00529C" ALINK="#313063">
9
10<font face="Arial, Lucida Sans, Helvetica">
11
12<table width=100% border=0 cellpadding=3 cellspacing=0>
13<tr>
14<td bgcolor="#004080" align=left height=24 background="images/bluetitlegradient.gif">
15<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
16<b>wxWindows 2 for GTK FAQ</b>
17</font>
18</td>
19</tr>
20</table>
21
22<P>
23
24See also <a href="faq.htm">top-level FAQ page</a>.
25<hr>
26<h3>List of questions in this category</h3>
27<li><a href="#wxgtk">What is wxWindows 2 for GTK?</a></li>
28<li><a href="#gnome">Does wxGTK have GNOME support?</a></li>
29<li><a href="#redhat">Warning about GTK libraries supplied with RedHat</a></li>
30<li><a href="#wxgtk">What is wxWindows 2 for GTK?</a></li>
31<hr>
32
33wxWindows 2 for GTK is a port of wxWindows to the <a href="http://www.gimp.org/gtk" target=_top>GTK+ toolkit</a>,
34which is freely available for most flavours of Unix with X. wxWindows 2 for GTK is
35often abbreviated to wxGTK. wxGTK has a separate home page <a href="http://www.freiburg.linux.de/~wxxt" target=_top>here</a>.
36<P>
37
38<h3><a name="gnome">Does wxGTK have GNOME support?</a></h3>
39
40Currently wxGTK does not have any features that would involve dependence on any desktop
41environment&#39;s libraries, so it can work on GNOME, KDE and with other window managers
42without installation hassles. Some GNOME and KDE integration features are file based, and
43so may be added without dependence on libraries. Other features may be supported in the
44future, probably as a separate library.
45<P>
46
47<h3><a name="redhat">Warning about GTK libraries supplied with RedHat</a></h3>
48
49It seems that some versions of RedHat include a badly patched version of GTK (not wxGTK)
50which causes some trouble with wxWindows&#39; socket code. Common symptoms are that when
51a client tries to establish a connection to an existing server which refuses the request,
52the client will get notified twice, first getting a LOST event and then a CONNECT event.
53This problem can be solved by updating GTK with an official distribution of the library.
54<P>
55
56
57</font>
58
59</BODY>
60
61</HTML>