fix packages for latest SDK changes

Fix packages for latest SDK changes
This is the observe/mdv/custom_element side of the changes.
Polymer changes are at https://chromiumcodereview.appspot.com/22254002

The big change here is we can't use a Stream for the MDV<->custom_element bridge, because Streams aren't re-entrant which makes them not useful for a sync event.

Also fixes createBinding to dispatch to the custom_element so we don't need to hack "bind" in PolymerElement

R=sigmund@google.com

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

[Siggi Cherem (dart-lang), 2013-08-05 20:20:51]

lgtm!

https://codereview.chromium.org/22253002/diff/1/pkg/mdv/lib/mdv.dart
File pkg/mdv/lib/mdv.dart (right):

https://codereview.chromium.org/22253002/diff/1/pkg/mdv/lib/mdv.dart#newcode54
pkg/mdv/lib/mdv.dart:54: // because custom elements are not upgraded during
clone()
seems the same as the TODO below, remove?

https://codereview.chromium.org/22253002/diff/1/pkg/mdv/lib/mdv.dart#newcode59
pkg/mdv/lib/mdv.dart:59: Set<DocumentFragmentCreated> get instanceCreated {
an alternative pattern to consider would be to do what we did in watchers long
time ago, where we made this registration a method and returned as a result a
closure that unregisters the callback.

https://codereview.chromium.org/22253002/diff/1/pkg/mdv/test/custom_element_b...
File pkg/mdv/test/custom_element_bindings_test.dart (right):

https://codereview.chromium.org/22253002/diff/1/pkg/mdv/test/custom_element_b...
pkg/mdv/test/custom_element_bindings_test.dart:129: callback(fragment) {
interesting, I didn't know this was equivalent to

var callback = (fragment) { ...};

I was afraid that maybe, like methods, each use of 'callback' as a variable
could have created a new closure for it. But, I did some testing and it seems to
work OK.

https://codereview.chromium.org/22253002/diff/1/pkg/observe/lib/src/microtask...
File pkg/observe/lib/src/microtask.dart (right):

https://codereview.chromium.org/22253002/diff/1/pkg/observe/lib/src/microtask...
pkg/observe/lib/src/microtask.dart:17: // the library "as microtask"?
sounds like a nice idea

[Jennifer Messerly, 2013-08-05 20:51:13]

Committed patchset #2 manually as r25799 (presubmit successful).

[Jennifer Messerly, 2013-08-05 20:51:15]

https://codereview.chromium.org/22253002/diff/1/pkg/mdv/lib/mdv.dart
File pkg/mdv/lib/mdv.dart (right):

https://codereview.chromium.org/22253002/diff/1/pkg/mdv/lib/mdv.dart#newcode54
pkg/mdv/lib/mdv.dart:54: // because custom elements are not upgraded during
clone()
On 2013/08/05 20:20:52, Siggi Cherem (dart-lang) wrote:
> seems the same as the TODO below, remove?

Done.

https://codereview.chromium.org/22253002/diff/1/pkg/mdv/lib/mdv.dart#newcode59
pkg/mdv/lib/mdv.dart:59: Set<DocumentFragmentCreated> get instanceCreated {
On 2013/08/05 20:20:52, Siggi Cherem (dart-lang) wrote:
> an alternative pattern to consider would be to do what we did in watchers long
> time ago, where we made this registration a method and returned as a result a
> closure that unregisters the callback.

yeah, this is basically private API though that should be gone soon :)