[KDE/Mac] [Interest] Carbon obsolete

[Rutledge Shawn]

On 20 Jan 2015, at 13:29, René J.V. Bertin <rjvbertin at gmail.com> wrote:

> On Tuesday January 20 2015 12:56:50 Ian Wadham wrote:
> 
> Hi,
> 
>>>>> I've made a number of patches to KDE4 that rely on
>>>>> that header, and KDE uses Carbon itself.
>>>> 
>>>> One hopes not, since Carbon is gone post-10.6 except for backward
>>>> compatibility for ancient apps.
>>> 
>>> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon is linked by
>>> both libkdeui.dylib and
>>> /opt/local/libexec/qt4/Library/Frameworks/QtGui.framework/QtGui
> 
>> Here is a more glaring example.  Shiny new code in Qt 5 (i.e. our friend QStandardPaths,
>> QSP for short) is using Carbon in a central supporting role for apps dependent on Qt5 ---
>> i.e. all Qt5 apps, all KF5 apps (from KDE), etc.
> 
>> "It looks as though QSP has started to move to using the COCOA library to find file types, which
>> is why qstandardpaths_mac.cpp has become qstandardpaths_mac.mm in Qt 5.4 source code.
>> Is "mm" short for "mix and match"?… :-)  Anyway, QSP is now using code that is a mix of C++
> 
> Heh, .mm is ObjC++. That's kinda mix and match indeed, but not really what it stands for.
> 
>> and Objective C, with use of both Cocoa and Carbon ATM.  And QSP might change some
>> more in later versions of Qt 5."
> 
>> It may be time to nip this continuing use of Carbon by Qt and KF5 in the bud --- but where to start?
> 
> One would probably start by rounding up all uses of Carbon calls. And query the Qt devs to what extent they have a timeline for the migration.
> 
> And one can only hope that a good part of the KDE4 functionality that relied on Carbon has been moved to Qt and will thus benefit automagically from Qt's severing of (from?) Carbon. 

Sounds good to me.  Now that we are dropping 10.6 support, it ought to be easier.

Patches welcome, as usual.  ;-)