-(1) Port LTTV to genevent-new parser.<br>
- # <A HREF="mailto:Mathieu Desnoyers <compudj@krystal.dyndns.org>>">Mathieu Desnoyers</A><br>
-(2) Fix bug with enums in lttv : make them use the value associated.<br>
-(4) create a event rate graphical view : Will be useful in conjonction with the
- filter.<br>
- # <A HREF="mailto:Parisa Heidari <parisa.heidari@polymtl.ca>">Parisa Heidari</A><br>
-(6) migrate align to lttv parser.<br>
-(7) create an analysis of function time (like a precise gprof)<br>
- -> with gcc -f inline-functions<br>
-(10) Add cancel button to LTTV filter GUI window.
+(3) Add cluster support.<br>
+ # <A HREF="mailto:Eric Clement <eric.clement@polymtl.ca>">Eric Clement</A><br>
+(3) Make LTTV aware of type formats (visual separators) defined in the XML
+file.<br>
+(3) Use a per architecture enumeration for traps.<br>
+(4) Add event specific fields support to filter.<br>
+(4) Add a periodic event interval view. (useful to verify event periodicity)<br>
+(4) create a graphical per cpu activity view.<br>
+(5) Add Python scripting hooks.<br>
+(5) Flight recorder : start lttd automatically upon GUI trace control stop.<br>
+(5) Automatically detect traces with too much processes and disable faulty operations.<br>
+(5) Event sequence detector (inspired from regular expressions).<br>
+(7) Create a hardware counter viewer (low cost rate counters : L1 cache miss,
+page faults, interrupts...). This will be a generalisation of the event rate
+view into a view of the evolution of a user definable event field.<br>
+<br>
+* TO FIX<br>
+(10) Event filter : event.time does not work.<br>
+(10) Add cancel button to LTTV filter GUI window.<br>
+(10) Sometimes, in the control flow view, a process with 0 creation time is
+created in addition to the real process itself. Seems to be caused by end of
+process life.<br>
+(10) Statistics do not take in account the time spent in the mode present at
+the beginning of the trace. Example : real time spent in system call on behalf
+of process 0.<br>