On Sunday, October 02, 2011 20:31:11 Dario Freddi wrote: > I don't think so. Every other system does a similar thing: there is no > use in saving battery when you're on AC, when you are on battery > these components are turned off. I don't think this should be > configurable at all, and to a certain mean it is: you can always > re-enable the service in the system tray with a single click. The > user doesn't need to do anything at all here and can simply trust his > system to do the right thing.
In this part we agree, that's why I said that with good defaults, configuration might not be needed. > > > > What I said that I might manually need to switch to a different > > > > profile independent of what the battery power *currently* is and > > > > without switching my workflow/applications. Because I know in > > > > advance (before the software can find this out from the battery > > > > level dropping down) how much time I need the computer running. > > > > > > But apparently you don't know what it takes to save power. > > > > Do I have to really know? I just want to save power. And do that > > whenever I want, not when the computer decides. Thats the whole > > point. > No offense meant, but this one made me laugh. If you don't know what > it takes to save power, you should trust me when I say some things > are not going to help you. Just like in the first case, this is about configurations, while both my and others mails were about two issues: - chosing a preset configuration whenver you want - creating presets And here I talked about the first. The software might know better what is the best to save power, and I might know when it should save power. How it does (turning off brightness, setting kernel argument in /proc or whayever) is not relevant - that's why Is said should i really know?), from the user pov. I hope this makes clear what I meant. Andras _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
