51–60 of 120 posts
This screenshot: http://kde.org/announcements/plasma5.0-beta2/plasma50b2-netw... Is this supposed to illustrate the "beta-ness" of the release? Because it's an atrocious UI. Two different-sized "wrench" icons next to each other? What are those checkboxes for? What does the little blue bar above the wireless symbol supposed to indicate? The blue lock is lost in the wireless icon in the network list (the eye is terribl…
This screenshot: http://kde.org/announcements/plasma5.0-beta2/plasma50b2-netw... Is this supposed to illustrate the "beta-ness" of the release? Because it's an atrocious UI. Two different-sized "wrench" icons next to each other? What are those checkboxes for? What does the little blue bar above the wireless symbol supposed to indicate? The blue lock is lost in the wireless icon in the network list (the eye is terribl…
Earlier quoted context omitted.
Actually more optimization is taking place than visual refreshes. Porting the stuff to Qt5 (esp. QtQuick2) should speed everything up on non-ancient PCs. Visual refreshes are just easier to explain. ;-)
Its not speed I'm bothered about. KDE is more or less very smooth at that. Its the resources it takes! The CPU is always nearly being utilized on a small-medium scale, and nearly 700mb is taken away at boot-time and gathers upto 2gb upon usage. That's too high, at least I think so. Would KDE actually require so much for all the features it gives or can that actually come down?
Is there an easy way with KDE4/dbus to get functionality similar to KDE3/dcop? Example task: 1) inspect running konsole task to find exposed interfaces 2) find one related to background colour 3) script up "change background colour to red in current konsole" command Last time I looked at the KDE+dbus situation (early KDE4) it seemed this was really hard.
For my part - ever since switching to i3, I can't really see myself using any other WM. Once I got used to not touching the mouse, I lost all desire to use a traditional mouse centric GUI.
Earlier quoted context omitted.
Its not speed I'm bothered about. KDE is more or less very smooth at that. Its the resources it takes! The CPU is always nearly being utilized on a small-medium scale, and nearly 700mb is taken away at boot-time and gathers upto 2gb upon usage. That's too high, at least I think so. Would KDE actually require so much for all the features it gives or can that actually come down?
Why would it matter if a piece of software uses CPU and RAM if it doesn't negatively affect the performance of the system?
Earlier quoted context omitted.
Actually more optimization is taking place than visual refreshes. Porting the stuff to Qt5 (esp. QtQuick2) should speed everything up on non-ancient PCs. Visual refreshes are just easier to explain. ;-)
Its not speed I'm bothered about. KDE is more or less very smooth at that. Its the resources it takes! The CPU is always nearly being utilized on a small-medium scale, and nearly 700mb is taken away at boot-time and gathers upto 2gb upon usage. That's too high, at least I think so. Would KDE actually require so much for all the features it gives or can that actually come down?
Can I press super/win-key, type [name of application], press enter and it brings up the [application]? It didn't when I last tried, and I don't want a window manager that doesn't behave in that way. Windows, Gnome shell and Unity does it - it's not hard.
Can I press super/win-key, type [name of application], press enter and it brings up the [application]? It didn't when I last tried, and I don't want a window manager that doesn't behave in that way. Windows, Gnome shell and Unity does it - it's not hard.