2005-11-10 Wim Taymans <wim@fluendo.com>
+ * docs/design/part-TODO.txt:
+ Updated todo.
+
+2005-11-10 Wim Taymans <wim@fluendo.com>
+
* gst/base/gstbasesink.c: (gst_base_sink_do_sync):
* gst/base/gstbasesrc.c: (gst_base_src_wait),
(gst_base_src_do_sync), (gst_base_src_get_range):
-
-- changing an object's name after construction is not allowed. Checks are performed
- when adding objects to parents that no duplicate names are used, changing the name
- to a duplicate name after adding it is therefore allowed and voids internal
- consistency.
+API/ABI
+-------
- implement return values from events in addition to the gboolean. This should be
done by making the event contain a GstStructure with input/output values, similar
after the seek you want to get the new stream time that will actually be used to
update the slider bar.
-- unlinking pads in the PAUSED state needs to make sure the stream thread is not
- executing code. Can this be done with a flush to unlock all downstream chain
- functions? Do we do this automatically or let the app handle this?
-
-- implement clock selection as explained in part-gstpipeline.txt.
-
-- when a pipeline with a live source goes to PAUSED again, a sample is prerolled
- in the sinks. This sample should be discarded, possibly with a flush event
- started from the source.
-
- convert framerate to GstFraction in GstCaps.
- implement latency calculation for live sources.
- query POSITION/DURATION return accuracy. Just a flag or accuracy percentage.
+
+IMPLEMENTATION
+--------------
+
+- implement clock selection as explained in part-gstpipeline.txt.
+
+
+DESIGN
+------
+
+- unlinking pads in the PAUSED state needs to make sure the stream thread is not
+ executing code. Can this be done with a flush to unlock all downstream chain
+ functions? Do we do this automatically or let the app handle this?
+
+- when a pipeline with a live source goes to PAUSED again, a sample is prerolled
+ in the sinks. This sample should be discarded, possibly with a flush event
+ started from the source.
+