Skip to main content

Dart: My Experience Porting to Library v2

Updated: January 25, 2013: I ported the rest of my code. Hence, I updated the list below.

I ported all of my code to Dart lib v2. Here's what I had to do to get all of my projects to work:

  • Timer is now in 'dart:async', not 'dart:isolate'.
  • Element.elements is now Element.children.
  • LocalWindow is now Window.
  • window.webkitRequestFileSystem is now window.requestFileSystem.
  • Completer.completeException is now Completer.completeError.
  • Future.handleException is now Future.catchError. Furthermore, it no longer receives a "bare" exception object. It receives an AsyncError object. Use AsyncError.error to get the original exception object.
  • You have to use .then() and .catchError() in a single chain such as produceFuture().then((value) => null).catchError((e) => null). If you do this as two separate calls on the same future, the wrong thing will happen.
  • innerHTML is now innerHtml.
  • window.webkitNotifications is now window.notifications.
  • Map.keys and Map.values return iterators, not lists. This might break your code even if there are no static warnings. If you need a real list, call .toList() on the iterator.
  • BiquadFilterNode.type now takes a string such as "lowpass" instead of an int such as 0 or LOWPASS. I created a bug (http://code.google.com/p/dart/issues/detail?id=8119) to change that to a string.
  • AudioBufferSourceNode, BiquadFilterNode, etc. have connect and disconnect methods that have input and output parameters. It used to be acceptable to pass null for those parameters. To get the same behavior now, you must pass 0. You will not get a static warning if you don't update your code. It'll fail at runtime.
  • FileReader.readAsDataURL is now FileReader.readAsDataUrl.
  • StringBuffer.add no longer returns the StringBuffer. Use method cascades instead.
  • new Path.fromNative is now just new Path.
  • Iterable.some is now Iterable.any.
  • Iterable.map is now Iterable.mappedBy.
  • Future.chain is now Future.then.
  • Change "import 'dart:json'" to "import 'dart:json' as JSON" since there is no
  • JSON class anymore.

There are lots of other things that have changed, but those are the things that I got hit with.

Comments

Unknown said…
Great post, I was getting fumbled with the future.then().catchError() just now. Is this a bug or a feature?
jjinux said…
It's a feature. It's so that you can setup multiple chains of .then().catchError().

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p