- Device synchronization removed: We have removed the ability to sync to iPod, MTP and filesystem-based MP3 players. You can store your gPodder data on your mobile device directly for now (using
$GPODDER_HOME) or wait for someone to implement a syncing plugin.
- New on-disk structure: Instead of having "gpodder-downloads" in your home folder, and the database and settings hidden away in another folder, all gPodder data is now stored in "gPodder" in your home directory (on Linux) or in "gPodder" in you "My Documents" folder (on Windows) or on the mass storage (MyDocs partition) on the N900 and N9. The database format has also been overhauled, you can use the "gpodder-migrate2tres" script to convert your gPodder 2 data to gPodder 3. Because all data is now stored in one folder, you can now use the Desktop version of gPodder to work on e.g. the gPodder downloaded data on your mobile device by pointing the
$GPODDER_HOMEenvironment variable to the storage device.
- EQL: The so-called "Episode Query Language" allows you to write queries against your podcasts. For example, you can use "(audio and downloaded and minutes < 10)" to show all downloaded audio files that are shorter than 10 minutes to listen to. This is very powerful, and can currently be used in the episode list of the GTK UI using "search-as-you-type".
- Improvements to the GTK UI, including support for showing the duration in the episode list, and hiding of columns in the episode list.
- New QML-based touch UI: In addition to the GTK UI and the command-line interface, gPodder 3 contains a QML UI for use with PySide. This UI can be used on touch-enabled netbooks/laptops and on mobile devices. The QML UI is the only mobile UI supported in 3.0.0 (replacing the Hildon UI in previous releases).
- Web UI: While this is still in its early stages, there is a small Web UI included that (when complete) will make it possible to manage gPodder via a web browser (with the help of a local, embedded web server).
- Refined backend / data model: The codebase has been cleaned up and restructured, so it should be easier to maintain and add to in the future.
- Support for Woodchuck: Neal Walfield has contributed a plugin for his Woodchuck framework. With Woodchuck installed, your device can detect which podcasts you like and automatically download the right episodes.
- Better support for Windows: The Windows launcher has been refined, and Windows users can now also use the CLI in addition to the GTK GUI. The new version will also use a system-wide installation of Python 2.7 and PyGTK, and auto-download the installers for these dependencies if they are not found. This means smaller package sizes and better disk usage.
- Dropped support for Maemo 4 (N800, N810) and Maemo 5 Hildon (N900)
- Added support for Maemo 5 QML (N900) and MeeGo 1.2 Harmattan (N9)
For packages in various distributions, see the downloads page.
With the release of the "tres" branch, gPodder 2 is put into maintenance mode, with 2.20 being the latest release at the moment. Maintenance mode means for us that we will only release updates in case bugs are found and reported. We will not be adding new features, but if translators update the (now frozen) strings, we will also push out new updates every now and then. Also, we might consider merging patches against 2.x. When a new bugfix release of gPodder 2.x is made, we will still create packages for Maemo 4 and Maemo 5 users.
For Maemo 5 users wishing to upgrade to 3.0.0, we will provide packages for the new release soon - in that case, only the QML UI is supported, and users are encouraged to install the Maemo 5 Community SSU if they want to use the QML UI on their devices.
MeeGo 1.2 Harmattan packages will be provided via the Nokia Store.
This release also changes something in the Git repository: The "tres" branch gets renamed to "master" (the master branch), and the old master branch (2.x) is renamed to "two".
Also, coinciding with the release of gPodder 3, we have a new mailing list on freelists.org.
This is just the beginning, though - with gPodder 3 finally out, the flood gates are once more open for new features to land in the master branch :)
Look out for new updates for your favorite podcatcher soon. In the mean time, if you find any bugs, please report them at http://bugs.gpodder.org/. Thanks to all who have made this release possible, and who helped support the gPodder project over the last year that it took to get "tres" in shape! Enjoy gPodder 3 :)
Congratulations! Very well done! I can't wait to get to try the new version and UI on my N900! Of course I've got the community SSU.ReplyDelete
"This is just the beginning, though - with gPodder 3 finally out, the flood gates are once more open for new features to land in the master branch :)"
Awesome! I hope this means that you will have a serious look at my ideas for making gPodder more social. I truly believe this would be a huge benefit. :)
Why was device sync support removed? That seems like an oddly significant feature to take out.ReplyDelete
I also think that remove sync option is wrong.ReplyDelete
I use gPodder to download podcast always and sync when I connect my player.
About removing sync: Nobody of the developers has an iPod or MTP device (anymore), so both devices types were not really as good supported as they could have been (there are still some bugs open) due to their closed nature.ReplyDelete
The only device type where we are confident that it worked was the filesystem-based MP3 player type (e.g. USB Mass Storage Mode). However, the old implementation while working wasn't maintainable from a code perspective. With the new architecture, it should be easier to add this later on - I don't say that we won't re-add it in the future. Contributions here are gladly accepted, also brainstorming for a better, new implementation of the filesystem-based MP3 player synchronization, in case you want to make it even more awesome :) Who's up for this task?
I hope that the gpodder editor of configuration will get more options. I'm particulary concerned about download_dir option. I have a dedicated partition for my music and I don't want it in the home directory.ReplyDelete
What about creating shortcuts to the git version of gpodder just like when it was at 2.-something (updater and GUI).
Thank you for making such good and very useful application.
stachowski-mateusz: As mentioned in the README, you can use the GPODDER_HOME environment variable to tell gPodder where it should put its downloads and database. The download_dir option doesn't exist anymore for this reason - it's replaced by $GPODDER_HOME from the environment. You can even write scripts (and create icons) for gPodder in different locations if you want to. The alternative is to symlink ~/gPodder to where you want it - this clutters your $HOME, but does not need any environment variable changes.ReplyDelete
The shortcuts creation was something that I didn't think anyone still used; it's trivial to add, but you can just create a custom launcher manually with bin/gpodder in the source folder as application and data/gpodder.png as the icon. HTH :)
I have installed 3.0.0 for Win7 and I can't get it to work. Every time I click on the gpodder application it wants to install, or repair or remove python. What am I doing wrong?ReplyDelete
Thanks. I will check it out.ReplyDelete
I've somehow didn't notice that option in the README. It's still not the thing, because it creates two unnecessary folders. If I want to go to podcast directory than I have to go one folder deeper than before.ReplyDelete
I'm also wondering when this version will appear in the gPodder Ubuntu PPA.
The old version is still available so I can use the sync option?ReplyDelete
I've been using gPodder exclusively since the 2.0 days. It's the best podcasting agent available on Linux.ReplyDelete
However, with the removal of the syncing option, I'll have to find another option, or stick with 2.20 for perpetuity. I only listen to them on my mobile device.
Mark me down as one of the users who needs the "iPod" in "gPodder."
"Unknown": Stick with 2.20 for now, and upgrade to 3.x when device sync lands in the 3.x branch. It's not that we throw it out indefinitely, it's just that the old syncing code was too inflexible and not well maintained.ReplyDelete
If you want to help with getting device synchronization into 3.x faster, please get in touch - there are several areas where you can help out, whether you are a developer or not.