mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2025-01-31 11:32:38 +00:00
app-dev: rename building/ -> basics/
https://bugzilla.gnome.org/show_bug.cgi?id=773976
This commit is contained in:
Tim-Philipp Müller
parent
f1c93b5f66
commit
be894db215
15 changed files with 25 additions and 25 deletions
|
|
@ -29,7 +29,7 @@ Lastly, we will explain how autoplugging and the GStreamer registry can
|
|||
be used to setup a pipeline that will convert media from one mediatype
|
||||
to another, for example for media decoding.
|
||||
|
||||
[helloworld]: application-development/building/helloworld.md
|
||||
[helloworld]: application-development/basics/helloworld.md
|
||||
[playback-components]: application-development/highlevel/playback-components.md
|
||||
|
||||
## Media types as a way to identify streams
|
||||
|
|
@ -62,7 +62,7 @@ Now that we have an idea how GStreamer identifies known media streams,
|
|||
we can look at methods GStreamer uses to setup pipelines for media
|
||||
handling and for media type detection.
|
||||
|
||||
[pad-caps]: application-development/building/pads.md#capabilities-of-a-pad
|
||||
[pad-caps]: application-development/basics/pads.md#capabilities-of-a-pad
|
||||
[pwg-type-defs]: pwg/advanced/building-types.md
|
||||
|
||||
## Media stream type detection
|
||||
|
|
|
|||
|
|
@ -924,7 +924,7 @@ the “capsfilter” element in between the two elements, and specifying a
|
|||
types matching that specified capability set for negotiation. See also
|
||||
[Creating capabilities for filtering][filter-caps].
|
||||
|
||||
[filter-caps]: application-development/building/pads.md#creating-capabilities-for-filtering
|
||||
[filter-caps]: application-development/basics/pads.md#creating-capabilities-for-filtering
|
||||
|
||||
### Changing format in a PLAYING pipeline
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ Most of the interfaces handled here will not contain any example code.
|
|||
See the API references for details. Here, we will just describe the
|
||||
scope and purpose of each interface.
|
||||
|
||||
[element-object]: application-development/building/elements.md#using-an-element-as-a-gobject
|
||||
[element-object]: application-development/basics/elements.md#using-an-element-as-a-gobject
|
||||
|
||||
## The URI interface
|
||||
|
||||
|
|
|
|||
|
|
@ -18,12 +18,12 @@ using the GStreamer tagging system. Stream-info can be retrieved from a
|
|||
|
||||
Stream information can most easily be read by reading it from a
|
||||
`GstPad`. This has already been discussed before in [Using capabilities
|
||||
for metadata](application-development/building/pads.md#using-capabilities-for-metadata).
|
||||
for metadata](application-development/basics/pads.md#using-capabilities-for-metadata).
|
||||
Therefore, we will skip it here. Note that this requires access to all
|
||||
pads of which you want stream information.
|
||||
|
||||
Tag reading is done through a bus in GStreamer, which has been discussed
|
||||
previously in [Bus](application-development/building/bus.md). You can listen for
|
||||
previously in [Bus](application-development/basics/bus.md). You can listen for
|
||||
`GST_MESSAGE_TAG` messages and handle them as you wish.
|
||||
|
||||
Note, however, that the `GST_MESSAGE_TAG` message may be fired multiple
|
||||
|
|
|
|||
|
|
@ -86,6 +86,6 @@ applications to GStreamer-0.10 in less than a day.
|
|||
`gst_init_get_option_group ()` is the new GOption-based equivalent
|
||||
to `gst_init_get_ptop_table ()`.
|
||||
|
||||
[bus]: application-development/building/bus.md
|
||||
[bus]: application-development/basics/bus.md
|
||||
[threads]: application-development/advanced/threads.md
|
||||
[queries-and-sevents]: application-development/advanced/queryevents.md
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ is an element itself, a bin can be handled in the same way as any other
|
|||
element. Therefore, the whole previous chapter ([Elements][elements]) applies
|
||||
to bins as well.
|
||||
|
||||
[elements]: application-development/building/elements.md
|
||||
[elements]: application-development/basics/elements.md
|
||||
|
||||
## What are bins
|
||||
|
||||
|
|
@ -22,7 +22,7 @@ would output decoded data. In the next chapter (see [Pads and
|
|||
capabilities][pads]), you will learn more about data input
|
||||
and output in elements, and how you can set that up in your application.
|
||||
|
||||
[pads]: application-development/building/pads.md
|
||||
[pads]: application-development/basics/pads.md
|
||||
|
||||
### Source elements
|
||||
|
||||
|
|
@ -385,7 +385,7 @@ the same bin or pipeline; if you want to link elements or pads at
|
|||
different hierarchy levels, you will need to use ghost pads (more about
|
||||
ghost pads later, see [Ghost pads][ghostpads]
|
||||
|
||||
[ghostpads]: application-development/building/pads.md#ghost-pads
|
||||
[ghostpads]: application-development/basics/pads.md#ghost-pads
|
||||
|
||||
## Element States
|
||||
|
||||
|
|
@ -450,7 +450,7 @@ pipeline, e.g. from within a "pad-added" signal callback, you need to
|
|||
set it to the desired target state yourself using `gst_element_set_state
|
||||
()` or `gst_element_sync_state_with_parent ()`.
|
||||
|
||||
[bus]: application-development/building/bus.md
|
||||
[bus]: application-development/basics/bus.md
|
||||
|
||||
1. The code for this example is automatically extracted from the
|
||||
documentation and built under `tests/examples/manual` in the
|
||||
|
|
@ -204,11 +204,11 @@ as follows:
|
|||
|
||||
|
||||
|
||||
[gst-init]: application-development/building/init.md
|
||||
[gst-init]: application-development/basics/init.md
|
||||
[advanced]: application-development/advanced/index.md
|
||||
[dynamic-pads]: application-development/building/pads.md#dynamic-or-sometimes-pads
|
||||
[bins]: application-development/building/bins.md
|
||||
[element-states]: application-development/building/elements.md#element-states
|
||||
[dynamic-pads]: application-development/basics/pads.md#dynamic-or-sometimes-pads
|
||||
[bins]: application-development/basics/bins.md
|
||||
[element-states]: application-development/basics/elements.md#element-states
|
||||
|
||||
## Compiling and Running helloworld.c
|
||||
|
||||
|
|
@ -11,7 +11,7 @@ media that the element can handle will be exposed by the pad's
|
|||
capabilities. We will talk more on capabilities later in this chapter
|
||||
(see [Capabilities of a pad](#capabilities-of-a-pad)).
|
||||
|
||||
[elements]: application-development/building/elements.md
|
||||
[elements]: application-development/basics/elements.md
|
||||
|
||||
## Pads
|
||||
|
||||
|
|
@ -91,7 +91,7 @@ debugging help and general tips to improve and simplify GStreamer
|
|||
programming.
|
||||
|
||||
[about]: application-development/introduction/index.md
|
||||
[app-building]: application-development/building/index.md
|
||||
[app-building]: application-development/basics/index.md
|
||||
[advanced]: application-development/advanced/index.md
|
||||
[highlevel]: application-development/highlevel/index.md
|
||||
[appendix]: application-development/appendix/index.md
|
||||
|
|
|
|||
16
sitemap.txt
16
sitemap.txt
|
|
@ -11,14 +11,14 @@ index.md
|
|||
application-development/introduction/gstreamer.md
|
||||
application-development/introduction/motivation.md
|
||||
application-development/introduction/basics.md
|
||||
application-development/building/index.md
|
||||
application-development/building/init.md
|
||||
application-development/building/elements.md
|
||||
application-development/building/bins.md
|
||||
application-development/building/bus.md
|
||||
application-development/building/pads.md
|
||||
application-development/building/data.md
|
||||
application-development/building/helloworld.md
|
||||
application-development/basics/index.md
|
||||
application-development/basics/init.md
|
||||
application-development/basics/elements.md
|
||||
application-development/basics/bins.md
|
||||
application-development/basics/bus.md
|
||||
application-development/basics/pads.md
|
||||
application-development/basics/data.md
|
||||
application-development/basics/helloworld.md
|
||||
application-development/advanced/index.md
|
||||
application-development/advanced/queryevents.md
|
||||
application-development/advanced/metadata.md
|
||||
|
|
|
|||
Loading…
Reference in a new issue