kdemm backends & Helix

[Kevin Krammer]

On Wednesday 15 September 2004 04:14, Ryan Gammon wrote:

> For kdemm, one idea would be to use QCOM
> (http://doc.trolltech.com/3.0/component.html). I'm not sure how much
> QCOM is actually used in kde, if at all, but if it's viable, one could:
> - add a getUnknown() method to KDE::Multimedia::Player that returns a
> QUnknownInterface
> - most apps use the basic KDE::Multimedia::Player api
> - apps that want/need advanced engine functionality can QueryInterface
> for back-end specific extensions
> - apps need header files for the interface definitions for those
> extensions, but don't actually have to link directly to the back-end.

Unfortunately QCOM is not part of the public API of Qt.
The article you referenced is from the Qt3 pre-release era, maybe it will be 
realized with Qt4

Cheers,
Kevin

-- 
Kevin Krammer <kevin.krammer at gmx.at>
Qt/KDE Developer, Debian User
www.mrunix.de - Unix/Linux programming forum
www.qtforum.org - Qt programming forum