[Mono-osx] Cocoa# customization
Fri, 22 Apr 2005 08:24:22 +1000
My Question is about the internal of Cocoa#, how does it work? what kind of
interop should you used to tap in ObjectiveC class?
calling a C function is straight enough: [DllImport] but how do you call
At least I would like to understand that (I haven't really lookede at it
yet, really busy on some other things so far).
I see you have a coed generator.
Could it be you just generate a C library to call each function and .NET
classes doing simple interop to the method?
Any clarification would be welcome!
----- Original Message -----
From: "Andreas Ringdal" <firstname.lastname@example.org>
To: <email@example.com>; <firstname.lastname@example.org>;
Sent: Friday, April 22, 2005 2:51 AM
Subject: Re: [Mono-osx] Cocoa# customization
I'm not quite shure if I understand your question.
Cocoa# is mac only and will not help you in converting an existing
application to windows.
På 21. apr. 2005 kl. 07.49 skrev Lloyd Dupont:
> I'm completely new to Cocoa# (but not to ObjectiveC, C# & Interop) and
> wonder how it works.
> I will have to port some MacOSX application to WIndows.
> Here's is how we see it:
> the main data classes are in ObjectiveC and common to both OSes (using
> GNUstep/MingW on Windows).
> Then I would like to use something like Cocoa#, but interfacing GNUStep
> FoundationKit and our ObjectiveC data classes to .NET (as smoothly as
> possibl: i.e. without, or with the less, human intervention possible).
> Then I will use this regular .NET classes in my .NET/Winform application.
> It's a bit tricky but the MacOSX application is already big and evolving!
> SO, here is my question again: roughly how does Cocoa# work? how could I
> do that?
> (Yep, I'm going to investigate by myself very soon, but any help,
> pointers, links, etc.. would be welcome!)
> Mono-osx mailing list
tel: 98 22 18 75
Mono-osx mailing list