Monday, December 24, 2012
Friday, December 21, 2012
Wednesday, December 19, 2012
Tuesday, December 18, 2012
Bob Nystrom sends the good news:
As Anders' announcement email said, with M2 out the door, you can now publish packages yourself to pub.dartlang.org.
You'll need a Google account that you can use to authenticate. In theory, it's as simple as going into your package directory and running:
$ pub publish
It will walk you through the one-time authentication process, validate your package, and then you're good to go!
We've tested this as thoroughly as we could, but our experience has been that users in the wild have a much greater variety of machine, operating system, software, and account configurations than we can hope to test for.
Please be patient if you run into issues. File bugs and we'll do our best to sort them out as quickly as we can.
Also, if you've filed a package upload request that we haven't gotten yet (likely because we are waiting on more information from you), please consider yourself empowered to handle that on your own now. You hold the keys to the castle!Get started with pub by downloading the Dart SDK or Dart Editor. We look forward to your feedback!
Monday, December 17, 2012
Tuesday, December 11, 2012
If you've been waiting for the right time to learn how to use Web Components in Dart, now's your chance! Continuing where we left off with the Google IO 2012 Dart Codelab, I've created a Dart Web UI Codelab which focuses on Web Components and the new Web UI library.
In this codelab, I cover:
- How to set up pub
- How to use Web Components
- How to use dynamic templates and two-way data binding (inspired by Model-driven Views)
- How to build an application with multiple Web Components
- Where to get more information about Web Components and the Dart Web UI package
- What to do if you get stuck while trying to build an app using the Dart Web UI package
We've already created videos, blog posts, and articles about how to use Web Components in Dart, but this codelab is pretty exciting in that it walks you through building a complete, albeit small, application using Web Components and the Dart Web UI library. So give it a try and tell us what you think!
As always, we invite you to join our Dart mailing list, ask questions on Stack Overflow, or file feature requests on dartbug.com.
Monday, December 10, 2012
doc-code-merge is the opposite of what Donald Knuth labelled Literate Programming. doc-code-merge lets you write your documentation and your code examples completely separately. When you run doc_code_merge.dart, it makes a copy of your documentation with all the examples merged in. The Pragmatic Programmers mentioned using a similar tool when writing The Pragmatic Programmer: From Journeyman to Master, so the idea has probably been around for a while.
Using doc-code-merge is easy. Start by writing some documentation such as:
Although doc-code-merge is written in Dart, it'll work with almost any programming language and with almost any type of documentation as long as the documentation is written in text such as HTML or Markdown. We're hoping to make use of it for the Dart web site, dartlang.org, and for our book on Dart, Dart: Up and Running.
If you're interested in using doc-code-merge, check out the README. As always, we invite you to join the Dart mailing list and ask questions on Stack Overflow.
The benchmarks are run on a Linux ia32 architecture and follow the standard Dart benchmark harness. Over time, we'll add to the set of benchmarks being tracked. Of course, benchmarking is a subtle science, which is why we've published a short guide on benchmarking Dart.
It's still early for Dart VM, but we're encouraged by the initial performance boost for web developers. If you are too, download the Dart SDK and get started today. We encourage you to send feedback using our mailing list.
Written by Anders Johnsen, Speed Obsessed Software Engineer