[Mono-osx] Obj-C#, Cocoa# and bundles.
dru at druware.com
Tue Jan 22 20:00:59 EST 2008
What you want is very doable. I'll try to get some docs on how to together
in the next day or so.
On 1/22/08 5:37 PM, "Sijmen Mulder" <sjmulder at gmail.com> found the proper
letters on the keyboard to produce:
> Thanks for answering. (Great quote line by the way.)
> It's pretty clear. Just two more things. First, are there any samples
> on using ObjC#? Secondly, I'm still wondering about the app wrapping,
> whether it's possible to include all the mono-related dependencies
> inside an app bundle. To me that doesn't seem very app-specific.
> Op 22 jan 2008, om 23:12 heeft Andrew Satori het volgende geschreven:
>> The short answer is that ObjC# is a bridge from Objective C to
>> code, while Cocoa# is an implementation of the Cocoa API from
>> As for the rest, these are implementation details specific to your
>> needs and
>> I'll address them at a later date if you still have questions.
>> On 1/22/08 4:46 PM, "Sijmen Mulder" <sjmulder at gmail.com> found the
>> letters on the keyboard to produce:
>>> I was looking at the various options of using C# the Mac. There are a
>>> few things which haven't yet become clear to me from my research so
>>> far on the net:
>>> 1. What is the relationship between Obj-C# and Cocoa#? Looking at the
>>> samples, they seem to be two totally different projects.
>>> 2. Continuing on question 1, here is my case. I have an application
>>> that basically consists of a .NET DLL assembly, and a generic
>>> (doing the system work) for every specific platform. My idea was to
>>> write an Objective-C launcher/backend for the Mac (as opposed to
>>> Cocoa#), as I need to a few native libraries. The program should be
>>> able to access most of the .NET assembly. Note that it's Objective-C
>>> calling .NET here, not the other way around. No Cocoa classes need to
>>> be exposed to the .NET code. Are either Obj-C# or Cocoa# mature
>>> to do this? Which one would be the best option?
>>> 3. I'd like to provide my users with the best experience. To me, that
>>> means no dependency hell. Is there a way to wrap up mono and Obj-C#
>>> Cocoa# libraries (whatever is needed) in the application bundle, like
>>> with PyObjC for instance?
>>> 4. Anything else I should be aware of?
>>> Thanks a lot.
>>> Also, great work so far!
>>> Mono-osx mailing list
>>> Mono-osx at lists.ximian.com
> Mono-osx mailing list
> Mono-osx at lists.ximian.com
More information about the Mono-osx