Transitioning to Cocoa from Carbon
Quote from Forum Archives on May 9, 2010, 4:00 pmPosted by: fblistserve <fblistserve@...>
Since this list is slow, I hope this general question isn’t too much of a bother.My goal is to migrate a large code bases to Cocoa ( currently using Carbon nibs and C as built by FB5 ) but leverage the existing code as much as possible without having to replace all Carbon C with Objective-C/Cocoa
Phase 1 ( almost complete ) changes all internal processing to Core Foundation.
Before taking a next transition step, I’m wondering if anyone has used the C wrapper functions for Cocoa methods ( as described in Apple’s “Carbon-Cocoa Integration Guide” - which includes using HICocoaView ) to transition their own code. Obviously, this makes it easier to leverage code because it is still Carbon but I’m wondering if this is a good transition step or possibly complicates matters later when code is converted to Objective-C/Cocoa nibs.
Brian S.
Posted by: fblistserve <fblistserve@...>
My goal is to migrate a large code bases to Cocoa ( currently using Carbon nibs and C as built by FB5 ) but leverage the existing code as much as possible without having to replace all Carbon C with Objective-C/Cocoa
Phase 1 ( almost complete ) changes all internal processing to Core Foundation.
Before taking a next transition step, I’m wondering if anyone has used the C wrapper functions for Cocoa methods ( as described in Apple’s “Carbon-Cocoa Integration Guide” - which includes using HICocoaView ) to transition their own code. Obviously, this makes it easier to leverage code because it is still Carbon but I’m wondering if this is a good transition step or possibly complicates matters later when code is converted to Objective-C/Cocoa nibs.
Brian S.