>>> I think the browser idea might be a bit clearer and easier
>>> to navigate, so that it's always clear what all the tests are
>>> by name, and both keyboard or mouse could navigate the tests
>>> consistently. (The browser would simply remain up while one
>>> cycles through the tests.)
>> +1, especially if you are volunteering to do the actual work!
>
> +1: Oh, yeah, sure. I did not care about usability back then. This was
> just a rough hack, so please, by all means, Greg's approach is so much
> nicer.
As promised:
http://seriss.com/people/erco/fltk/tmp/unittests-revised.cxx
Should be a standard build. Tested on linux.
I basically merged Ian's and Matthais' test programs together,
and put a some code at the bottom to handle the app.
You should be able to navigate all the tests either with
the mouse or the up/down arrow buttons.
You can just keep adding more tests.. should be scalable.
We could break the test code out into separate .cxx files
that are all brought together with a bunch of #include<>'s.
I had it that way when I started, but thought for now to
merge it all into a single file so that you could try it
out easily; we can always split it out later.
I can say it's nice to have the tests in separate files;
this way if you're the one adding a new test, you're in a file
that is all your own code, and not have to be distracted by
the other test code.
Feel free to tweak. Comments welcome.
_______________________________________________
fltk-dev mailing list
fltk-dev@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-dev
