Nokia Releases KHTML Based Code to S60 Browser

Nokia has announced the release of the code to the web browser for their S60 phones. The browser is based on WebKit and KHTML. At Akademy last year the developers told us how they plan to be active Open Source contributors. It will be used on ESeries, NSeries devices and 3250 phones soon.

Dot Categories: 


by AC (not verified)

So, how close are WebKit and KHTML these days? Is this browser really "based on" KHTML, or is it more based on WebKit, a descendant of KHTML? Their press release only mentions Apple, not KDE, sadly.

S60WebKit and WebKit look close, since they share a repository, and a name. Is KHTML getting left behind?

by superstoned (not verified)

since Apple and KDE are cooperationg more closely through, webkit and KHTML aren't that different anymore, and when KHTML2 and the other enhancements to javascript etc are finished in KDE 4, Apple will start to use those as well.

by Carewolf (not verified)

Nope.. WebKit and KHTML are more different that ever. We do however share KJS implementation now.

Apple is not going to adapt anything major from KHTML, and KHTML2 is not even likely to be adapted by KHTML ;)

To clarify the relationship, Apple is also moving away from using the name KHTML in WebCore.

by Peppelorum (not verified)

Two completely different answers, can someone clear this out?

by Charles de Miramon (not verified)

Could you elaborate Allan ?

I clearly don't understand KDE strategy with KHTML (if we have any strategy). Why is it not possible for KDE4 to have Konqueror use either Webkit, either KHTML ?

by SadEagle (not verified)

WebKit doesn't provide most of the APIs any more. Nor would it build with any Qt or KDE version.

by blacksheep (not verified)

Of course, WebKit is GUI independent. But how hard would it be to make a KDE frontend?

by germain (not verified)

Quite hard and for hardly any benefit.
The only compelling advantage of WebKit at this point is the editing functionalities. Porting those to KHTML is a much easier and desirable path.

As for rendering and ecma, it's pretty much a tie. There are a *lot* of bugfixes and some functionalities that have not made it into WebCore at all, since they are not making any backporting effort, whereas we do.

WebKit enhancements have been very limited in the past 6 monthes, as they needed to go cross platform and basically turned their finests into windows programmers (poor guys!).

by jimmie (not verified)


by AC (not verified)

Should KDE standardize on Webkit, then?

by Charles de Miramon (not verified)

If I understand correctly the situation. What would be needed, would be to split KHTML between a glue interface between the HTML engine and Qt and the HTML engine. Then we could choose either Webkit or the revamped KHTML or KHMTL2 for the engine.

by AC (not verified)

Are there any plans to do that? Does anybody know what the KHTML roadmap is?

by Fede (not verified)

They do mention KDE, just not directly on that article. But if you navigate to, as they suggest in the end, KDE and Konqueror are mentioned on the first Paragraph.

The title makes it sound like they're doing something incredibly generous . Aren't they forced to do so given the LPGL license of KHTML and so Webkit? and by the way, how can Nokia relicense something LGPL under BSD? it's a little confusing there

by Roberto Alsina (not verified)

They are forced to release their version of Webkit (which is, of course, their version of KHTML as well).

They are not forced to release the actual browser. For example, Apple is not releasing Safari as open source.

it looks like the nokia browser is not floss, but they do release a floss api and a floss implementation of the browser that is ReferenceUI Reindeer. is that it?

It seems that KHTML had nothing to win by being licensed under the Lesser GPL (LGPL). In other words, KHTML and KDE developers got the short end of the stick, while big business opportunists like Apple took advantage of KHTML without lifting a finger to help it and give back. Apple did the _very least_ they could get away with under the LGPL, which was obviously not enough for KDE developers to improve KHTML for the benefit of FOSS users:

So why continue to SUCK UP to DRM-loving big business by releasing KHTML and KDE-libs code under the LGPL, when you can fight for Freedom and for the users' rights by licensing _all_ your code under the GPL, the license with the strongest copyleft protections?

Nonsense. Nokia have done what the LGPL asks them to do. What else do you want? Do you want them to come round to your house and cook your dinner for you too? If that's what the LGPL was meant to achieve, then it would say so.
KDE has benefited a lot from Webkit. Stop being an FSF troll!

by Cobarde anónimo (not verified)

You are a troll, too.
Who do you think created the LGPL?
Stallman's FSF, of course.

by Alistair John S... (not verified)

Agreed 100%. Apple are worse than Microsoft; instead of just competing with open source, they rip us off.

The LGPL might be arguably too tame, but at least KDE didn't make the mistake of licensing very important technologies under an artistic license (alarmingly much of KDE is under these licenses).