[Gtk-sharp-list] How the developments of gtksharp and gtk+ interact?
alp at atoker.com
Wed Mar 21 12:28:56 EDT 2007
Rafael Teixeira wrote:
> "The other way, C# to C, is not posible, thought."
> Not quite right. GTK+ has some extension mechanisms: the problems are:
> 1) You need to code a C-wrapping library to conform to GTK+ APIs (the
> reverse of what gapi does to generate GTK# from GTK+)
> 2) As keeping the managed bits out-of-process for the widgets seems a
> bad solution (both in security/performance), probably you also need to
> embed mono in the wrapping library.
The "cilc" CIL-to-C binding generator tool which ships with Mono has
explicit GObject support. This means that it can tie a Gtk# widget
subclass into the Gtk+ object hierarchy. Some areas like event-to-signal
mapping, interfaces and properties aren't that well tested but it more
than works as proof of concept.
I think that if you channel the time saved by writing widgets in C# back
into cilc and submit the patches, you would save time overall and help
bring a neat little tool to the wider developer community.
More information about the Gtk-sharp-list