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

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=396779

  GStreamer | gst-plugins-base | Ver: HEAD CVS





------- Comment #10 from Brendan Howell  2007-01-29 17:03 UTC -------
Your example looks great now.  What about keeping track of the plugin/element
version?  Updates of plugins can change the properties or enums, right?  If we
have a version in there, you can avoid any nasty errors trying to load an
incompatible preset.

The only other thing I might add would be some kind of meta tags so that an
application could optionally implement things like groups or keyword tagging.  

As far as format, I guess I can understand if XML is too much overhead.  Can we
do something in YAML, JSON or Sexp that would be up to the application to
parse?  That way, an embedded app could have a custom parser and a bigger
system could use a library method.  I hate using ugly binary or unreadable text
formats if I can avoid it.

I also have a question about managing presets.  How should package maintainers
handle merging presets?  They might need some kind of merge utility, unless the
GStreamer devs want to manage some sort of preset repository.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email