Making ScriptProcessorNode not an EventTarget.

tools/dom/templates/html/impl/impl_ScriptProcessorNode.darttemplate

Index: tools/dom/templates/html/impl/impl_ScriptProcessorNode.darttemplate
diff --git a/tools/dom/templates/html/impl/impl_ScriptProcessorNode.darttemplate b/tools/dom/templates/html/impl/impl_ScriptProcessorNode.darttemplate
new file mode 100644
index 0000000000000000000000000000000000000000..b5e6d202c2106400c90e7ee6a634896a08ff9e5c
--- /dev/null
+++ b/tools/dom/templates/html/impl/impl_ScriptProcessorNode.darttemplate
@@ -0,0 +1,18 @@
+// Copyright (c) 2013, the Dart project authors.  Please see the AUTHORS file
+// for details. All rights reserved. Use of this source code is governed by a
+// BSD-style license that can be found in the LICENSE file.
+
+part of $LIBRARY;
+
+$(ANNOTATIONS)class $CLASSNAME$EXTENDS$NATIVESPEC {
+  void set onAudioProcess(EventListener listener) {

[blois, 2013/03/13 00:46:49]

should probably be void callback(AudioProcessingEvent) rather than
EventListener.

[podivilov, 2013/03/13 07:57:56]

AFAIR we deliberately abandoned attribute event listeners in dart:html.
Can't we implement on.audioProcess.add/remove stuff on top of JS onaudioprocess
setter for consistency with other dart:html API?

[Emily Fortuna, 2013/03/13 23:35:21]

The reason this can't fit in like all the other event handlers is because
ScriptProcessorNode is not an EventTarget, and we were trying to avoid
reinventing the wheel of Stream providers for this special case where there can
only be one listener. In the newest CL I went ahead and did this though. 

+$if DART2JS
+    JS('void', '#.onaudioprocess = #', this, 
+        convertDartClosureToJS(listener, 1));
+$else
+    //TODO(antonm): Get this working on Dartium.
+$endif
+  }
+$!MEMBERS

[podivilov, 2013/03/13 07:57:56]

There's no onAudioProcess getter, right? Is it intentional?

+}
+