Re: RFC: GSound, a GObject library for playing system sounds
- From: Emmanuele Bassi <ebassi gmail com>
- To: Tristan Brindle <tcbrindle gmail com>
- Cc: Desktop Development List <desktop-devel-list gnome org>
- Subject: Re: RFC: GSound, a GObject library for playing system sounds
- Date: Fri, 14 Nov 2014 12:17:37 +0000
hi;
On 14 November 2014 09:47, Tristan Brindle <tcbrindle gmail com> wrote:
A little while ago I wrote a small library called GSound (remarkably, a name which doesn’t seem to have
been used before, at least on my Fedora installation). It wraps the libcanberra API and “GObject-ifies” it
so it can be properly used in introspected languages. I’ve recently dug it back up and dusted it off ready
for public release. The code is available at
https://github.com/tcbrindle/gsound
and the generated documentation can be found at
https://tcbrindle.github.io/gsound-docs
(libcanberra itself isn’t introspectable, which I believe has caused problems for various projects in the
past, and is the reason GSound exists.)
sounds great!
I also have a couple of quick questions:
* What is the status of the libcanberra GTK module? I’ve held off wrapping any of the canberra-gtk stuff as
I seem to recall that it was being dropped, but perhaps that has changed?
I was talking to Matthias Clasen about this on the #gtk+ IRC channel
not so long ago; I'd be happy if the libcanberra-gtk module was
actually subsumed into GTK+ proper, and we just added a direct
(optional) dependency on libcanberra. it would simplify the build, the
dependency list, and the QA process of the library.
* Is there a procedure for submitting libraries for inclusion into the Gnome project proper? I’d be very
keen on GSound becoming an “official” part of the platform if people find it useful, and I’m happy to
follow the Gnome release cycles and so forth, but as an “outsider” (currently) I’m not sure what I’d need
to do for that to happen.
there is no real procedure: if applications in the jhbuild moduleset
start depending on GSound, and you commit to maintaining the library
in a way that is compatible with the GNOME release schedule, then
that's all that you need to do. :-)
if you want to use the GNOME infrastructure to host your code, track
bugs and enhancements, and open a mailing list, you can start the
process to get an account:
https://wiki.gnome.org/action/show/AccountsTeam/NewAccounts
ciao,
Emmanuele.
--
http://www.bassi.io
[ ] ebassi [ gmail com]
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]