[Mono-osx] Monobjc and mobjc, confusion, duplicate work?

[Eugeny Grishul]

Hi. There is another one - NObjective ( http://code.google.com/p/objcmapper/
) =)

Cocoa# is most ancient binding with bad project architecture/performance.

mcocoa/mobjc have more performance and additionally can provide exception
propagation in both directions - from managed to unmanaged world and vise
versa.

monobjc have most complete documentation and it's main goal to make
objective-c more .NET-compliant. but still lacking exception propagation (
currently monobjc is pure .NET solution ). Also it provides non-objc
bindings for Mac OS X.

NObjective targeted to experienced Cocoa developers who need near-native
performance and more natural objc syntax to write their .NET programs. It
has most complete objc class coverage, efficient exception propagation,
highest performance and ability to generate proxies even for user-defined
frameworks. If you want to improve my work ( NObjective ) you can contact
with me via email ( see project page ).


Andrew Brehm wrote:
> 
> I am getting more and more confused over Monobjc and mobjc and mcocoa and
> cocoa#.
> 
> How many of these projects are ongoing and is work being duplicated or is
> there some communication between the groups?
> 
> And how can I (rather incompetent programmer but very enthusiastic user)
> help?
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Monobjc-and-mobjc%2C-confusion%2C-duplicate-work--tp20599230p20606576.html
Sent from the Mono - OSX mailing list archive at Nabble.com.