It all depends on the number of ui elements you have to convert. But
that aside moving from carbon to cocoa isn't as big as moving from
PowerPlant to cocoa IMHO, and no its not exactly the same. That will
make even the most enthusiastic engineer's sphincter pucker (not to
mention CodeWarrior to Xcode). Its fun but a lot of work and in fact
one of the projects I've worked on does, to this day, still have some
PowerPlant based ui in it. On that project we got to the point where
only if a ui element had been respecified did we convert it to cocoa
(shipping deadline, etc.).
The nice thing is with Objective-C++ you don't have to redo the
underlying code (for the most part at any rate).
I'm looking at this and thinking anytime you start talking about it
the entire discussion becomes parenthetical.
Milt
On Jun 09, 2005, at 13:17, Craig Hopson wrote:
I'd be interested in hearing any war stories about moving an
application from Carbon to Cocoa: what worked, what did not, big
wins, black holes, etc. Thanks!
-Craig
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
