<br><div><span class="gmail_quote">On 1/9/07, <b class="gmail_sendername">Thiago Macieira</b> <<a href="mailto:thiago@kde.org">thiago@kde.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Are you proposing an in-process or an out-of-process playback of the sound<br>file?</blockquote><div><br>I don't care :) Seriously, this should be an implementation detail and not a C API problem.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> If it's in-process, I think you're going to find it very hard to adapt to<br>backends in use and to find themed files. At least, if you plan on<br>keeping this library lightweight.</blockquote><div><br>Hmm, I don't know. If I have to write an out-of-process, I will have the same problem isn't it? This should be implemented somehow, someone as to do it. Furthermore, once you have implemented it, it seems quite easy to add transparent out-of-process for the very same API. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">If you're going for out-of-process, I suggest you simply define a D-Bus<br> interface class, service name as well as the documentation for it. This<br>should be enough. Your library would simply wrap those D-Bus calls and<br>signals for applications not using a high-level D-Bus binding.</blockquote> <div><br>I should definetly provide a DBus API that can complement with API. But I was more interested by an in-process implementation first.<br><br></div>Thanks for your comments,<br><br><span class="gmail_quote">I know it's a tough issue and that kde guys have probably other better plan than those very limited for libgnome-sound... But any comment is very pleased, <br><br>Best regards,<br><br></span></div>-- <br>Marc-André Lureau, GSmartMix