[Mono-osx] MacOS bindings and MonoDevelop.

Laurent Etiemble laurent.etiemble at gmail.com
Wed May 20 02:39:17 EDT 2009


My answers below:

Regards, Laurent Etiemble.

2009/5/19 Miguel de Icaza <miguel at novell.com>:
> Hello,
>> agreed on Monobjc as the best choice for the base, here.
> I am still concerned about a few things about MonoObjc:
>        * The copyrighted material from Apple included in the source.

I will remove the copyright content from the source, and publish it outside.

>        * It seems auto-generated, but the auto-generator is not public.

The basis of the wrappers has been auto-generated with various
scripts, but at the end, the result was mixed. So I have started
cleaning the API by hand, to make sure that the API was usable with

I do consider automatic generation only for getting a starting point,
and fixing by hand the remaining issues. That is why there is no
generator bundled with Monobjc.
I am still looking for a reliable generator to go with, that can
produce accurate API, Enumeration and Constants, for both Mac OS X
10.4 and 10.5.

>        * The bindings in a few areas are incomplete/wrong/incorrect or
> leaky.   I was looking in particular at the CoreGraphics APIs.

Can you elaborate on this point ? Please file a bug report with a test
case, so I can investigate the issue.

> For an internal Novell project that we are doing, we needed a full
> CoreGraphics binding.   We ended up going with a hand-wrapped API for
> now.
> Auto-generation can lead to that.   We have tried that with some APIs
> and we have got some mixed results in the past.

I agree.

> APIs need to be curated, and without the generator public, it seems
> difficult for an API of this size to get properly fixed and curated.
> Miguel.
> _______________________________________________
> Mono-osx mailing list
> Mono-osx at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-osx

More information about the Mono-osx mailing list