[Mono-osx] Delphi Prism and all those Cocoa bridges

Andrew Brehm ajbrehm at gmail.com
Tue Feb 24 14:34:20 EST 2009

I hope the quoting isn't messed up. I find it weird that a Web interface to a
mailing list archive would use a different quoting scheme than mail

marc hoffman-4 wrote:
> Andrew,
>> I find Delphi more convincing every time I read about it! Ever since
>> the .NET Rocks podcast episode about Prism I was sort of hooked.
> glad to hear that. i believe we have a lot of cool stuff in Prism that  
> sets it apart from C# - not just it's support for Mono(objc). For  
> example, have a look at our upcoming support for AOP:
> http://blogs.remobjects.com/blogs/mh/2009/02/06/p253 
>   (shows on an example that's very relevant to Monobjc, too ;)

I'll be busy with other stuff until May. If until then I hear two more good
things about Prism, one of which related to Cocoa, I'll buy it! :-) Your
example up there doesn't count for the two.

If you guys add more support for Cocoa (Monobjc), that's exactly what I am
looking for. And learning Delphi cannot be more unproductive than learning
REALbasic. :)

(I understand Delphi Prism just adds itself to an existing installation of
Visual Studio Professional if found?)

marc hoffman-4 wrote:
>> I think we are getting somewhere.
>> I am looking for a way to write applications that are portable between
>> Windows and Mac OS X, ideally use Cocoa, and are garbage-collected.
> very doable, yes. one of the things i was thinking about just today  
> was doing a nice sample that (aided by a variation of the Aspect i  
> describe in the blog post above) would show an application that has a  
> WPB MVVM and a Monobjc Cocoa frontend both based on the same  
> modelview. (The aspect would publish the properties according to KVO  
> when using Monobjc, and as bindable properties for WPF, when using  
> that...

I managed to write a program in C# that checks the platform it's running on
and uses Cocoa on Mac OS X and Windows Forms on Windows. It was an
interesting exercise but it's ultimately useless as the NIB file required
the program to be in a Mac bundle anyway and it cannot be shipped that way
on Windows.

Hence two or three different binaries will be the way to go. (Is there a way
to use #IFDEF to organise those different build settings in the source?)

marc hoffman-4 wrote:
>> I am sure it will change. I think there is a positively huge market
>> for decent cross-platform applications.
> i believe so too, yes.

There is more demand for Mac applications than ever, I think. And with .NET
we are a good step closer to cross-platform code.

marc hoffman-4 wrote:
>> I'd be content with a Visual Studio plug-in that supports Mono and
>> Monobjc. But I am willing to spend money and learn Delphi if this is
>> the best way for me to get what I want. I liked Turbo Pascal.
> inside VS, i dare say that is the best option, yes. Until we can ship  
> our MD support...

Do you know if this will be a separate product or something that can be used
by existing Delphi Prism customers?

View this message in context: http://www.nabble.com/Delphi-Prism-and-all-those-Cocoa-bridges-tp22180106p22188884.html
Sent from the Mono - OSX mailing list archive at Nabble.com.

More information about the Mono-osx mailing list