+2007-08-27 Stefan Kost <ensonic@users.sf.net>
+
+ * docs/random/ensonic/dynlink.txt:
+ More thoughs on this.
+
+ * plugins/elements/gstcapsfilter.c:
+ Add bugzilla ticket number to FIXME comment.
+
2007-08-24 Wim Taymans <wim.taymans@gmail.com>
* docs/design/part-TODO.txt:
$Id$
Currently its only save to link/unlink elements/pad when pipeline is in READY.
+Belowe some thoughts. See http://bugzilla.gnome.org/show_bug.cgi?id=435487
+for patches.
= current api =
== swapping out an elelment ==
- * we have: e1 ! e2 ! e6
- * we have: e1 ! e2 ! e3 ! e6
- * we want: e1 ! e4 ! e5 ! e6
- * we want: e1 ! e3 ! e6
+* we have: e1 ! e2 ! e6
+* we have: e1 ! e2 ! e3 ! e6
+* we want: e1 ! e4 ! e5 ! e6
+* we want: e1 ! e3 ! e6
gst_element_swap_linked(e1, e4, e5, e6);
gst_pads_insert_link (e1.src, e4.sink, e5.src, e6.sink);
connect e1.src, e4.sink
connect e5.src, e6.sink
-
-
= thoughts =
* I don't think we need api for pads
* Should current api check for the state?
* do we want to swapp multiple elements at once
+== events ==
+* tee and adder need special treatment
+ * both would need to cache an accumulated segment
+ * tee
+ * would also cache tags
+ * when linkfunc is called, it can send out the segment and the tags
+ * when all pads got unlinked it could clear the segment
+ * adder
+ * when linkfunc gets called it sends a seek-event
+
+= ideas =
+== dynlinkpoint ==
+* use cases
+ * its ment to be used with one side disconnected to allow to connect elements
+ at runtime
+ * it can be used in a pipeline to remove/insert elements at runtime
+* element with 1 source- and 1 sinkpad
+* when both connected it passes data thru
+* if src is not connected it drops received buffers
+* if sink is not conected
+ * it does not push
+ * it creates silence on pull
+* events
+ * it caches events
+ * down: newsegment, tags, buffersize
+ * up: seek (needs to be modified)
+ * when other-pad get connected it pushes events depending on direction