Showing posts with label maebar. Show all posts
Showing posts with label maebar. Show all posts

It's about time...

...displayed inside gPodder. Not only the total time of a podcast episode, but (thanks to the MAFW integration that has been added in 2.8) also the position that you stopped listening to, so you know how much time is remaining. There are several possibilities how to display the progress: A circle sector image, a "position/total" text display and a "remaining" text display. Right now, I opted for the "position/total" display (with "total" in cases where you haven't started listening to an episode). Here's how it looks in the current development version of gPodder:

If I remember correctly, the idea for this came up during the Barcelona Long Weekend and was suggested by Tuomas while we were discussing gPodder's UX. Back then gPodder did not store any kind of time-based length information in its database - only the file size in bytes, which isn't that helpful for listening purposes. But since then the work on gpodder.net and the desire to synchronize episode status information between different devices has put everything in place that's needed to detect the duration of episodes (it's even provided as <itunes:duration> (spec) in some RSS feeds) and with the MAFW integration to detect the current playback position when playback is stopped.

If you are using gPodder 2.8 and the built-in Media Player, gPodder already collects this information, so when the next release comes out, you will immediately have some useful data there. This should also help you in deciding which episode to pick on your commute.

What do you think of this feature? Is the current representation the best one, or would something else be more useful to you?

headphoned, Metalab Talk, App Forum and gPodder updates

Due to popular demand, the Headphone Daemon is now available for Fremantle and the N900, too. A package is in Extras-Devel and should be available for QA testing in Extras-Testing soon. There is also a discussion thread on t.m.o and the packages page for QA.

In other news, I'll be giving a talk about Maemo.org and Maemo development at the Metalab Vienna on the 22nd of January. This is in preparation of the Hackathon that's happening on the weekend after the talk (a good opportunity to hack on CLI Sharing, maybe..).

In general, it seems like the N900 seems to get up to speed here in Austria now: The Nokia App Forum Alps is organizing a competition for mobile applications, so hopefully we see some new apps coming out of this. And if you happen to be around Hagenberg in early March, do join the Mobile Developers Conference.

A new gPodder version will be out "very soon now" - just one bug and one feature (my.gpodder.org API) left to do. I hope I'll be able to do it this weekend, so you can all enjoy the #maebar UI updates and new features such as Flickr support.

gPodder "after 2.1" Maemo 5 UI Changes (#maebar)

Quick note about the stable version: Thanks to the hard-working testers, gPodder 2.1 has received its necessary karma points in Extras-Testing before the quarantime time is up, so we are just waiting for some more days to pass before gPodder 2.1 will finally enter the Extras repository.

In the mean time, there have been some important developments in the Git repository, mostly based on ideas from the Barcelona Long Weekend - thanks to all the people who provided valuable input, especially Tuomas (tigert) for all the hard work. I have created a new set on Flickr with some screenshots of the current development version:

The new UI is not set in stone, and still has some rough edges, so I'd like to receive some feedback on what can be improved.

If you want to test the development version interactively, use Git to checkout git://repo.or.cz/gpodder.git on your device, and then run bin/gpodder --fremantle --verbose inside the checkout to start the development version in debugging mode. Make sure to have the current version of gPodder installed to drag in the required dependencies (alternatively, install the dependencies by hand). As with all development versions, if it breaks (or messes with your downloads/subscriptions), you got to keep the pieces.

Thanks in advance for the feedback :)