Fancy use of PrimitiveFixture

I put a new case study up on fit.c2.com today. I had a chance to show 
Bob Martin some of the stuff I was doing with microcontroller software 
development but I glossed over how I was using Fit. This case study 
doesn't explain everything, but it does show some cleverly simple 
fixtures that build on PrimitiveFixture, an evolutionary dead end that 
I left in Fit for mostly historical reasons. (Jim Little was looking 
for an example where PrimitiveFixture was useful so this is also for 
him.) Here is some test output and the case study that explains it.

	http://c2.com/doc/Codosome-2/VideoCirclesOutput.htm -- test output
	http://fit.c2.com/wiki.cgi?TinyTv -- the case study about the fixtures

There is a methodological track I am following here that may not come 
out too strongly so I will say a few words about it here. In the old 
days we use to talk about "symbolic evalutation". This was a 
realization that we didn't have to actually compile a program to 
evaluate it. I think it fell out of favor because as often as not the 
eventual compilation was as likely as not to cause more problems and 
these would not be seen by symbolic evaluation.

But this was all before xp and tdd. I think that there is a huge 
opportunity for paired-tdd against symbolic evaluators, especially when 
the evaluators can raise the level of machine interaction to a level 
that a pair would want to discuss. I'll write more on this as I gain 
more experience. As always, I'm fishing for pairs (or clients) with 
similar interests who might want to explore with me. Best regards. -- 
Ward

--
Ward Cunningham
503-245-5633 v	mailto:[email protected]
503-246-5587 f	http://c2.com