(Or thereabouts, since it’s obviously still there.) Why am I bothering to mention a dead development tool in the first place, particularly with Apple’s own Xcode included free with every copy of Mac OS X? Two reasons: first, we’ve already heard noted music developer Propellerhead complaining that their PowerPC code was faster on CodeWarrior than Apple’s Xcode. Metrowerks is no longer supporting the product (though they’ll still happily sell it to you unsupported - uh, thanks), and “after Q1 2006” you won’t be able to download at all. This week’s entry: it looks like CodeWarrior, the long-beloved Mac development tool, is nearly at its end. ![]() But I care about them (because I care about arcane things), and we’ll see if someone else does, too. It’s the arcane post of the week: Yes, this series will bring all the stories the fewest readers care about, direct to you. I’ll be moving happily over to Xcode! Thanks, vallen! Now all we need is someone from Apple marketing to say something snarky about how Xcode is more advanced than anything else on the planet, and anyone who uses anything else is a loser. ![]() Check out the new documentation, posted by David Zicarelli. Despite what the PDF documentation says in the Max/MSP SDK, you can now develop Mac externals using Xcode. ![]() Max/MSP and Xcode, correction: Okay, while it might be handy to have a copy of CodeWarrior around, I’m happy to say I was wrong about developing externals.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |