Split out documentation into subfolders.

[platform/upstream/gstreamer.git] / markdown / pwg / other / base.md

diff --git a/pwg-other-base.md b/markdown/pwg/other/base.md
similarity index 99%
rename from pwg-other-base.md
rename to markdown/pwg/other/base.md
index e23c314..ebf5d9f 100644 (file)
--- a/pwg-other-base.md
+++ b/markdown/pwg/other/base.md
@@ -56,7 +56,7 @@ gst_my_sink_class_init (GstMySinkClass * klass)
   klass->render = [..];
 [..]
 }
-    
+
 ```
 
 The advantages of deriving from `GstBaseSink` are numerous:
@@ -64,7 +64,7 @@ The advantages of deriving from `GstBaseSink` are numerous:
   - Derived implementations barely need to be aware of preroll, and do
     not need to know anything about the technical implementation
     requirements of preroll. The base-class does all the hard work.
-    
+
     Less code to write in the derived class, shared code (and thus
     shared bugfixes).
 
@@ -137,7 +137,7 @@ videosink:
 ## Writing a source
 
 In the previous part, particularly [Providing random
-access](pwg-scheduling.md#providing-random-access), we have learned
+access](pwg/advanced/scheduling.md#providing-random-access), we have learned
 that some types of elements can provide random access. This applies most
 definitely to source elements reading from a randomly seekable location,
 such as file sources. However, other source elements may be better
@@ -207,4 +207,3 @@ Since the `GstBaseTransform` is based on the 1-to-1 model for filters,
 it may not apply well to elements such as decoders, which may have to
 parse properties from the stream. Also, it will not work for elements
 requiring more than one sourcepad or sinkpad.
-