notes on documenting elements and plugins

Original commit message from CVS:
notes on documenting elements and plugins
This commit is contained in:
Thomas Vander Stichele 2005-09-14 22:01:45 +00:00
parent 93ca1da67c
commit 58a4a1a7bf
18 changed files with 52 additions and 49 deletions

2
common

@ -1 +1 @@
Subproject commit 112f70ef5172090966f53934a471eb2e54c2d667 Subproject commit 9563779845a70c73dd9bc9ff6750b155e2b4cba2

View file

@ -195,6 +195,47 @@ d) have verified your changes build documentation locally.
Then, after updating any of the docs, run "make upload" from that directory. Then, after updating any of the docs, run "make upload" from that directory.
Or, run "make upload" from this (docs) directory. Or, run "make upload" from this (docs) directory.
DOCUMENTING ELEMENTS
====================
As of september 2005 we have some system to document plugins and elements
in the various plugin packages.
- in a submodule, docs go in docs/plugins
- template can be copied from gst-plugins-base
- to add an element to be documented:
- add an include href in the Elements chapter for the element
- add a section for it in -sections.txt with
<FILE>element-(element)</FILE>
<TITLE>(element)</TITLE>
- add a gtk-doc section to the source code like:
/**
* SECTION:element-multifdsink
and fill it with documentation about the element, preferably inside
a <refsect2> docbook container.
- add an example:
- either a few pipelines, inside <programlisting>
- or a piece of code:
- create an example program (element)-example.c in the plugin dir
- add the full path (starting with $(top_srcdir)) for this example
to the EXAMPLE_CFILES variable in Makefile.am
- add an xinclude of a file named "element-(element)-example.xml"
to the docbook documentation piece in the element source code
- add the header to EXTRA_HFILES in Makefile.am to be able to document
signals and args
(FIXME: are we sure we can both do the xinclude from the tmpl/ sgml,
as well as an override from the source itself ? maybe we should just
make sure the xinclude is in the source itself instead ?)
- to rebuild the docs, do:
make clean
make inspect-update
make
- to add a plugin to be documented:
- make sure inspect/ has generated a .xml file for it
- add it to CVS
- add an include in -docs.sgml in the Plugins list for that plugin
RANDOM THINGS I'VE LEARNED RANDOM THINGS I'VE LEARNED
========================== ==========================

View file

@ -65,9 +65,6 @@ and gst_element_set_clock(). You can wait for the clock to reach a given
<!-- basic object functions --> <!-- basic object functions -->
<!-- ##### SECTION Stability_Level ##### -->
<!-- ##### STRUCT GstElement ##### --> <!-- ##### STRUCT GstElement ##### -->
<para> <para>
@ -973,6 +970,16 @@ Sets the parent of an element.
@Returns: @Returns:
<!-- ##### FUNCTION gst_element_set_state_async ##### -->
<para>
</para>
@element:
@state:
@Returns:
<!-- ##### FUNCTION gst_element_state_get_name ##### --> <!-- ##### FUNCTION gst_element_state_get_name ##### -->
<para> <para>

View file

@ -14,6 +14,3 @@ all gstreamer core related enumerations
</para> </para>
<!-- ##### SECTION Stability_Level ##### -->

View file

@ -14,9 +14,6 @@ Core interface implemented by #GstElements that allows runtime querying of inter
</para> </para>
<!-- ##### SECTION Stability_Level ##### -->
<!-- ##### STRUCT GstImplementsInterface ##### --> <!-- ##### STRUCT GstImplementsInterface ##### -->
<para> <para>

View file

@ -15,9 +15,6 @@ in a pipeline.
#GstIndexFactory #GstIndexFactory
</para> </para>
<!-- ##### SECTION Stability_Level ##### -->
<!-- ##### STRUCT GstIndex ##### --> <!-- ##### STRUCT GstIndex ##### -->
<para> <para>

View file

@ -14,9 +14,6 @@ GstIndexFactory is used to dynamically create GstIndex implementations.
#GstIndex #GstIndex
</para> </para>
<!-- ##### SECTION Stability_Level ##### -->
<!-- ##### STRUCT GstIndexFactory ##### --> <!-- ##### STRUCT GstIndexFactory ##### -->
<para> <para>
The GstIndexFactory object The GstIndexFactory object

View file

@ -68,9 +68,6 @@ categories. These are explained at GST_DEBUG_CATEGORY_INIT().
and environment variables that affect the debugging output. and environment variables that affect the debugging output.
</para> </para>
<!-- ##### SECTION Stability_Level ##### -->
<!-- ##### ENUM GstDebugLevel ##### --> <!-- ##### ENUM GstDebugLevel ##### -->
<para> <para>
The level defines the importance of a debugging message. The more important a The level defines the importance of a debugging message. The more important a

View file

@ -67,9 +67,6 @@ object.
</para> </para>
<!-- ##### SECTION Stability_Level ##### -->
<!-- ##### STRUCT GstObject ##### --> <!-- ##### STRUCT GstObject ##### -->
<para> <para>

View file

@ -57,9 +57,6 @@ Last reviewed on December 13th, 2002 (0.5.0.1)
#GstPadTemplate, #GstElement, #GstEvent #GstPadTemplate, #GstElement, #GstEvent
</para> </para>
<!-- ##### SECTION Stability_Level ##### -->
<!-- ##### STRUCT GstPad ##### --> <!-- ##### STRUCT GstPad ##### -->
<para> <para>

View file

@ -73,9 +73,6 @@ The following example shows you how to add the padtemplate to an elementfactory:
#GstPad, #GstElementFactory #GstPad, #GstElementFactory
</para> </para>
<!-- ##### SECTION Stability_Level ##### -->
<!-- ##### STRUCT GstPadTemplate ##### --> <!-- ##### STRUCT GstPadTemplate ##### -->
<para> <para>
The padtemplate object. The padtemplate object.

View file

@ -21,9 +21,6 @@ the pipeline, use gst_object_unref() to free its resources.
#GstBin #GstBin
</para> </para>
<!-- ##### SECTION Stability_Level ##### -->
<!-- ##### STRUCT GstPipeline ##### --> <!-- ##### STRUCT GstPipeline ##### -->
<para> <para>

View file

@ -35,9 +35,6 @@ to bring the plugin into memory.
#GstPluginFeature, #GstType, #GstAutoplug, #GstElementFactory #GstPluginFeature, #GstType, #GstAutoplug, #GstElementFactory
</para> </para>
<!-- ##### SECTION Stability_Level ##### -->
<!-- ##### FUNCTION gst_plugin_error_quark ##### --> <!-- ##### FUNCTION gst_plugin_error_quark ##### -->
<para> <para>
Get the error quark Get the error quark

View file

@ -14,9 +14,6 @@ This is a base class for anything that can be added to a #GstPlugin.
#GstPlugin #GstPlugin
</para> </para>
<!-- ##### SECTION Stability_Level ##### -->
<!-- ##### STRUCT GstPluginFeature ##### --> <!-- ##### STRUCT GstPluginFeature ##### -->
<para> <para>

View file

@ -14,9 +14,6 @@ various global enums and constants
</para> </para>
<!-- ##### SECTION Stability_Level ##### -->
<!-- ##### ENUM GstState ##### --> <!-- ##### ENUM GstState ##### -->
<para> <para>

View file

@ -14,9 +14,6 @@ GValue implementations specific to GStreamer
</para> </para>
<!-- ##### SECTION Stability_Level ##### -->
<!-- ##### MACRO GST_VALUE_HOLDS_FOURCC ##### --> <!-- ##### MACRO GST_VALUE_HOLDS_FOURCC ##### -->

View file

@ -27,9 +27,6 @@ network connections also need a protocol to do this.
#GstBuffer, #GstCaps, #GstEvent #GstBuffer, #GstCaps, #GstEvent
</para> </para>
<!-- ##### SECTION Stability_Level ##### -->
<!-- ##### ENUM GstDPHeaderFlag ##### --> <!-- ##### ENUM GstDPHeaderFlag ##### -->
<para> <para>

View file

@ -14,9 +14,6 @@ accelerated routines for getting bits from a data stream.
</para> </para>
<!-- ##### SECTION Stability_Level ##### -->
<!-- ##### STRUCT gst_getbits_t ##### --> <!-- ##### STRUCT gst_getbits_t ##### -->
<para> <para>