 |
 |
What is the webcore interface?
|
|
|
|
|
Professional Poster
Join Date: Sep 2000
Location: San Francisco
Status:
Offline
|
|
The Apple dev pages say that webcore presents an ObjC interface. Is it possible to interact with it through C++ rather than ObjC? Can you interface directly with the KHTML rendering engine using C++ or do you have to go through the external webcore interface using ObjC?
kman
|
|
|
| |
|
|
|
|
|
|
|
Senior User
Join Date: Dec 2001
Status:
Offline
|
|
WebCore is not yet useable by third party developers. The source code has only been released because of LGPL requirements. When the final version of Safari is released, the Safari SDK will be released and (at least somewhat) documented by Apple.
|
|
"Think Different. Like The Rest Of Us."
iBook G4/1.2GHz | 1.25GB | 60GB | Mac OS X 10.4.2
Athlon XP 2500+/1.83GHz | 1GB PC3200 | 120GB | Windows XP
|
| |
|
|
|
|
|
|
|
Professional Poster
Join Date: Sep 2000
Location: San Francisco
Status:
Offline
|
|
Originally posted by macmike42:
WebCore is not yet useable by third party developers. The source code has only been released because of LGPL requirements. When the final version of Safari is released, the Safari SDK will be released and (at least somewhat) documented by Apple.
Can you elaborate on this? Will the Safari SDK be separate from WebCore? I'm assuming the Safari SDK will be for extending Safari and WebCore/JavaCore will be the APIs to the rendering engine.
kman
|
|
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: May 2002
Status:
Offline
|
|
WebKit (not WebCore, that's a lower level framework) is a part of the Safari SDK. You could, indeed, interact directly with KHTML, duplicating all of Apple's work in the creation of WebCore. The main problem is that you'd still need kwq to eliminate the qt dependence, and kwq is Cocoa.
|
|
[vash:~] banana% killall killall
Terminated
|
| |
|
|
|
|
|
|
|
Senior User
Join Date: Dec 2001
Status:
Offline
|
|
Originally posted by kman42:
Can you elaborate on this? Will the Safari SDK be separate from WebCore? I'm assuming the Safari SDK will be for extending Safari and WebCore/JavaCore will be the APIs to the rendering engine.
kman
Basically what Gul Banana (have I ever mentioned how much I love that nick?) said. The Safari SDK will include WebCore, JavaScriptCore, WebKit, and some half-decent (not ranking on Apple, just being realistic) documentation. Hopefully this will give Cocoa programmers something analagous to a NSWebView.
Like Gul said, you could theoretically interface with WebCore now, but you would be using a truly nasty combination of Objective-C and C++ to interface with an intertwined [mess] of Cocoa and QT/KDE code. Many people on Apple's cocoa-dev list have hacked around with it, and basically decided that if Apple releases the Safari SDK w/WebKit before the end of 2003, it would take less time to simply wait for it than to try to implement any kind of useable frontend by themselves.
|
|
"Think Different. Like The Rest Of Us."
iBook G4/1.2GHz | 1.25GB | 60GB | Mac OS X 10.4.2
Athlon XP 2500+/1.83GHz | 1GB PC3200 | 120GB | Windows XP
|
| |
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Mar 2000
Location: London, UK
Status:
Offline
|
|
The WebCore interface is, indeed, Obj-C and pretty much unusable. The current WebKit interface is Obj-C, too. It has been hinted at that the final Safari SDK release will have both an Obj-C/Cocoa API and a HIView-based C API for use in modern Carbon applications.
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
|
Top
