1337-x369513929661000482
x369513929661000482
Source (link to git-repo or to original if based on someone elses unmodified work):
amarokky (0.1beta3) unstable; urgency=low
* Better label handling to avoid flicker
* Added smooth scrolling options
* Improved display code
* Small code fixes
Ratings & Comments
9 Comments
Ark says "An error occurred while trying to open the archive". What could the problem be?
Did you check out mediacontrol applet already? It supports amaroK amongst other things, and also supports seeking, current track display and navigation controls. Probably it would be better to spend effort in that direction, instead of making OneMoreApp.
Short answer: No :) .. i have fun writing this, so i will continue :)
i like it. berkus: well this way, there wouldn't be any amaroK now, and we would have become noatun devs ;-) ...muesli
that's the way life goes :)
would have actually made more sense too but given the miriads of irc-clients I don't think that stops anybody from doing the same mistake over and over again.
I agree, mETz, Noatun was a weird reinvention of the wheel..
What you're trying to do sounds like a nice plan. We could really use a good kicker applet specifically written for amaroK, so that it fits perfectly to our features. If you have any questions or want to talk with us about development, come visit us sometime on irc.freenode.net, #amarok. Also you could subscribe to our mailing list, which is here: http://lists.sourceforge.net/lists/listinfo/amarok-devel Regarding the dcop issue with beta3: We just got a aware of the problem and are currently looking into it. Apparently you must append amaroK's PID to the call, for some reason.
Not KUniqueApplication anymore?