Apple Win32 to OS X Porting Guide

BoomerSooner writes "Apple has released a Win32 to Mac OS X Porting Guide for C/C++ developers. This Guide is to get you started porting an existing procedural Win32 application written in C or C++ to Mac OS X. It looks like Apple is getting a bit more aggressive toward Microsoft."

Comments

Huh?

[phillymjs]

That's funny. I'm on a Mac and yet my mouse has two buttons and a scroll wheel that can be a 3rd button.

And what are these "floppies" of which you speak?

~Philly

Re:Oops

[glwtta]

Hit the wrong 'reply' link.

Getting confused by all the buttons? ;)

Re:Marklar

[Twirlip of the Mists]

The ultimate aggressive move would be to release Marklar, the x86 version of Mac OS X.

I'm sorry, but I think you typed "aggressive" when you meant to type "suicidal."

It's a common mistake. The keys are right next to each other.

Re:Step #1

[ajiva]

Get this

It does wonders for cross-platform development

Great!

[JoshuaDFranklin]

Soon we will be able to use Cygwin on MacOSX!

Well, as long as those lazy open-source developers hurry up and follow the guidelines.

A little draconian, no?

[mbogosian]

From the guide: You will use Interface Builder to translate your application's visual appearance into the visual appearance of a well-designed Mac OS X application.

You don't need to see his interface specification. These aren't the design elements you're looking for. He can go about his development.

You win

[dalangalma]

You know, your compelling argument has shown me the way. I mean... *I* have one butt, why shouldn't my mouse? And it should definitely match the color of my CPU - that dark silicon sheen is pretty sexy.

What's a floppy?

[kitzilla]

Ask your wife.

Okay, I'm sorry. But you did post AC, after all. ;-)