faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: how about native Cocoa KDE port?
by Ranger Rick on Friday 02/Jan/2004, @19:38
|
Actually, Apple made a wrapper library that emulates Qt string types using native types and such without having to use Qt. KHTML doesn't really have any GUI code in it in the first place.
|
[
Reply To This | View ]
|
Re: how about native Cocoa KDE port?
by Tanner Lovelace on Friday 02/Jan/2004, @20:50
|
Safari does *not* use Qt at all. This is what it uses:
otool -L Safari
Safari:
/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 9.0.0)
/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 128.0.0)
/System/Library/Frameworks/WebKit.framework/Versions/A/WebKit (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook (compatibility version 1.0.0, current version 300.0.0)
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 19.0.0)
/System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 163.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 71.0.0)
Since I was curious, I also checked WebKit
otool -L WebKit
WebKit:
/System/Library/Frameworks/WebKit.framework/Versions/A/WebKit (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 19.0.0)
/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 128.0.0)
/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 9.0.0)
/System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/WebCore (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 500.1.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 71.0.0)
And, finally I checked WebCore
otool -L WebCore
WebCore:
/System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/WebCore (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 19.0.0)
/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 128.0.0)
/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 9.0.0)
/System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore (compatibility version 1.0.0, current version 1.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 71.0.0)
Those are the most likely places for it to be linking to Qt, if it used it, and as you can see, it doesn't use Qt at all. It does, however, use Cocoa and Carbon, which are the native Mac libraries.
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|