[Mono-osx] [ANN] mcocoa 0.7 and mobjc 0.8
martin.smith.jr at gmail.com
Thu Jan 7 22:00:02 EST 2010
Thanks for all your great work on these libraries... we use them and
love them. They've saved us a ton of time.
Out of curiosity, have you tried (or do you know if anyone has tried)
to use your libraries with objective-c 2.0 garbage collection enabled?
I've done some thinking about what it would take to get it to work,
and it seems theoretically possible.
On Tue, Dec 29, 2009 at 10:34 PM, Jesse Jones <jesjones at mindspring.com> wrote:
> mcocoa provides C# wrappers around nearly all of Apple's Foundation and AppKit frameworks. mobc is a bridge between Mono and Objective-C. Together these libraries allow you to write Cocoa applications using Mono. Unlike most other libraries mobjc properly handles exceptions arising in both managed and native code.
> The libraries can be found at:
> Changes to mcocoa include:
> * Updated to work with Snow Leopard.
> * Added hand-written versions of most of the foundation and appkit methods that take function pointers.
> * Added hand-written versions of about half the foundation and appkit methods that take blocks.
> * Instead of omitting deprecated methods from the generated code we now decorate them using ObsoleteAttribute.
> * Added an example which uses the quartz framework.
> Changes to mobjc include:
> * Added support for Objective-C blocks.
> * Static methods can now be registered with custom types. This works just like regular methods: the static method is registered if it starts with a lower case letter or if the method (instead of just the type) is decorated with RegisterAttribute.
> * SuperCall now takes a (super) class argument.
> * The exception message used when a method cannot be found was not properly including the type name.
> * Fixed the top call in the sample app so that it works on snow leopard.
> -- Jesse
> Mono-osx mailing list
> Mono-osx at lists.ximian.com
More information about the Mono-osx