[gst-devel] What I want out of a "Status Table"
Jeffrey C. Ollie
jeff at ollie.clive.ia.us
Fri Feb 11 12:43:30 CET 2005
What kinds of information to gather:
1) Element/plug-in name.
2) Short, one-line description.
3) Longer, more meaningful description.
a) Listing of all pads.
5) External library dependencies:
a) Name of library.
b) Link to "home page", not just where the source tarball can
c) Version numbers that are compatible (where known).
c) Read/write or read only?
d) Type (float, integer, string, etc.)
e) Valid values.
7) Platform availability (all platforms, Mac OS X only, anything but
8) CVS module/branch/revision number (or whatever) that indicates the
version of the plug-in that is being referred to.
What this information would be used for:
1) Learning about the plug-ins that are available so that gstreamer apps
can be developed.
2) Learning about plug-ins that are not available on the current system
so that appropriate dependencies can be installed and plug-in can be
Ideally, this information would be available both to gstreamer-based
apps (gst-inspect, totem, etc.) and on a web page. Also, the
information should _not_ be limited to the plug-ins that have been
compiled on (or installed on) a particular system because part of the
point (and where the current gst-inspect fails) is learning about plug-
ins that are available in the gstreamer source but have not been
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
More information about the gstreamer-devel