Make bench_pictures output a meaningful config name.

Make bench_pictures output a meaningful config name.

Committed: https://code.google.com/p/skia/source/detail?r=6288

[benchen, 2012-11-02 01:19:04]

LGTM

Thanks Leon. The names are much more meaningful than what I'd come up with. Plus
it seems future proof.

https://codereview.appspot.com/6813074/diff/1/tools/PictureRenderer.cpp
File tools/PictureRenderer.cpp (right):

https://codereview.appspot.com/6813074/diff/1/tools/PictureRenderer.cpp#newco...
tools/PictureRenderer.cpp:352: name.appendf("%.f%%", fTileWidthPercentage);
I'm a bit concerned with "%"s in the names as it might screw up something in
HTML.
But since 1) it should only affect urls and we can escape it, and 2) I don't
have better alternatives, I'll say let's try it until we find out we need to
change it.

[Leon, 2012-11-02 21:51:23]

https://codereview.appspot.com/6813074/diff/1/tools/PictureRenderer.cpp
File tools/PictureRenderer.cpp (right):

https://codereview.appspot.com/6813074/diff/1/tools/PictureRenderer.cpp#newco...
tools/PictureRenderer.cpp:352: name.appendf("%.f%%", fTileWidthPercentage);
On 2012/11/02 01:19:04, benchen wrote:
> I'm a bit concerned with "%"s in the names as it might screw up something in
> HTML.
> But since 1) it should only affect urls and we can escape it, and 2) I don't
> have better alternatives, I'll say let's try it until we find out we need to
> change it.

The good news is, at the moment, we do not use one with a percentage. (I suppose
one alternative is that I could say "50/100" instead of "50%".)

[Leon, 2012-11-02 21:52:50]

https://codereview.appspot.com/6813074/diff/1/tools/PictureRenderer.cpp
File tools/PictureRenderer.cpp (right):

https://codereview.appspot.com/6813074/diff/1/tools/PictureRenderer.cpp#newco...
tools/PictureRenderer.cpp:352: name.appendf("%.f%%", fTileWidthPercentage);
On 2012/11/02 21:51:23, scroggo-work wrote:
> On 2012/11/02 01:19:04, benchen wrote:
> > I'm a bit concerned with "%"s in the names as it might screw up something in
> > HTML.
> > But since 1) it should only affect urls and we can escape it, and 2) I don't
> > have better alternatives, I'll say let's try it until we find out we need to
> > change it.
> 
> The good news is, at the moment, we do not use one with a percentage. (I
suppose
> one alternative is that I could say "50/100" instead of "50%".)

Sorry for the awkward response. What I meant to say is that the bots never
actually set a width or height percentage (we currently only use 256x256) so
this path does not get taken.