[Portland] DAPI Sound for Portland? and general comments

[Mikael Hallendal]

12 jan 2007 kl. 00.24 skrev Marc-André Lureau:

Hi,

>> Under the dapi.sound interface, there is a simple Play method.
>>
>> Such methd, I would say, should not be limited to take only a  
>> filename. A URI at least  would be much nicer. Another thing that  
>> comes to my mind, is that PlaySoundFile under dapi has only a  
>> limited chance to succeed on a cross-desktop project: if you need  
>> such function, then you probably need to do more advanced things,  
>> like getting metadata (even if there is other way for files, but  
>> lets talk about URI instead). Why? Because, if you refer to a  
>> soundfile, that means you are probably not willing to play a sound  
>> event. Right now, I only see a file manager for this "file" need  
>> (see Nautilus sound, for example). But a file manager need more  
>> things, like changing the playing state, seeking (and it would be  
>> nice, of course to set fadein/out!). Basically, you need some  
>> control. So you need to define an object that implement a  
>> sound.playback interface.
>>


Just to clearify, I'm only talking about what I think fits in DAPI.  
Not that the features you describe wouldn't be useful in a multi- 
platform library/daemon.

I think they fit in their own component as I said in my last email.  
DAPI can't be a full Sound-abstraction layer, that's not what it  
does. It's a layer to abstract common and simple operations that are  
used by a wide range of applications.

Cheers,
   Mikael Hallendal

--
Imendio AB, http://www.imendio.com