From a76176f9e9d1482e308f05a2279d508c65a34f12 Mon Sep 17 00:00:00 2001 From: Stefan Kost Date: Mon, 6 Oct 2008 07:30:57 +0000 Subject: [PATCH] docs/pwg/advanced-request.xml: Fix 0.8 api usage in example. Fixes #554561 Original commit message from CVS: * docs/pwg/advanced-request.xml: Fix 0.8 api usage in example. Fixes #554561 * docs/pwg/appendix-porting.xml: Change 0.9 to 0.10 here. --- ChangeLog | 8 ++++++++ docs/pwg/advanced-request.xml | 2 +- docs/pwg/appendix-porting.xml | 20 ++++++++++---------- 3 files changed, 19 insertions(+), 11 deletions(-) diff --git a/ChangeLog b/ChangeLog index 1c46245b7e..145fba9efc 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,11 @@ +2008-10-06 Stefan Kost + + * docs/pwg/advanced-request.xml: + Fix 0.8 api usage in example. Fixes #554561 + + * docs/pwg/appendix-porting.xml: + Change 0.9 to 0.10 here. + 2008-10-06 Stefan Kost * docs/manual/basics-data.xml: diff --git a/docs/pwg/advanced-request.xml b/docs/pwg/advanced-request.xml index 8f2f03b0d2..67f9c9034a 100644 --- a/docs/pwg/advanced-request.xml +++ b/docs/pwg/advanced-request.xml @@ -253,7 +253,7 @@ gst_my_filter_request_new_pad (GstElement *element, context = g_new0 (GstMyFilterInputContext, 1); pad = gst_pad_new_from_template (templ, name); - gst_element_set_private_data (pad, context); + gst_pad_set_element_private (pad, context); /* normally, you would set _link () and _getcaps () functions here */ diff --git a/docs/pwg/appendix-porting.xml b/docs/pwg/appendix-porting.xml index 5a3b771229..8c3d9cf922 100644 --- a/docs/pwg/appendix-porting.xml +++ b/docs/pwg/appendix-porting.xml @@ -1,13 +1,13 @@ - Porting 0.8 plug-ins to 0.9 + Porting 0.8 plug-ins to 0.10 This section of the appendix will discuss shortly what changes to plugins will be needed to quickly and conveniently port most - applications from &GStreamer;-0.8 to &GStreamer;-0.9, with references + applications from &GStreamer;-0.8 to &GStreamer;-0.10, with references to the relevant sections in this Plugin Writer's Guide where needed. With this list, it should be possible to port most plugins to - &GStreamer;-0.9 in less than a day. Exceptions are elements that will - require a base class in 0.9 (sources, sinks), in which case it may take + &GStreamer;-0.10 in less than a day. Exceptions are elements that will + require a base class in 0.10 (sources, sinks), in which case it may take a lot longer, depending on the coder's skills (however, when using the GstBaseSink and GstBaseSrc base-classes, it shouldn't be all too bad), and elements requiring @@ -21,15 +21,15 @@ - Discont events have been replaced by newsegment events. In 0.9, it is + Discont events have been replaced by newsegment events. In 0.10, it is essential that you send a newsegment event downstream before you send your first buffer (in 0.8 the scheduler would invent discont events if - you forgot them, in 0.9 this is no longer the case). + you forgot them, in 0.10 this is no longer the case). - In 0.9, buffers have caps attached to them. Elements should allocate + In 0.10, buffers have caps attached to them. Elements should allocate new buffers with gst_pad_alloc_buffer (). See for more details. @@ -57,7 +57,7 @@ be _get ()-based or _loop ()-based, and any other element could be _chain ()-based or _loop ()-based, with - no limitations. Scheduling in 0.9 is simpler for the scheduler, + no limitations. Scheduling in 0.10 is simpler for the scheduler, and the element is expected to do some more work. Pads get assigned a scheduling mode, based on which they can either operate in random access-mode, in pipeline driving mode or in @@ -78,7 +78,7 @@ For as far as possible, elements should try to use existing base - classes in 0.9. Sink and source elements, for example, could derive + classes in 0.10. Sink and source elements, for example, could derive from GstBaseSrc and GstBaseSink. Audio sinks or sources could even derive from audio-specific base classes. All existing base classes @@ -88,7 +88,7 @@ - In 0.9, event handling and buffers are separated once again. This + In 0.10, event handling and buffers are separated once again. This means that in order to receive events, one no longer has to set the GST_FLAG_EVENT_AWARE flag, but can simply set an event handling function on the element's sinkpad(s), using