3 System.Windows.Forms eventually will support multiple
4 toolkits. Ximian will be delivering a product that will allow
5 for System.Windows.Forms applications to integrate with GNOME
6 through Gtk and MacOS X using Cocoa.
8 There are no current plans to support embedded devices, but
9 Gtk/FrameBuffer is an option. If you have suggestions or
10 recommendations, please let us <a
11 href="mailto:mono-hackers-list@ximian.com">let us know</a>
15 Currently Ximian developers are busy making our JIT engine
16 feature complete, and dealing with the low-level details of
19 If you are interested in contributing, you can start stubbing
20 out classes and providing enumerations. That will help us
21 significantly when we start working on the actual bindings.
23 Christian Meyer is currently organizing this effort.
27 Using existing libraries to implement some of the functionality required
30 * gdk-pixbuf is a generic image loader that loads an image
31 and leaves it into an RGB buffer. It hides all the details
32 about what image file format is being loaded.
34 * Libart is a general framework for rendering RGB/RGBA
35 buffers into RGB buffers and rendering postscript-like paths into
39 We want to use gdk-pixbuf as the image loader for the image
40 classes, and then we need operations to render that into the
41 windowing system (Gtk+, MacOS, etc). But notice how there is
42 very little dependnecies in Gdk-pixbuf on gtk, and libart has
45 They are pretty independent from a windowing system
46 (gdk-pixbuf comes with some "helper" routines for rendering
47 data into a pixmap and to load pixmaps into RGB buffers).
49 A few things to keep in mind:
53 * gdk-pixbuf can be used to load images for Gtk+,
54 MacOS X and Windows, it should be pretty portable,
55 although we might need in the future to back-port
56 some new features from Gtk head.
58 * Libart is probably only going to be used with X11,
59 as the MacOS X provides the same features in Quartz,
60 and Win32 *probably* has that in GDI+. If not, we
61 should use libart in Win32 as well (or for older
67 System.Drawing (assembly directory)
69 Common code for "Blah"
70 Stubs for "Blah" to ease ports.
74 Gtk ports of "System.Drawing.Blah"
77 MacOS ports of "System.Drawing.Blah"
80 Win32 ports of "System.Drawing.Blah"
82 Then we use nant targets to include/exclude the right set of
83 files to create the assembly.
87 I believe that the graphics contexts that are used to render
88 can accept either libart-like rendering operations and
89 X11-like rendering operations. This complicates matters, but
90 I am not sure. Someone needs to investigate this.