[gstreamer-bugs] [Bug 396779] Preset interface for elements

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=396779

  GStreamer | gstreamer (core) | Ver: HEAD CVS

Wim Taymans changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #100165|none                        |needs-work
               Flag|                            |




------- Comment #44 from Wim Taymans  2007-12-04 11:26 UTC -------
Quick braindump. I see 3 components:

 (1) A global repository mapping 
     Element name -> multiple preset names -> multiple key/value pairs
     This object should allow for query and modification of the presets.

 (2) A component to use the repository and apply a setting by changing object
     properties. This will usually be done from the application but could 
     also be performed right after loading an element to restore its default
     settings. This could be merged into (1), depending on complexity.

 (3) A system to feed the repository
     From stored core files (in one or more formats)
     From stored user files
     From elements (based on element specific info like RDF, ...)
     From application code.

We definitely want to decouple (1) and (3) similar to the registry so that we
can
use alternative file formats or sources for the presets. 

I don't see an immediate need to make elements implement an interface. I see
this
as a way to configure GObject properties, which is independant of the GObject
in
question. For feeding the presets (3) into the repository (1) you could just as
well push/merge it into the repo when the plugin loads (or ultimately an
interface to pull them).

(1) and (2) seem to be below GStreamer, it could operate solely on GObjects.
(3) could be part of core or needs at least more interaction with it (paths
maybe).


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=396779.