[Plib-devel] puTrace and puFly

[Gil C. <g.c...@ca...>]

Hi,

In our little chats about my proposal for puTrace and puFly, there are a 
number of things which have dawned on me:

* puTrace and puFly are perhaps misnomers - perhaps they should be called 
PTL (PLIB Trace Library) and PFLY instead
* PTL is really two components - the measurement of rendering stats and 
their display.
* Since PLIB is comprised of more than just SSG, there's more to measure 
than just graphics performance - what else do people want to measure?
* Should PFLY seek to exercise *everything* in PLIB - joystick and sound 
also?  Currently, it's just targeted toward benchmarking SSG and using PUI 
to disply results, but it might be handy to have a known-good app for 
letting people debug sound and joystick problems in their own code.

If you guys can offer me some advice, I'll write up a more formal 
requirements analysis for both bits and post it for review.

Gil