[Mono-osx] [ANN] mcocoa & mobjc libraries
ajbrehm at gmail.com
Wed Oct 29 05:26:16 EDT 2008
Does this mean that (by design at least) all Cocoa classes and GUI
elements are usable now?
Have they been renamed like in the old Cocoa# or do we finally have
NSString and NSArray to differentiate from .NET Strings and Arrays?
Does everything still work as it did with Cocoa#?
I'll try this out this weekend.
> Message: 8
> Date: Tue, 28 Oct 2008 16:31:17 -0700
> From: Jesse Jones <jesjones at mindspring.com>
> Subject: [Mono-osx] [ANN] mcocoa & mobjc libraries
> To: mono-osx at lists.ximian.com
> Message-ID: <1E7693F9-76FF-4228-964E-BF1EF8689042 at mindspring.com>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
> 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. These libraries are relatively efficient and unlike similar
> libraries properly handle exceptions in both directions. (These
> libraries were formerly called cocoa3-sharp and objc3-sharp).
> The libraries can be found at <http://code.google.com/p/mcocoa/> and <http://code.google.com/p/mobjc/
> mcocoa has been completely rewritten: instead of a handful of
> experimental hand-written wrappers the wrappers are now generated
> directly from Apple's headers.
> mobjc has been simplified quite a bit: the support for formatted
> method calls has been removed, Call methods return System.Object
> instead of Untyped, methods are decorated with the existing
> RegisterAttribute instead of NewMethodAttribute and
> OverrideMethodAttribute, public nullary/unary methods which start with
> a lower case letter are automatically registered, and the typing of
> values passed between managed and native code is not as forgiving.
More information about the Mono-osx