After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 700909 - GStreamer Documentation for GNOME Desktop says applications should be developed using gconfelements plugin but the plugin is depreciated
GStreamer Documentation for GNOME Desktop says applications should be develop...
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: documentation
1.0.7
Other Linux
: Normal normal
: 1.1.1
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-05-23 17:59 UTC by Meg Ford
Modified: 2013-05-24 07:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Meg Ford 2013-05-23 17:59:39 UTC
GStreamer Documentation for GNOME Desktop says applications should be developed using gconfelements plugin ( http://gstreamer.freedesktop.org/data/doc/gstreamer/head/manual/html/section-integration-gnome.html ) but the plugin is depreciated/removed in GStreamer 1.0. The documentation should be corrected with a new recommendation to replace gconfelements plugin.
Comment 1 Tim-Philipp Müller 2013-05-23 22:57:10 UTC
Quite right, thanks for the bug report.
Comment 2 Tim-Philipp Müller 2013-05-23 22:58:41 UTC
I guess technically the (not-yet-ported) gsettings* elements would replace those. But so far no one has complained yet that they haven't been ported yet, which makes me think no one uses them, so maybe it's time to let go of both without a GNOME-specific replacement.
Comment 3 Meg Ford 2013-05-24 02:39:14 UTC
I've only been using GStreamer for a month or so, so I'm not really qualified to comment. However, I'm writing a new sound recorder for GNOME and using GStreamer as the backend, so I can say a few things: from what I've seen while reading other GStreamer-based code in GNOME, a lot of apps are still using 0.10x. One of the reasons I'm writing an updated version of the sound recorder is because it relies on gconf. Afaik I should be fine using autoaudioscr. Seif Lofty and his team are working on Music right now, as well, but I think they are relying on Playbin.

So if I were to say anything here, it would be that it doesn't seem that the newer apps will rely on it; but perhaps it would be good to keep the possibility open for now in case there are issues that come up in the near future that could be solved by relying on it?

But in terms of the documentation, yeah, it might make sense to just remove it unless someone knows of a good reason why we need to recommend gsettings* elements. Unfortunately, the person who might know that reason isn't me.
Comment 4 Olivier Crête 2013-05-24 03:02:49 UTC
@Meg: For something like gnome-sound-recorder, it may make sense to hardcode "pulsesrc" instead of using the portable autoaudiosrc, so you can control the input source (you can steal/borrow useful code from Empathy to list existing input sources/microphones).
Comment 5 Meg Ford 2013-05-24 03:27:24 UTC
@Oliver, thanks very much! I will read that code tomorrow :)
Comment 6 Sebastian Dröge (slomo) 2013-05-24 06:44:47 UTC
I think the gsettings elements can go away, yes. gnome seems to only care about pulseaudio nowadays and without it some functionality is gone.
Comment 7 Olivier Crête 2013-05-24 07:27:17 UTC
commit bd5708a0cd1d866995922b8beac2563a2be6b8a4
Author: Olivier Crête <olivier.crete@collabora.com>
Date:   Fri May 24 16:24:10 2013 +0900

    docs: Remove mention of gconf* elements
    
    Instead recommend pulsesrc/sink for audio, there is nothing GNOME
    specific for video.