View Single Post
Posts: 462 | Thanked: 550 times | Joined on Sep 2008 @ Moscow
#210
Originally Posted by Benson View Post
Is 0.3.5 going to use its own algorithm for estimating runtime left, then? Or am I missing something?
I'm still thinking about own time left algorithm (TLA)... On the one hand it would great not to deal with Nokia's time left stuff anymore, on the other hand... On the other hand AP is splitting into 2 packages:
- Advanced Power Monitor (APM) (a daemon (still written in Python, but C looks more and more attractive), which gets all the info and uses D-Bus to notify about changes and get values). Mainly for cross-project and cross-application usage. I want to keep APM lightweight as much as it can be using Python for such things.
- Advanced Power (GUI's statusbar item).
That splitting is my #1 at the moment. To my mind implementing a statistics based TLA is the thing to be done, but I'm not sure, if it gonna be in APM-0.3.5, may be in APM-0.3.6.
In fact ideas about other possible algorithms are welcomed