Back after a little break

[José Fonseca]

I really like the "trace"/"retrace" dichotomy, but because I'm
apparently the only one and I'm not a native english speaker, I can
let it go.

But because I don't want to run into troubles because of this
renaming, this is what I must require:
- it must be an user-visible change only, ie, change only the docs,
CLI commands, GUI menus, etc
- backwards compatibility must be retained in CLI commands (i.e,
apitrace trace, apitrace retrace must alias to whatever is the new
name). But it's fine to hide / not-document these aliases
- no source file name/symbol renaming, at least not for now. I might
eventually do it in an opportune moment, but for now I want to avoid
merge conflicts.
- no executable renaming (glretrace, d3dretrace) as I have too many
private scripts that interface directly with those executables.

If this is acceptable, and you're willing to carry out the changes,
then I''ll merge it.

You might however want to reconsider the trace->record rename, as
there are apparently several people in the web interested in using
apitrace as an efficient way to record movies from OpenGL applications
(I saw two different blogs about it now), so one could easily envision
the need for a "record" like CLI command that creates a video from a
trace using video encoders like ffmpeg/mencoder/etc.

Jose