Originally posted by Awesomeness
View Post
And as a recent “convert” you suddenly obtained all knowledge about KDE?
Your claim is absolutely false and I can easily prove it: https://projects.kde.org/oxygen-gtk
Your claim is absolutely false and I can easily prove it: https://projects.kde.org/oxygen-gtk
And I do acknowledge they have gotten a lot better about using tools with platform momentum in recent times, be it pulseaudio, dbus, or gstreamer. And oxygen-gtk is just a gtk port of the default theme, it isn't major systemic infrastructure like what I meant, and of course there are exceptions, its open source. I'm talking about how Phonon and Gstreamer ran parallel for a while, and are now mingling. I can get behind the sentiment of something like "I like gnome-system-monitor, but our desktop doesn't have GTK dependencies, so we will write our own in qt, and expect it to be better for our choice of toolkit, so heres KGuard".
KDE’s current approach is to either integrate GTK applications as well as possible via Oxygen-GTK or to write a KDE front-end on an existing back-end (as with LightDM, NetworkManager, PackageKit, etc.)
In fact the main reason why there is no broad push for a KDE web browser (Konqueror and Rekonq are basically one-man shows these days) is that most KDE devs simply use Firefox or Chrome.
In fact the main reason why there is no broad push for a KDE web browser (Konqueror and Rekonq are basically one-man shows these days) is that most KDE devs simply use Firefox or Chrome.
And I actually liked the ideas behind Konqueror as a universal resource explorer. I do think it is a good thing projects like Rekonq are downplayed because the best way to make KDE better is to focus on the aspects of the experience that don't have tremendous market competitors where you try to tuffle with giants. It is like how Totem is mediocre next to VLC because it is just another part of Gnome vs VideoLan being entirely centered around VLC.
That's because the current keyboard shortcut implementation is lacking and IIRC cannot easily be fixed without breaking binary compatibility. I believe it’s on the agenda to be fixed in KF5. The current implementation can’t handle two alternatives for global shortcuts. Therefore a default that works also with keyboards without multimedia keys is chosen.
Again: Distributors can change such defaults to target a specialized user group (e.g. one that has a higher likelihood of owning such keyboards).
Again: Distributors can change such defaults to target a specialized user group (e.g. one that has a higher likelihood of owning such keyboards).
Comment