Wednesday, October 19, 2011
gPodder 2.20 for Maemo 4 and Maemo 5, 2.950.14 for Harmattan
For all N950/N9 users: The Harmattan build of the gPodder QML UI is available for free in Ovi Store. The version available in Ovi Store is a development snapshot of the "tres" branch, where we will have an official release soon. I'm using it on a daily basis, and it's very stable and usable - new features will be added as we go along, so check out the new gPodder! You can grab the source code from the harmattan branch in our Git repository.
Wednesday, May 4, 2011
gPodder 2.15 available; QML UI plans and Diablo support
Because I've been asked about the QML UI several times now: It's still not day-to-day usable, and missing some features. It's also only included in the "tres" branch, and won't be included in the 2.x release series. Judging from the current performance of QML UIs on Maemo 5, I also think that the Hildon-based Gtk+ UI might be better suited for Maemo 5, especially since it has been polished for the last 1.5 years - that's why the current Maemo 5 UI will most likely still be the default, even when gPodder 3 comes out (with the QML UI as an option).
Support for Diablo will be dropped in "tres", but as there haven't been any new features for Diablo in the last several months, that's not really a problem (bug fixes will still be made to the 2.x branch of gPodder, even after "tres" is released - you just have to report them).
That said, the QML UI will be available (and the default) for environments like the MeeGo N900 DE and probably any other MeeGo UIs (tablet, handset, etc..) in the future, and it will come with some exciting new features and a streamlined user interface.
Monday, April 11, 2011
gPodder 2.14 and Panucci 0.99.1 in Extras-Testing
gPodder 2.14 is a bugfix release in the 2.x release series. It includes fixes for YouTube downloads (this fixes the HTTP 400 errors some users were reporting) and adds per-podcast "Keep episodes" settings (to avoid accidental removal of episodes that you want to archive/keep). This release also includes some fixes for feeds that don't include a valid guid element in their entries. Please test and vote for gPodder 2.14-1 in Extras-Testing.
Panucci 0.99.1 is the second experimental release of xerxes2's development branch of Panucci. As announced on t.m.o, this release includes persistence of settings between invocations and a Qt GUI that can be activated by running Panucci with the --qt command-line switch. Thanks to xerxes2 and Helmuth for collaborating on the improvements made to Panucci recently. Please test and vote for Panucci 0.99.1 in Extras-Testing.
Saturday, January 22, 2011
Ovi Store Requirements vs. Extras Testing QA
If you want to publish your applications on Ovi Store for Maemo 5, you have to fulfill certain criteria for the package to be accepted. The technical ones are listed in the document Maemo™ 5 Applications: Ovi Store Entry Requirements. Here are some problematic entries that were not clear to me in the beginning (coming from Extras QA and a Debian-based background):
- The file must be named myapplication_1_0_1.deb (for an application that is called "myapplication"). Interesting factoid: The version number must include three digits (one can interpret that as "no less and no more"). That's different from the Debian standard naming of myapplication_X_armel.deb (where "X" can be any format version number, and "armel" specifies the target architecture). So if you have packaged your application, make sure to rename the file after upload.
- The relation of the file size of /opt compared to the files in /usr must be greater than 1:80. Here's an example from That Rabbit Game: /usr contains two files: The icon (7kB) and the .desktop file (128b) and /opt contains one file: The binary (658kB). However, the difference between these two is not a factor of over 80 when compared with "du -sh" (depending on the filesystem settings).
With that said the structure of the testing criteria in that document is very clear and (apart from some problems with the detailed specs), everything is understandable, well thought-out and can be tested by following the instructions in the document. Some of these could be use to "formalize" the Extras-Testing QA checklist here on Maemo.org or at least provide an easy-to-follow guide for carrying out the basic tests.