Linked by Thom Holwerda on Tue 4th Aug 2009 10:43 UTC
Thread beginning with comment 377013
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2005-07-11
That's the fault of the app developers, not the KDE devlopers. GTK doesn't play nicely with anything except GTK.
Yes it does. In KDE3 you use network-manager-kde. In KDE4, you use the Network Management plasmoid. They both hook into NetworkManager, giving you access to the same config database that network-manager-gtk and the cli version use.
Yes. In KDE4, you go into System Settings, into Multimedia, and set the preference for output in the Xine/Phonon config to use PulseAudio. You can also change the Phonon config to use GStreamer instead of Xine if you want.
Problem with that philosophy is that it's backwards. KDE devs bend over backwards to make KDE apps integrate and play nicely with GNOME technology. GNOME devs (seemingly) couldn't give two shits about making things work well with KDE technology.