TDE frontend for power management
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

TODO 1.6KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748
  1. Currently we porting KPowersave to use HAL instead of the powersave daemon.
  2. ********************************************************************************
  3. For more information read this:
  4. http://dkukawka.blogspot.com/2006/10/kpowersave-development-for-next-stable.html
  5. or in general about the current state of development:
  6. http://dkukawka.blogspot.com/
  7. or the powersave-devel mailinglist archive:
  8. http://forge.novell.com/pipermail/powersave-devel/
  9. or at gmane.org:
  10. http://news.gmane.org/gmane.linux.power-management.powersave
  11. ********************************************************************************
  12. Currently TODOs: (except as TODO marked issues in the code)
  13. IMPORTANT:
  14. * related to new PolicyKit/ConsoleKit/HAL combination and 'Session'-handling:
  15. - fix scheme handling (don't set scheme if inactive, force correct scheme if
  16. active session again)
  17. - the running KPowersave instance can may not react as configured on empty/
  18. low battery if the session is inactive. May only a shutdown via KDE is
  19. possible.
  20. Think about this possible solutions:
  21. - fall back to shutdown via KDE on lowest battery level
  22. - drop org.freedesktop.Policy.Power interface and let powersaved to the
  23. job
  24. NORMAL:
  25. * fix suspend workflow, including:
  26. - handle errors (50 % done)
  27. * add code to react if KPowersave could not claim the
  28. org.freedesktop.Policy.Power interface from D-Bus
  29. * update doxygen files, remove/update tasks etc.
  30. * testing and bugfixing (always!)
  31. * check if there is room of improvment for:
  32. - reduce calls and set/force settings (partly done)