[Open-graphics] protocol, file format, and library for PCI analyzer

[Timothy Miller]

On 1/16/07, Dieter <netbsd at sopwith.solgatos.com> wrote:

> No.  We want the ability to have multiple config files to go with one
> data file.
>
> > Other kinds could/should be put into a key/value file
>
> Yes.  A key/value file.
>

I think we should have exactly none of this.  It will be necessary to
store trace dumps and trigger programs in files.  That is all we need
right now.  If you can make room for these things later, that's nice,
but certainly not necessary.

This isn't a word processor or web browser.  You're not going to have
a huge variety of users who want to customize, well, anything.  The
objective is to make it easy and intuitive for an engineer to view PCI
signals.  There is a minimum of analysis that that the software needs
to do as well.  It's mostly about presenting the signals clearly and
making it easy to navigate.

Why is everyone caught up in what color someone wants it to be?  I
don't think that should be a high priority.  I don't think it should
be a low priority.  I think it should be something that someone can
add to version 5, if they're really bored, and if it causes any
regression in usability, it should get ripped right back out.


-- 
Timothy Miller
http://www.cse.ohio-state.edu/~millerti