Surfin’ Safari

Recently Zack Rusin posted about the first version of a Qt/KDE API for WebKit, plus some cool screenshots of neat things you can do with it.

Two days ago Lars and I sat down and did the initial implementation of classes which will represent the public API for the Qt/KDE version of WebKit. In KHTML almost everything has been handled by KHTMLPart. We’d like to avoid having one huge object that does everything this time so we went with similar abstraction to the one present in WebCore - meaning Page/Frame distinction. The top level classes are now: QWebPage which represents (surprise - a web page) and QWebFrame which is (another shocking discovery) a frame (remember that a page can have multiple frames).

Looks like the Qt backport of WebKit is making good progress.

You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.