[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: gEDA-user: What is the current procedure and location to submit patches for PCB?
DJ Delorie wrote:
>> That, itself, sounds like a bug.
One wag once said something similar about a CPU design project I was
one. Paraphrasing: Just let some VP file a bug report that says:
"Product XXX does not exist". Then we can just keep amending that one
until we close it. That will greatly simplify having to remember
various bug reference numbers.
>
> Perhaps, but none of us have felt up to the challenge of creating a
> testsuite that involves multiple operating systems and image matching.
Yes, well. Been there a number of times, too. As to the multiple OS
issue, I'd say just pick one and then trust the ./configure stuff to
make the rest work and just spot check them.
The graphical output part is always nasty. Back when I managed a
validation lab that Windows GUI software came through, we had a tool
that did two things. 1. It intercepted the Windows API calls and
allowed you to check expected values for window decorations and widget
contents. ie: Did a window titled "Foo Editor" just pop up? Does it
have a button named "Close"?, etc. It also allowed you to script in
clicks and such forth so you could automated driving the GUI around. It
was a darn tedious tool to use. 2. The other major feature was a
pixel-XOR for selected windows. This was problematic, in that any
changes caused a fail. You could specify regions (simple rectangles, I
think) to be ignored. Anyway, that about exhausts my memory of the tool
-- I was in a pointy-hair position at the time and didn't actually spend
any time driving the tool.
It strikes me that now that gerbv has a library with a nice API, we
could do something like a pixel-XOR tool. It's a pretty crude way to
check GUI programs, but for simple test cases it may suffice. Doesn't
do much for screen comparisons, though.
-dave
>
>
> _______________________________________________
> geda-user mailing list
> geda-user@xxxxxxxxxxxxxx
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>
_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user