Technical stuff, XRandR, Udev, helper... Smooth brightness change Try to avoid double brightness changing (some hardware is wired in a way that it does not require us to actually change the brightness, but we still have to show the osd)
Technical stuff, upower? udev as well?
Types of inhibition, api, fd.o spects Note to myself: fd.o spec should inhibit dimming as well ?
Technical info, most probably port to xcb
Technical info (suspend vs hibernation vs hybrid)
What should happen by default? and when you plug a monitor?
Showing menu by default?
Should we agresively restore settings like we are doing right now? or should we trust the user knows what it wants every time? Should we restore everything but brightness?
Power Management is a tricky matter, we need it to be extensible so all use cases can be fit. for example, executing a script when AC is disconnected.
We need multiple backends, a clear example of it is KDE Connect. Question is, how do we want them to look like? First idea is Binary plugins, just good old QLibrary but that might be dangerous given that an in correct written plugin might break all app's linking to libsolidpower.
Another idea would be create some kind of DBus api that people can use to add batteries, it could even have the same API UPower have... just in different service/path. This will be safe and will allow third parties to create batteries in a safe way.
PowerDevil has a backend architecture that should be moved into a library which allows to perform the operations that currently are possible in those backends.
A great example of what should be avoided is The Solid::PowerManagement API, which relays on having powerdevil running to support different backends.