Request for moving kdelibs/arts/knotify outside the arts directory
kretz at kde.org
Tue May 31 23:30:10 BST 2005
I guess you are talking about KDE4 and not KDE 3.5?
Anyway, the plan (my plan - and what we discussed on aKademy 04) is to have a
new Multimedia API for KDE4. So, yes, knotify will need to be moved out of
the arts dir and all the remaining aRts code can be removed. All multimedia
(audio/video) API should go into the new kdemm libs. If you are interested in
helping let me know and we can coordinate our efforts.
Would you be interested in implementing the multimedia API with native Windows
code (I guess you'd be using DirectX)?
On Wednesday 01 June 2005 00:02, Ralf Habacker wrote:
> Because this relates also with the KDE 4 plan to use KAudioplayer with
> akode http://edu.kde.org/development/port2kde4.php, for my opinion is would
> be nice to have knotify outside from the arts dir directly into kdelibs.
I've never heard of this plan before...
> Beside the basic movement of knotify, an additional topic is where to put
> the native sound support.
Into the backend implementation for kdemm.
> Currently there are two different implementation, one in knotify using the
> arts api and one in KAudioplayer using the dcop/mcop bridge.
The dcop/mcop bridge was never used AFAIK. KAudioPlayer uses knotify.
Matthias Kretz (Germany) <><
MatthiasKretz at gmx.net, kretz at kde.org,
Matthias.Kretz at urz.uni-heidelberg.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the kde-core-devel