Linked by Thom Holwerda on Tue 10th Aug 2010 22:00 UTC, submitted by JRepin
KDE KDE today celebrates its semi-annual release event, releasing new versions of the Plasma Desktop and Netbook workspaces, the KDE Development Platform and a large number of applications available in their 4.5.0 versions. In this release, the KDE team focused on stability and completeness of the desktop experience.
Thread beginning with comment 436174
To read all comments associated with this story, please click here.
KHTML
by evert on Wed 11th Aug 2010 06:10 UTC
evert
Member since:
2005-07-06

I'm baffled that it takes so much effort to get webkit in KDE, because webkit is kind of a child (fork) of KHTML. But I did not study the code, so I must assume that apple really changed a lot.

Reply Score: 2

RE: KHTML
by Tuxie on Wed 11th Aug 2010 08:31 in reply to "KHTML"
Tuxie Member since:
2009-04-22

IIRC it's a concious decision to keep KHTML instead of switching to Webkit. I'm not sure why, it's probably a control (or pride?) thing. They regularly import code from Webkit into KHTML though.

Update: Maybe I should read TF announcement before commenting... ;) It seems that they ARE integrating Webkit now.

Edited 2010-08-11 08:34 UTC

Reply Parent Score: 1

RE[2]: KHTML
by lemur2 on Wed 11th Aug 2010 12:31 in reply to "RE: KHTML"
lemur2 Member since:
2007-02-17

IIRC it's a concious decision to keep KHTML instead of switching to Webkit. I'm not sure why, it's probably a control (or pride?) thing. They regularly import code from Webkit into KHTML though.

Update: Maybe I should read TF announcement before commenting... ;) It seems that they ARE integrating Webkit now.


Yes. Apparently the default renderer for Konqueror is still KHTML, but Webkit may now be chosen instead.

The word is that Kubuntu are considering making rekonq the default browser for Maverick, and this decision may have prompted the Konqueror authors to now allow this choice.

Reply Parent Score: 3

RE[2]: KHTML
by Fettarme H-Milch on Wed 11th Aug 2010 12:58 in reply to "RE: KHTML"
Fettarme H-Milch Member since:
2010-02-16

KHTML is being kept, because it's part of kdelibs4 which KDE guaranties full binary compatibility for.

Reply Parent Score: 4

RE: KHTML
by mart on Wed 11th Aug 2010 08:45 in reply to "KHTML"
mart Member since:
2005-11-17

webkit can be used in konqueror quite easily instead of khtml
or check rekonq that is a webkit based browser with a pretty and minimal ui

Reply Parent Score: 2

RE: KHTML
by tyrione on Wed 11th Aug 2010 09:40 in reply to "KHTML"
tyrione Member since:
2005-11-21

I'm baffled that it takes so much effort to get webkit in KDE, because webkit is kind of a child (fork) of KHTML. But I did not study the code, so I must assume that apple really changed a lot.


You're baffled? They had to wait for Qt to have their port of WebKit solid and ready to be KDE'ified.

Reply Parent Score: 1

RE: KHTML
by Carewolf on Wed 11th Aug 2010 11:51 in reply to "KHTML"
Carewolf Member since:
2005-09-08

Integration is hard. If people would just realized that, so many projection mistakes could be avoided.

Both programmers and non-programmers have a strong tendency to underestimate the work that goes into integration. And they don't just underestimate with a factor of 2 or 4 like is common for development projects in general. No, integration is typically underestimated by a factor of 10 if not a 100.

Add to that, that integration is incredibly dull work, and due to it being underestimated doesn't earn you any credit and in fact, doing this work is more likely to get you flamed at, bitched at, yelled at, and in the private sector: fired.

Reply Parent Score: 4