[Gstreamer-bugs] [Bug 125890] Changed - Plugin Writers Guide needs rewrite

[bugzilla-daemon at widget.gnome.org]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=125890

Changed by mnews2 at wp.pl.

--- shadow/125890	Thu Jan 29 14:31:12 2004
+++ shadow/125890.tmp.25586	Thu Jan 29 16:16:45 2004
@@ -54,6 +54,27 @@
 description.  I prefer to use the term 'converters' for
 format-changing elements (like colorspace, audioscale, videoscale, or
 audioconvert).
 
 Erik used to use the term 'filter' for everything that wasn't a source
 or a sink, which I think is incorrect.
+
+------- Additional Comments From mnews2 at wp.pl  2004-01-29 16:16 -------
+Elements can be divided into several categories by their function and
+by how they work:
+- Filters are the elements that do most of the work one would consider
+"processing media". They take some input data (by so called _sink
+pads_, described in next chapter), manipulate it in some way, and
+produce some output, pushing it through _source pads_. Filter elements
+are for example codecs, visualisation elements, or sample rate converters.
+- Source and sink elements are producers and consumers of data,
+respectively. Example of source may be filesrc element that allows to
+read data from file on disk.
+- Another type of elements are _managing elements_, such as bins,
+threads and pipelines themselves that can contain other elements.
+Although it may not seem obvious, they are also subclassed from
+GstElement and as such are first class elements.
+- Special, and very useful type of bin is _autoplugger_, ie. bin that
+can perform arbitrary manipulation on data types, by managing its
+child elements accordingly. This way you can request specific
+*transformation* instead of linking specific elements, and thus avoid
+having to hardcode some required elements in your application.