Right now, the policies are more or less set by the system admin. He defines what happens on certain events, when certain battery levels are reached etc. The user/client can merely choose the provided schemes and set things like screensaver settings. IMO it would be a huge improvement if the client could set the actions for certain events or something like the battery levels himself. For this I would introduce an additional flag for the configuration files. I will call it "Overrides". Here you would specify what values the user should be able to override. Some examples.
## Path: System/Powermanagement/Powersave/Battery ## Type: integer(1:100) ## Overrides: integer(1:100) ## Default: "12" # User is allowed to override the value for the complete range BATTERY_WARNING="15" ## Path: System/Powermanagement/Powersave/Battery ## Type: integer(1:100) ## Overrides: integer(2:100) ## Default: "2" # Enfore a min value of 2 for a user provided setting BATTERY_CRITICAL="2" ## Path: System/Powermanagement/Powersave/Events ## Types string(notify,wm_shutdown,wm_logout,uspend_to_disk,suspend_to_ram ...) ## Overrides: string(suspend_to_disk, suspend_to_ram, ignore) # If the user wants to change the default settings he is only allowed to # choose from the given options EVENT_BUTTON_LID_CLOSED="suspend_to_ram" This would allow for a much more fine grained control over what is happening. As a first step you would have to identify a reasonable set of overridable variables and the set of allowed values and of course the support in the daemon and GUI client. Do you think that sound reasonable and feasible? Comments, alternate suggestions and criticism are welcome? Cheers, Michael
signature.asc
Description: OpenPGP digital signature
_______________________________________________ powersave-devel mailing list [email protected] http://forge.novell.com/mailman/listinfo/powersave-devel
