Full time on Amarok

[Nikolaj Hald Nielsen]

> Regarding the PUD, I think we all liked the concept but the
> implementation, in the three or so ways it was attempted, was
> troublesome.  However, with the little I actually know about Plasma
> (i.e. I don't really know how easy it is, or not, to code nice graphic-y
> things with it), I'm guessing that the best way to do this -- if we have
> it at all -- would be to implement it as a Plasma applet that is
> automatically moved to the foreground (or other objects are
> minimized/iconized and then restored after).  So the applet could always
> be running, and simply move it to the front when necessary.

I am going to get very familliar with plasma doing some of the stuff I
had planned for the services, so I might give a plasma drop target a
shot sometime.

> By the way...although it will be nice to have an Amarok release for when
> KDE releases, Amarok 2.0 might want to take a cue from KDE 4.0: a
> technology release, with the polish -- and the users, and the push for
> users -- coming with 4.1.  From the little I know being on the release
> party planning team, I have the feeling that 4.0 won't be hyped to users
> or even distributions as something people should switch to -- that
> target is 4.1, when things are more stable, more mature, etc.  4.0 will
> simply let KDE showcase the technologies they've developed as they mature.
>
> Not that I don't want 2.0 to have users, but I think it'll be in pretty
> much the same boat as KDE...huge overhaul, not necessarily too
> stable/tested, etc.  So perhaps we're better releasing 2.0 on similar
> terms, then trying to mature and polish and extend functionality and
> features for a 2.1 release to coincide with the KDE 4.1 release.

I would tend to agree. But lets see how thing pan out over the next
month or so before making any final desicions

> --Jeff
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>