4 (in no particular order)
10 * Allow clamping to a GL version or a number of extensions.
12 * Put (de)compression in a separate thread.
16 * Trace window sizes somehow
18 * Allow to distinguish between the calls really done by the program, vs the
19 fakes one necessary to retrace correctly.
21 * Start tracing on demand (e.g., key-press, or by frame no), emitting calls
22 that recreate all current state.
24 * Add option to include call stack frames in the trace.
26 * Trace the internal GL calls done by GLU on Mac OS X & Windows.
32 * Use visuals that best match those used in the trace; specially auto
33 detect single/double buffer visuals.
35 * Respect multiple context sharing of the traces.
37 * Support multiple threads
39 * Leverage `ARB_debug_output` where available.
49 * Visualize meshes in draw commands.
51 * Breakpointing and step-by-step debugging.
57 * Add retrace Replay all the calls in a trace
58 * Add dump-state Output the OpenGL state in JSON format
59 * Add dump-images Create image files for each frame/drawing operation of a trace
61 * Add some common command-line options:
63 Most commands acting on a trace accept the following common options:
65 --calls=[RANGE] Operate only on calls with index numbers within
68 --frames=[RANGE] Operate only on frames with index numbers within
71 --functions=[REGEXP] Operate only on function calls which have a
72 name that matches the given regular expression.
74 A [RANGE] can be any of the following:
78 4 A single number specifying a single call or frame.
80 10-20 Two numbers separated by '-' (FIRST-LAST) specifying a
81 range of consecutive calls/frames from FIRST to LAST. If
82 either of FIRST or LAST is omitted, the first or last
83 call/frame index in the trace will be used.
85 1-100/5 Either of the above range specifications followed by '/'
86 and a number (INTERVAL). This specifies the inclusion of
87 only each INTERVAL call/frame within the range. For
88 example, 1-100/5 species frame 1, frame 5, frame 10,
91 4,10-20/2 A comma separated list of any of the above range
92 specifications, specifying the union of the ranges.
94 * Add some retrace-specific options (-b, -db, -sb, -v)
96 * Add some trime-specific options (--every={draw,framebuffer,frame})
98 * Accept a filename for --calls or --functions (to use the same calls
99 or functions as present in a trace dump).
101 * Add an "apitrace bisect" for trimming down a trace based on user
104 * Add an "apitrace git-bisect-helper" for calling from git-bisect.
110 * Side-by-side trace diffing; either as a separate tool on or the GUI.
112 * Ability to extract just a single frame from a trace, and all previous calls
113 that contributed to it:
115 * via a state tracker (i.e., knowledge of how calls affect the state);
117 * or by leveragine retrace, dumping the calls to emit all state at beginning
123 * open issues on [github](https://github.com/apitrace/apitrace/issues)
125 * _Known issues_ section in BUGS.markdown
127 * FIXME, TODO, and XXX comments on the source code.