Add pause/resume for isolates in vmservice/observatory.

Add pause/resume for isolates in vmservice/observatory.

Improve the isolate view and isolate summary.

Details:

- Rig DbgMsgQueueList so it can run even when the debugger hasn't started.

- Add <action-link> element for pause/resume actions.

- Introduce new flex-percentile css classes.

- Add <isolate-run-state>, <isolate-location>, <isolate-shared-summary>, and <isolate-counter-chart> elements.  Counters are now displayed as a pie chart instead of as text.

- Reorg <isolate-view> and <isolate-summary> substantially.

- Add shared style sheet to <script-view>.

- Combine pause-on-start/pause-on-exit with other debugger pause events and present a consistent representation for these in the vm service.  Reorg how pause events are shown in <isolate-run-state>.

- Give the user a nicer message when an isolate is still loading.

- Move the /resume command to /debug/resume.  Implement this with a bool in the Isolate class which is used to smuggle resume requests from the vm service to the dart embedding api.

- Add the /debug/pause command to the vm service

- Break the DebuggerEvent struct out into its own top-level class.  Add JSON printing.

etc.

R=johnmccutchan@google.com

Committed: https://code.google.com/p/dart/source/detail?r=36366

[Cutch, 2014-05-12 17:57:08]

lgtm with some comments.

https://codereview.chromium.org/271153002/diff/40001/runtime/bin/dbg_connecti...
File runtime/bin/dbg_connection.cc (right):

https://codereview.chromium.org/271153002/diff/40001/runtime/bin/dbg_connecti...
runtime/bin/dbg_connection.cc:343: if (listener_fd_ == -1) {
Maybe factor this into a predicate function. 

if (UsingServiceAsTransport()) {
  // Don't wait for a connection on debugger port.
  return;
}

https://codereview.chromium.org/271153002/diff/40001/runtime/bin/vmservice/cl...
File runtime/bin/vmservice/client/lib/src/elements/css/shared.css (right):

https://codereview.chromium.org/271153002/diff/40001/runtime/bin/vmservice/cl...
runtime/bin/vmservice/client/lib/src/elements/css/shared.css:170:
.flex-item-10-percent {
I would rename these to flex-item-fixed-10-percent because they are fixed size
(no grow or shrink allowed).

https://codereview.chromium.org/271153002/diff/40001/runtime/bin/vmservice/cl...
File runtime/bin/vmservice/client/lib/src/elements/isolate_view.dart (right):

https://codereview.chromium.org/271153002/diff/40001/runtime/bin/vmservice/cl...
runtime/bin/vmservice/client/lib/src/elements/isolate_view.dart:126: //
TODO(turnidge): Instead of asserting here, handle errors
This code is duplicated here and in the summary- does it make sense to move
these methods into Isolate?

Same fore resume()

https://codereview.chromium.org/271153002/diff/40001/runtime/bin/vmservice/cl...
File runtime/bin/vmservice/client/lib/src/service/object.dart (right):

https://codereview.chromium.org/271153002/diff/40001/runtime/bin/vmservice/cl...
runtime/bin/vmservice/client/lib/src/service/object.dart:615: loading = false;
Would be nice to generalize this for all ServiceObjects

https://codereview.chromium.org/271153002/diff/40001/runtime/vm/json_stream.h
File runtime/vm/json_stream.h (right):

https://codereview.chromium.org/271153002/diff/40001/runtime/vm/json_stream.h...
runtime/vm/json_stream.h:100: void PrintProperty(const char* name, const
DebuggerEvent* event);
I like this pattern.

[turnidge, 2014-05-20 17:09:30]

Committed patchset #7 manually as r36366 (presubmit successful).