Re: [Plib-devel] Work outstanding.

[Wolfram K. <w_...@rz...>]

Gil wrote:

>puTrace

Sounds great! Obviously, the more info on bottlenecks there is, the
better. For example, it would be GREAT to know how much
texture-swapping there is going on, but I doubt this can be done 
portably? 

I think the first step should be simply to measure all the things.
Displaying and(or sending them via TCP/IP is of secondary importance.

>puFly

Why not use PPE? It has several windows, a hierarchial view, great
viewing via mouse or keyboard or commands (for example, "view
everything"). It allows you to edit the model while seeing the
performance. Of course PPE can load all plib stuff, since it is build
on plib. We could create a new window for puTrace output.

>I'd *really* like to help with this.  Documentation is a pretty vital part 
>of getting newbies running, 

Yes.

>[autmatical docs]

I am not against them. But I think we need a handcrafted doc for the
users of plib as well. For example, you have to give an overview of
plib.This fits nowhere in the code.

>Gil

Bye bye,
Wolfram.