Dart: Adds a content handler and a test.

mojo/public/dart/bindings.dart

Index: mojo/public/dart/bindings.dart
diff --git a/mojo/public/dart/bindings.dart b/mojo/public/dart/bindings.dart
index 5d6298ed63d3d634ccf6cba84f859f3eedc7c809..168d9be07f9d1b9a714c2c0b3e20e1a7344cc370 100644
--- a/mojo/public/dart/bindings.dart
+++ b/mojo/public/dart/bindings.dart
@@ -10,8 +10,14 @@ import 'dart:mirrors';
 import 'dart:mojo_core' as core;
 import 'dart:typed_data';
 
+import 'package:mojo/public/interfaces/application/application.mojom.dart' as application;
+import 'package:mojo/public/interfaces/application/service_provider.mojom.dart' as service_provider;
+import 'package:mojo/public/interfaces/application/shell.mojom.dart' as shell;

[abarth-chromium, 2015/01/16 05:43:43]

This is a bit of a layering violation.  The code in mojo/public/dart shouldn't
know anything about applications, service providers, or shells.  Those are
concepts built up on top of the underlying language buildings.  In principle,
you could build a completely different set of services and conventions on top of
the language bindings.

Instead, these concepts belong in the dart_content_handler, which is the layer
of the system that starts understanding the constellation of services that
exist.

[zra, 2015/01/16 17:54:51]

Moved to an application library under //services/dart/

+
+part 'src/application.dart';
 part 'src/client.dart';
 part 'src/codec.dart';
 part 'src/interface.dart';
 part 'src/message.dart';
+part 'src/service_provider.dart';
 part 'src/struct.dart';