3 <p>Currently Windows.Forms support is under development. Check Mono's <a
4 href = "http://www.go-mono.com/mono-roadmap.html">Roadmap</a> for more
5 details on when it is going to be available.
7 <p>System.Windows.Forms in Mono is implemented using System.Drawing and
8 Wine. This allows applications that use P/Invoke to call Win32 functions
9 or rely on event delivery through the Wndproc method to work as
10 expected. This is the path of best compatibility.
12 <p>In terms of integrating visually with the desktop, we are hoping to
13 contribute to the Wine project a mechanism to make it use the Gtk+
14 themes on X11 and Cocoa on MacOS to render the widgets, and get the
15 native look and feel on each of these platforms.
19 <p>To get the Windows.Forms support working, you need:
23 <li> The latest <a href = "http://www.go-mono.com/download.html">Mono</a> package.
24 <li> The latest <a href = "http://www.go-mono.com/download.html">libgdiplus</a> library.
25 <li> The latest <a href = "http://www.cairographics.org/download">Cairo</a> vector graphics library.
26 <li> A recent copy of <a href="http://www.winehq.com/">Wine</a>.
27 <li> A recent copy of WineLib (do a cvs co winelib from Mono's CVS).
33 <p>The Winforms effort is being coordinated in the <a
34 href="mailto:mono-winforms-list@ximian.com">mono-winforms-list@ximian.com</a>.
35 If you are interested in helping out with this effort,
36 subscribe to it by sending an email message to <a
37 href="mailto:mono-winforms-list-request@ximian.com">mono-winforms-list-request@ximian.com</a>.
39 <p>If you want to help, you can pick a control and start implementing it's
40 methods. You can do this either on Windows or on Linux. Try using
41 System.Drawing calls instead of P/Invoked Win32 calls.
43 <p>If you choose a particular control to work on, send a note to the
44 winforms list to avoid duplication of effort.
49 <p>For details, see the <a
50 href="drawing.html">System.Drawing implementation notes</a>
51 section of the web site.