Fixed shell in docs/gst/Makefile.am and docs/libs/Makefile.am so that it works with...

[platform/upstream/gstreamer.git] / TODO

diff --git a/TODO b/TODO
index 36bcf07..c65aa57 100644 (file)
--- a/TODO
+++ b/TODO
@@ -10,13 +10,13 @@ before changes are accepted.
 target release ! description
                !
   0.4.1        ! expose and API to query the supported seek formats/flags on
-               ! pads, somthing like an extra arg to gst_pad_set_convert_function
+  (done)       ! pads, somthing like an extra arg to gst_pad_set_convert_function
                ! and gst_pad_set_event_function with some function to query the 
                ! flags and formats. more ideas in docs/random/wtay/query_events
               !  (API: medium dificulty)
               !
   0.4.1        ! add event for segment playback/looping and seeking (docs/random/wtay/segments)
-              !  (API: medium dificulty, plugins: HARD to very HARD)
+  (done)       !  (API: medium dificulty, plugins: HARD to very HARD)
               !
     ?          ! add event to adjust rate (reverse playback, slow motion, frame skipping)
                ! (docs/random/wtay/rate_event)
@@ -26,21 +26,26 @@ target release ! description
               ! (docs/random/wtay/scheduler_entry)
               !  (API: moderatly EASY, scheduler implementation MEDIUM)
               !
-    ?         ! create a design doc for a timecache implementation, 
-              !  (docs/wtay/random/timecache)
+   0.6.0       ! create a design doc for a timecache implementation, 
+   (done)      ! (docs/wtay/random/timecache)
               !  (API: MEDIUM, needs lots of discussion, plugin implementation MEDIUM to HARD)
+              ! (done: implemented using GstIndex base class + subclasses)
               !
     ?         ! implement a QoS event and a policy for handling the event.
                !  (API: kindof EASY, plugins MEDIUM to very HARD)
               !
-    ?         ! implement user defined GstFormat values, make a format factory etc..
-               !  (API: MEDIUM, plugins MEDIUM)
+   0.4.1       ! implement user defined GstFormat values, make a format factory etc..
+   (done)      !  (API: MEDIUM, plugins MEDIUM)
               !
     ?         ! strip the API to a bare bones minimal set of functions, leave the automatic
                ! stuff to the app instead of forcing a policy in the core.
               ! create a library with usefull higher level function for people who don't want
               ! to deal with the lowlevel stuff.
               ! (HARD, need to negotiate with people :))
+              !
+    ?         ! use GMarkup to load/save objects, remove dependency on libxml2
+               ! (MEDIUM) breaks API/ABI compatibility
+              !
               
 
 shortterm core feature enhancements
@@ -86,6 +91,26 @@ Policy definition is closely related to a HOWTO but sometimes needs some thinkin
               ! 
     ?         ! figure out a policy for the NEW_MEDIA event
               ! (MEDIUM to HARD)
+              !
+    ?          ! figure out how to better handle clock resync
+              ! (MEDIUM to HARD)
+              !
+            
+
+midterm feature enhancement
+---------------------------
+   
+  0.6.0        | Define and implement a syntax in gst_parse to handle filtered pad connections.
+  (done)       | (MEDIUM)
+              |
+    ?          | Figure out a way to set properties on schedulers (and bins?) from gst_parse.
+               | (MEDIUM)
+              |
+    ?          | Make gst-inspect do inspection of plugins, schedulers, autopluggers, types.
+               | An idea would be to make -inspect output an XML representation of the objects
+              | and use XSLT to transform this into text, HTML, docbook, ...
+               | (MEDIUM to EASY)
+              |
 
 
 midterm (longterm) optimisations
@@ -94,7 +119,7 @@ midterm (longterm) optimisations
 These optimisations can be done without changing the existing API.
 
 
-    ?          ! implement an optimal scheduler that uses chaining when possible
+ (in progress) ! implement an optimal scheduler that uses chaining when possible
                ! (HARD, requires detailed knowledge of element scheduling)
               !
     ?         ! alternatively optimisations to the current scheduler can be done such