More sensible JSON format for iterating

[GoogleCodeExporter]

Steve mentioned that the format of our JSON is lousy for iterating on, and I'm 
not surprised, as it's simply the same format that we use for creating our 
stats table and not really rethought for a simpler use-case.
This bug is a note that we should update that JSON to make it easier to iterate 
on. If anyone wants to make a suggestion for a new format, go for it, or I'll 
take a crack next time I want to use it myself.

Original issue reported on code.google.com by els...@gmail.com on 22 Aug 2010 at 11:19

[GoogleCodeExporter]

I've put together a suggestion for simplifying the data structure: 
https://gist.github.com/981518

Original comment by scott.go...@gmail.com on 19 May 2011 at 7:33

[GoogleCodeExporter]

FWIW, +1 to https://gist.github.com/981518#file_suggested.json

Original comment by math...@bodyfoams.com on 20 May 2011 at 9:30

[GoogleCodeExporter]

Alrighty, check this out:
http://www.browserscope.org/user/tests/table/agt1YS1wcm9maWxlcnIMCxIEVGVzdBirxHY
M?v=3&o=json
I renamed "display" to "result" and got rid of "score" (used to evaluate a 
result against other results on a 1-10, scale and probably not useful in JSON 
output)
If you're happy with this, I'll commit and close this issue.
Thanks for the feedback!

Original comment by els...@google.com on 20 May 2011 at 4:25

[GoogleCodeExporter]

fwiw v= matches whatever you pass in for the v URL parameter.

Original comment by els...@google.com on 20 May 2011 at 4:33

[GoogleCodeExporter]

That looks great.

Original comment by scott.go...@gmail.com on 20 May 2011 at 5:09

[GoogleCodeExporter]

This issue was closed by revision r820.

Original comment by els...@gmail.com on 20 May 2011 at 5:12

• Changed state: Fixed