Yeah, that's my thought. It's obvious with things like Core* that they're trying to migrate to a single code base *eventually*, the question was whether that would be Core* with two wrapper APIs, or a unified system with a deprecated API, and a preferred API.
This *might* indicate that they're going with the latter, when it was pretty well assumed by many people that the former was the foreseeable future. Settling on a single API that has more legs for future opportunities makes sense.
The question is... how to do it successfully? We had Carbon as the 'fill-in' API that took on a life of its own, are they now getting to the point where, finally, they can start moving towards the original vision?
It's already possible to mix Carbon and Cocoa APIs, if you're careful, right?
Focusing on Cocoa and depreciating (but not breaking) Carbon seems like the next logical step to improve OS X development.
Yes. You don't even have to be 'careful', it's pretty easy.
The only problem is that you need to compile using Objective-C (for C applications) or Objective-C++ (for C++), and I'm curious if as to how this effects cross-platform compatibility.
I'm assuming if you set up a WIndows IDE to interpret ".m" (ObjC) and ".mm" (ObjC++) files as C and C++ files, respectively, and set the precompiler to ignore any ObjC code, you should be fine, but I've never made a Windows program.
Just to add more information... the WWDC Session descriptions are up (or at least the ones that they're announcing publicly so far): http://developer.apple.com/wwdc/sessions/
Search for Carbon on that page.
One session: Carbon Feedback Forum.
That's it. Cocoa everywhere, that's it for Carbon.
Just to add more information... the WWDC Session descriptions are up (or at least the ones that they're announcing publicly so far): http://developer.apple.com/wwdc/sessions/
Search for Carbon on that page.
One session: Carbon Feedback Forum.
That's it. Cocoa everywhere, that's it for Carbon.
Hmm.
I noticed that too. As several have said, it does seem like the next logical step. A single (or at least overwhelmingly-paramount) API could be a good thing. I hope this means QTKit will be maturing rapidly.
Carbon, the set of APIs built upon Classic MacOS and used by most 3rd party high-profile Mac OS X applications, now allows Cocoa views to be embedded into the application. This could provide applications like Photoshop and Microsoft Office access to advanced functions previously only available to Cocoa applications.
Lots more there too, but the above relates specifically to this thread.
Comments
Focusing on Cocoa and depreciating (but not breaking) Carbon seems like the next logical step to improve OS X development.
This *might* indicate that they're going with the latter, when it was pretty well assumed by many people that the former was the foreseeable future. Settling on a single API that has more legs for future opportunities makes sense.
The question is... how to do it successfully? We had Carbon as the 'fill-in' API that took on a life of its own, are they now getting to the point where, finally, they can start moving towards the original vision?
Originally posted by Hobbes
It's already possible to mix Carbon and Cocoa APIs, if you're careful, right?
Focusing on Cocoa and depreciating (but not breaking) Carbon seems like the next logical step to improve OS X development.
Yes. You don't even have to be 'careful', it's pretty easy.
The only problem is that you need to compile using Objective-C (for C applications) or Objective-C++ (for C++), and I'm curious if as to how this effects cross-platform compatibility.
I'm assuming if you set up a WIndows IDE to interpret ".m" (ObjC) and ".mm" (ObjC++) files as C and C++ files, respectively, and set the precompiler to ignore any ObjC code, you should be fine, but I've never made a Windows program.
Search for Carbon on that page.
One session: Carbon Feedback Forum.
That's it. Cocoa everywhere, that's it for Carbon.
Hmm.
I bet the Carbon Feedback Forum will be quite lively.
Originally posted by Kickaha
Just to add more information... the WWDC Session descriptions are up (or at least the ones that they're announcing publicly so far): http://developer.apple.com/wwdc/sessions/
Search for Carbon on that page.
One session: Carbon Feedback Forum.
That's it. Cocoa everywhere, that's it for Carbon.
Hmm.
I noticed that too. As several have said, it does seem like the next logical step. A single (or at least overwhelmingly-paramount) API could be a good thing. I hope this means QTKit will be maturing rapidly.
(Love the user name, btw)
Three whole sessions for Carbon (http://developer.apple.com/wwdc/schedules/):
Carbon Feedback Forum
Carbon Programming Hands-on
Cocoa for Carbon Developers
Aaaaaaand that's all folks.
Carbon, the set of APIs built upon Classic MacOS and used by most 3rd party high-profile Mac OS X applications, now allows Cocoa views to be embedded into the application. This could provide applications like Photoshop and Microsoft Office access to advanced functions previously only available to Cocoa applications.
Lots more there too, but the above relates specifically to this thread.
I'd love to hear why Carbon was almost MIA from the schedule.
Of course, I'd love to see a filled-out schedule.