Linked by Thom Holwerda on Wed 10th Jan 2007 23:55 UTC
Gnome The GNOME team has released GNOME 2.17.5. "This is our fifth development release on our road towards GNOME 2.18.0, which will be released in March 2007. This is also the release which marks the start of the API/ABI freeze for the platform and the start of the feature freeze."
Thread beginning with comment 200731
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Gnome, C, and KDE
by sirhomer on Thu 11th Jan 2007 17:27 UTC in reply to "Gnome, C, and KDE"
sirhomer
Member since:
2007-01-03

I like KDE technically but hate them philopshically. KDE has this dendency to reinvent the wheel everytime they want to add some feature. For instance, KDE uses their own HTML ("KHTML") rendering engine, while GNOME uses the better Mozilla "Gecko" rendering engine. They will reinvent something some complicated like an HTML rendering engine (more complicated then Qt), but hell if they will make their own widget engine. No, do not touch the holy Qt. ;) No disrespect to the KHTML team btw.

Edited 2007-01-11 17:31

Reply Parent Score: 3

RE[2]: Gnome, C, and KDE
by dindin on Thu 11th Jan 2007 17:39 in reply to "RE: Gnome, C, and KDE"
dindin Member since:
2006-03-29

I don't think Gecko is the better engine. As a foreign language speaker, it has several issues rendering Unicode properly (take a look at their bug posts). KHTML is very tightly integrated with Qt rendering. I am quite disappointed with this since Pango is one of the best technologies out their for multi-linguale enablement and while Firefox can be compiled/made to use it, its layout output does not seem to properly made use of by the firefox display engine. A native Gtk based HTML rendering engine would be much better.

Reply Parent Score: 0

RE[3]: Gnome, C, and KDE
by anda_skoa on Thu 11th Jan 2007 18:22 in reply to "RE[2]: Gnome, C, and KDE"
anda_skoa Member since:
2005-07-07

KHTML is very tightly integrated with Qt rendering.

Ah, well. It has been ported to Cocoa (Apple WebKit) and GTK (WebKit GTK backend by Nokia).

You call that tightly integrated with Qt rendering?

Edited 2007-01-11 18:25

Reply Parent Score: 5

RE[2]: Gnome, C, and KDE
by aseigo on Thu 11th Jan 2007 20:20 in reply to "RE: Gnome, C, and KDE"
aseigo Member since:
2005-07-06

khtml predates gecko and continues to provide us with features and use possibilities gecko simply can't. this is why apple, nokia, adobe and others use it as well.

as for reinventing wheels, we just tend to get to new ground first. most times it's other people ignoring what we've done and doing their own thing. personally i don't have a big problem with that.

but your assertion really falls apart badly when you look at kde4 where we dropped dcop for dbus (improving the latter dramatically in the process, btw), dropped aRts for a wrapper over 3rd party back ends (aka Phonon), have done the same for hardware detection, ditto for voip and presence, same for spelling and grammar checking, or how we continue to move forward aggressively with ODF instead of our own office file formats, etc, etc... where we end to do our own thing is when the alternatives simply aren't viable for our needs.

kde is actually one the most open projects when it comes to collaboration. and that's a statement backed by code you can download today.

Reply Parent Score: 5

RE[3]: Gnome, C, and KDE
by Hiev on Thu 11th Jan 2007 22:44 in reply to "RE[2]: Gnome, C, and KDE"
Hiev Member since:
2005-09-27

khtml predates gecko and continues to provide us with features and use possibilities gecko simply can't.


like what?

Reply Parent Score: 1