On Mon, 25.08.08 11:36, Brian Cameron ([EMAIL PROTECTED]) wrote: Heya!
> First, I should say that I really appreciate your comments, and helping > me to understand a whole range of issues, that go far beyond just > libcanberra. You're welcome! >> Is it so difficult to understand that I consider having c-g-p >> in $PATH to be somewhat part of libcanberra's API? You are welcome to >> deviate from that, it's Free Software after all, but please, don't ask >> me to do this for you upstream. > > On the libcanberra sixfold-announcement web page there is a link to the > "complete!" documentation, but there doesn't seem to be any docs > regarding the fact that c-g-p is considered a part of the API. Also, I > couldn't find any docs about the API for writing a backend plugin, which > made it a little hard for me to figure out how to write one, and might > explain why my GStreamer plugin was a bit hacked. > > http://0pointer.de/public/libcanberra-html/libcanberra-canberra.html > > Are the docs for writing a backend plugin API somewhere else? Or do > you just have to figure it out from the existing plugin code? The backend "API" is considered internal -- not public; it might be changed at any time. If you write a backend make sure to submit it upstream so it is easy to keep up to date if the backend API changes. I don't see any changes coming, but I want the freedom that I can change it. Please note that we don't install any header files related to the backend API for precisely this reason. Backends should be developed in-tree. OTOH the official API for applications is considered stable. After all it's an "Application Programmers Interface", not a "Backend Programmers Interface". ;-) The gtk-docs API only includes documentation for the C API. We probably should add a man page for c-g-p though. >>>> Somehow I managed to ignore that second iteration of the patches and >>>> didn't review them when Marc-Andre posted them. However, a few minutes >>>> ago I finally reviewed them with Marc-Andre on IRC. He plans to rebase >>>> them on current libcanberra. >>> Great, does this mean that GStreamer will just be supported >>> out-of-the-box with the next libcanberra release? That's great. Or >>> do you need further help to make the code ready? >> Note sure about the *next* libcanberra release. That depends entirely >> on whether I get a good, mergable patch by then. Consider working with >> Marc-Andre to get it ready quickly. > > Okay. That sounds reasonable. I do not remember you sharing > Marc-Andre's contact information. If you could share that with me, > I will get in touch with him. The patch I linked contains Marc-Andre's address, AFAIR. marcandre dot lureau at gmail dot com, elmarco on IRC. He's a Nokia employee. He's also the gnome-multimedia maintainer if I am correctly informed. i.e. someone to know for people interested in audio on free desktops. ;-) And he is also on this ML. So you might as well keep discussions about the gst patch on-list. Marc-Andre, say something! Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4 _______________________________________________ libcanberra-discuss mailing list [email protected] https://tango.0pointer.de/mailman/listinfo/libcanberra-discuss
