I've been thinking about it a bit more, and I had the following idea:
While it's all nice and dandy to restrict the scope of your app to an mplayer front-end, it's kinda counter-productive to market it as a general media player, isn't it?
Basically the problem is that mplayer is really designed to be a video player, not a music one. They hacked ID3v1 tag support already, but it shouldn't even be in there. Ideally you'd use a different lib to read those, but that's both out of your focus, and too time-consuming, apparently. Any ideas? I'm all out
This is interesting idea . I will see if Qtopia label widget can display a picture along with text. If it does, that can be implemented relatively easily...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=67852\"][{POST_SNAPBACK}][/a][/div]
That's brilliant. Please do not make it filename dependent (just display whatever pic is in the directory). Another nice thing about APE and ID3v2 tags is that they can be extended to include picture information (although I hate people who embed tags in them directly. Hate hate hate). I'll shut up about tags now, I promise
It might also be a good idea to have ready-to-use packages for all the supported architectures, so people don't get confused.
How is the situation when installing on top of cacko, which already has kino and mplayer, but not listed as packages. Can you just dump the new version on top?
I agree - displaying album covers is a proper enhancement for a mp3 player, playing slideshows is a job for image viewers.
Millions of iPod photos weep in despair.
