A sketch of a command-line interface for apitrace

[José Fonseca]

On Wed, Oct 26, 2011 at 12:42 AM, Carl Worth <cworth at cworth.org> wrote:
> On Tue, 25 Oct 2011 22:51:59 +0100, José Fonseca <jose.r.fonseca at gmail.com> wrote:
>> I'll defer to Zack here.  But from my POV, the GUI should be a equal
>> citizen as the CLI. One can imagine that certain users might want to
>> use strictly the GUI.
>
> OK. But surely we can come up with a better name than qapitrace? How
> about apitrace-gui at the very least. Installing this in <prefix>/bin is
> fine.

That sounds fine by me too.

> We don't really want people creating menu entires and desktop
> icons, etc. that reach into /usr/lib/apitrace.

Agree.

>> The only tricky business here is that on windows the .py extension is
>> required. We can always fix up at install time, but in the git tree
>> the scripts should be named either with .py or without, so I'm not
>> sure what's best.
>
> As long as the apitrace program knows how to find its private programs
> inside /usr/lib/apitrace I don't care what the actual names are. So we
> can have "ugly" .py extensions and the actual users should be totally
> unaffected by this.

Yes, good point.

> Anyway, the next email from me will have actual code attached.
>
> Thanks for the discussion.

Looking forward to it Carl. Thanks for taking the initiative.

Jose