trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2012

Re: [trinity-devel] UPower support added in tdebase/ksmserver

From: Calvin Morrison <mutantturkey@...>
Date: Thu, 16 Feb 2012 12:08:35 -0500
On 16 February 2012 12:07, Serghei Amelian <serghei@...> wrote:
> On Thursday 16 February 2012 18:04:13 Ilya Chernykh wrote:
>> On Thursday 16 February 2012 20:55:10 Serghei Amelian wrote:
>> > Now I consider to create something like ksmserver, which will handle all
>> > things related to power, and will expose a DCOP API to user applications.
>>
>> Now kpowersave does the thing, i.e. the DCOP API.
>
> Right. But kpowersave still using HAL. Also, kpowersave is an applet, if is
> not started, cannot be used. I think a service is much better.
>
>
> --
> Serghei.

kpowersave does have a interface already though look at it's public interface:

QCStringList interfaces()
QCStringList functions()
bool lockScreen()
bool do_setScheme(TQString)
bool do_setCPUFreqPolicy(TQString)
bool do_suspendToDisk()
bool do_suspendToRAM()
bool do_standBy()
bool do_brightnessDown(int percentageStep)
bool do_brightnessUp(int percentageStep)
void disableAutosuspend(bool)
void showDetailedDialog()
bool openConfigureDialog()
bool currentSchemeManagesDPMS()
int brightnessGet()
TQString currentScheme()
TQString currentCPUFreqPolicy()
TQStringList allowed_sleepingStates()
TQStringList listSchemes()
TQStringList listCPUFreqPolicies()

basically we need all of that, in a daemon.

Right?

Calvin