On Mon, 13.12.10 10:55, Colin Guthrie ([email protected]) wrote: > Hi, > > In GTK, the current sound theme name is stored AFAICT in gconf. This in > itself makes sense I guess, in that context.
Well, ultimately it is indeed stored in gconf/dconf. However, clients do not read it from there. That instead works via XSETTINGS (much like the icon theme), and to my knowledge KDE supports XSETTINGS as well. > However, if I ever implement libcanberra support (or any alternative > Sound Theme implementation (which is very much NOT my intention, but > just making a point)) in KDE, then the logical step would be to store > the sound theme in some kconfig file. That should be a simple matter of adding a single XSETTINGS to kconfig mapping to KDE's settings daemon somewhere. > But therein lies the problem. If KDE and GTK sound theme preferences are > separate, then running GTK apps under KDE or KDE/Qt apps under GNOME > would result in potentially different sound themes which is not ideal. > > Would there be some scope to instead store the current sound theme in > the .config tree? Perhaps expose an API in libcarberra itself which > allows the current theme to be set? It could internally use this config > as a fallback if the client does not set the theme in the context or > play proplists. Hmpf, we want to follow the machisms of the icon theme as closely as possible here. I do bot want to introduce an independent meachnism for this. In particular because XSETTINGS actually supports chnage notification, which isn't fun with plain config files. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ libcanberra-discuss mailing list [email protected] https://tango.0pointer.de/mailman/listinfo/libcanberra-discuss
