Any thoughts on a new name for apitrace?

[Carl Worth]

As I recently started creating a new top-level binary program for
apitrace, it occurs to me that this program could use a better name.

One problem with "apitrace" is that the name is a bit too generic. What
we have here is a program to trace (and manipulate traces) graphics
APIs, but "apitrace" sounds much more generic than that.

In looking through the existing code, there are a few other names:

	gltrace
	glxtrace

both of which have the opposite problem. These are too specific since
the current code can trace some other graphics APIs besides OpenGL.

Additionally, we might prefer to have a name without "trace" in it. This
is a minor cosmetic thing in that a command like:

	apitrace trace <program>

just feels a bit redundant to type.[*]

So, what do you think. Do you agree we could use a better name? Do you
have any proposals for what we might use?

The one concrete proposal I was going to make was "gator" (for Graphics
Api Trace Or Replay) which works well for something you could feed huge
traces too (and parallels nicely with wireshark). But gator is
unfortunately already well as existing spyware software of some sort.

Anybody have any good name ideas?

-Carl

[*] I was tempted to make "apitrace <program>" without any "trace"
command implicitly mean to perform tracing. But this would lead to
problems such as a typo of "apitrace trim" as "apitrace trip" trying to
execute and trace a program named trip. Also, to support tracing a
program with the same name as an existing command we would need to allow
"apitrace -- <program>". And if user's have to type that, perhaps they
should just type the "trace" command explicitly.

-- 
carl.d.worth at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/apitrace/attachments/20111019/4f606e1c/attachment.pgp>