batlevel 2.1-1
A QT based widget to display battery level
Styles and colors can be changed using settings now.
Polling interval can be changed to keep minimum impact on power consumption.
The widget stops polling when screen is off to save battery.
On tapping the battery icon , it displays more detailed information as
shown by the hal-device bme command.
Homepage:
Section:
user/desktop
Repository:
Depends:
libc6 (>= 2.5.0-1), libdbus-1-3 (>= 1.1.4), libdbus-glib-1-2 (>= 0.76), libgcc1 (>= 4.2.1), libgconf2-6 (>= 2.13.5), libglib2.0-0 (>= 2.20.0), libqt4-maemo5-core (>= 4.6.2~git20100203), libqt4-maemo5-dbus (>= 4.6.2~git20100203), libqt4-maemo5-gui (>= 4.6.2~git20100203), libqt4-maemo5-maemo5 (>= 4.6.2~git20100203), libqt4-maemo5-network (>= 4.6.2~git20100203), libqt4-maemo5-xml (>= 4.6.2~git20100203), libstdc++6 (>= 4.2.1), libx11-6
Warning: This package has missing dependencies!
Warning: Promotion of experimental Qt based applications (qt4-maemo5 and qt4-experimental) is blocked due to conflicts. See this post for more information. If you want to promote your application, you should repackage it so it uses libqt4 instead of libqt4-maemo5 or libqt4-experimental. The builder now defaults to PR1.3 which has libqt4 (4.7.0)
Status:
Package has been removed
Bugtracker:
Warning: This package does not have the required bugtracker link specified!
QA Quarantine ends:
ENDED 2010-02-17 21:15
| Tester | Karma | Timestamp |
| rama kurvakat (Maintainer) (413) | 2010-02-20 01:15 UTC | |
| Willie Pretorius (Tester) (314) | 2010-02-19 22:41 UTC | |
| Mustali Dalal (Tester) (995) | 2010-02-07 23:26 UTC |
Package events
| Event type | User | Timestamp |
| Package has been removed | System | 2010-07-01 10:33 UTC |
| Package imported | System | 2010-06-30 14:45 UTC |
| Package has been removed | System | 2010-06-30 14:26 UTC |
| Promotion rejected | System | 2010-02-20 01:14 UTC |
| Package is in testing | System | 2010-02-07 19:15 UTC |
Comments:
As mentioned, this version is not to be tested. I have released newer versions with a bugzilla page for the bug tracking. Hence Ive voted down so this can be demoted so I can promote the newer version.
About the battery not showing full, thats not the problem of the app, refer to the bug 7636 for details.
https://bugs.maemo.org/show_bug.cgi?id=7636
As mentioned, this version is not to be tested. I have released newer versions with a bugzilla page for the bug tracking. Hence Ive voted down so this can be demoted so I can promote the newer version.
About the battery now showing full, thats not the problem of the app, refer to the bug 7636 for details.
https://bugs.maemo.org/show_bug.cgi?id=7636
thanks, I will post a version soon with the polling disabled when screen is locked.
Bugzilla page is used for all versions, so you need to get it only once.
sorry I seem to be lost now. Should I open a bugzilla page ? I went to http://wiki.maemo.org/Bugs:Adding_Extra_products and this talks about products in extras and not extras-testing.
what happens when I change the software the version changes, I open another bugzilla page ? what happens to votes if it was already there( in this maybe not ) but general question still ?
@Mustali
Quote:
Lack of bug reporting database http://bugs.maemo.org/ is the preferred option. Otherwise it needs to be identified in the http://maemo.org/packages/ page.
Developers: filling the XSBC-Bugtracker field in your packages address this problem. Check this wiki page to get your bugtracker at bugs.maemo.org. You can also use a external bugtracker or a e-mail address for small projects (wallpapers,..).
In the future the autobuilder will check for the existence of a bugtracker field.
End of quote
Bugtracker link is not required in package data. Bugtracker must exist and it can be indicated otherwise too. Using XSBC-Bugtracker link is not always good idea because it's too hard to change it (requires new version of a package). http://maemo.org/downloads bug link can be changed manually when it's not included in package. http://maemo.org/downloads is the only place where the link actually matters.
@rama Constant polling is no go for widgets. Using dbus callbacks doesn't require polling.
libhildondesktop provides a way to see if widget is visible http://maemo.org/api_refs/5.0/5.0-final/libhildondesktop/HDHomePluginItem.html#HDHomePluginItem--is-on-current-desktop but I don't know if it's possible to use it from Qt.
Thanks for creating this app!
Mikko, *) yes , please accept my request to report bugs here, that was what I thought when i promoted to testing. I did visit the bugzilla page but noticed I could open a bugzilla report only for apps that are in extras , or maybe I didnt look properly. *) I did think of turning off polling for the widget when the screen is off using the MCE DBUS, but I decided against it for 3 reasons. %) the user interval is configurable so its really not polling all the time. hal-device command is what it uses so its pretty low on cpu. %) even if i start listening to the mce dbus for screen lock its going to be polling all the time to see if the screen is unlocked/locked again, this is battery consumption too. %) i dont think there is any place ATM which can prove hal-device commmand is more power hungry than listening/delistening to dbus at a predefined interval of time.
Mustali, Keeping my previous post in mind about QT desktop widgets I liked the idea of a banner , I will add it.
Finally, i think its being very harsh to give a -1 for the reason state above. Its hard as it is to get software through to extras, many threads discussed it even issues like votes dont transfer to next version if its a minor change, like the banner for example. Im not going to rant about this more, but its for a thought :), and dont get me wrong I do care for testing the s/w so we have quality stuff in , but hey lets be a little lenient too in the way we go about it, all of us including you maybe dont have this as a paid job, so I suggest we give downers only for real issues other issues like the one above please resolve using a mail by having a follow up flag giving some time to developer.
Apologies if Im talking nonsense.
Lack of bugtracker link isn't a blocker but lack of bug reporting place is. But you can say bugs are reported here, problem solved.
Is this widget constantly polling or does it stop polling when the widget is not visible?
there is still no known ways to make a QT application a widget. As far as I know this is still an open issue, only gtk widgets, which compiled as a library, or python widgets can be made available this way. So nothing I can do about that at the moment. It functions as a widget nevertheless. Let me know if you have an example of a QT desktop widdgt that can be added using widget selection menu.
About the other points, I will look into it certainly.
thanks for the feedback again :)
This is a widget, it should not appear in the menu, but in the widget selection menu.
App name is qt subapplication, it should be changed.
Package needs a bugtracker.
The info given by douple tapping could be confusing for the end user, maybe they should be given in a different way.
Comments:
You must be logged in to make comments.