On 18. Aug 2018, at 20:19, Stephane Sudre <dev.iceb...@gmail.com> wrote: > Regarding the complexity of porting from C++ Carbon to Cocoa, there's > also the important question of what your minimum OS target is. > > Maybe one of the reasons why you kept a Carbon version alive so long > is that the application needs to keep working on older OS versions. > > Porting to OS X 10.10 or later is not the same thing as porting to > 10.6 or later for instance.
+1. I think we pretty much only supported whatever the current OS version was in our Cocoa ports. We had the Carbon versions in parallel that supported the older OSes, so it wasn't as if users would notice. There were significant improvements over macOS releases. Particularly 10.2 and 10.8, IIRC. I haven't had to Carbon-port much later than that. ... well, that's not true, I did a rough Carbon-to-Cocoa port for a friend about a year ago, but that was just getting the basics to work and solving the hard issues (like adding certain modifications he needed to standard views to Cocoa, in a Cocoa way), and hasn't shipped yet. Cheers, -- Uli Kusterer "The Witnesses of TeachText are everywhere..." http://www.zathras.de _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
