Add the ability to export the captured NetLog data to a formatted text file, ...

Add the ability to export the captured NetLog data to a formatted text file, or to JSON.

This is similar to the display of about:net-internals, and is intended to be used when attaching log info to bug reports.

The formatting is still fairly crude, and there are some remaining TODOs.

BUG=37421
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=45967

[eroman, 2010-04-29 00:08:28]

Entry point:  http://i.imgur.com/1KLzf.png
Text dump: http://i.imgur.com/pq5dk.png
JSON dump: http://i.imgur.com/XERqP.png

[Mike Belshe, 2010-04-29 16:44:53]

LGTM

In the UI, I think you should just fill in the text (for cut and paste) when the
user clicks on the "Data" tab.  You can have a button for the json stuff.  This
removes one click for the user when filling out bug reports.  But, not a big
deal.

Or maybe the button of the text should read, "Click here to generate bug report
data" rather than "Export data (text)".

[eroman, 2010-04-29 18:24:37]

Done. (I renamed the button per your suggestion).

For now I decided to leave it as an extra click, since it wasn't trivial to
address some of the difficulties that arise when inlining.

Perhaps I could turn the button into a "Copy to clipboard" button to make up the
extra click.

The UI issues I had with  inlining:

  * How to deal with dynamic updates; the user's expectation will be for the
tab's contents to change as new data is captured (since this is what the other
tabs do). However if the text is changing, that makes it more difficult to do an
atomic copy-paste since the selection changes. Conversely, if the text is not
being updated dynamically, we run the risk of the user copy-pasting old data.

  * I will probably be adding some extra buttons to this tab, in order to
provide a mechanism for importing data (from JSON), and for resetting all the
captured data.