Summary: | podcast: add opml export | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | andreaswuest |
Component: | Podcast | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | wishlist | CC: | bart.cerneels |
Priority: | NOR | ||
Version: | 2.3.0 | ||
Target Milestone: | 2.3.2 | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
andreaswuest
2010-03-21 11:06:50 UTC
amarok version is 2.3.0 There is only an OPML import option, and I don't think anyone is working on export right now. I'd say native support for this would be very welcome. So if you want to give it a try just go ahead and do so! :) A native export is on my todo list. Pretty far down though. It's something I could implement during the week on my daily 2 x 20 minutes train trip, so I imagine it might be a good junior job for a Qt programmer with a year or so experience. Basically OpmlParser needs to be expanded to be able to create on OPML document instead of only parsing them. OpmlOutline already has the necessary setters. Talk to me (stecchino) on IRC for help. i planned the export as a script. however you seem to plan to add it as cpp code. at the moment i just cannot decide if it is worth spending the time on the javascript export if there will be a native export, which makes my script obsolete :-( The way I see it OPML export in C++ will be superior because it will integrate well and be usable in other components as well. How about you try to implement it in native code? I quickly looked at it and feel it's not to much and nicely contained as well. And you can always ask my advice by mail or irc (Stecchino). 2.3.1 is in feature freeze -> 2.3.2 *** This bug has been marked as a duplicate of bug 126120 *** |