> Concerning the actual implementation: currently I use a very basic approach by
> simply polling TrackNavigator::queue() from within a QueueEngine and
> subscribing to the QueueEngine from a QueueManager context applet. To be able
> to access the queue from within the QueueEngine I had to AMAROK_EXPORT the
> class TrackNavigator, but probably it would be better to create an observer
> pattern like a separate TrackQueue-class and a TrackQueueObserver. What do you
> think about this approach?

Why not emit a signal when the queue is modified, and connect that
signal to a slot in your manager?

Casey
_______________________________________________
Amarok-devel mailing list
Amarok-devel@kde.org
https://mail.kde.org/mailman/listinfo/amarok-devel