Skip to main content

API Doc refresh

Posted by Bob Nystrom

Happy Wednesday, Dartisans!

We've just pushed a new batch of documentation to api.dartlang.org. It includes a slew of fun new things to help you be more productive with Dart.

We now show subclasses, subinterfaces, and implementing classes for each type. You can now see the full graph of types and click around to see how things are related to each other.

Docs for the server libraries! One of the most frequent questions we get is "what can I do on the standalone VM?" The libraries that answer that are still being fleshed out, but we've got nice documentation up now for what's there. No more hunting through old samples to try to guess at things. It's all right here: http://api.dartlang.org/io.html.

Last, but not least, we have documentation for our DOM and HTML libraries. The DOM is a huge API and documenting it is a monumental undertaking. Fortunately, the Mozilla folks and an army of honorable volunteers have tackled that at https://developer.mozilla.org/en/DOM. Even better, they've graciously done so under a Creative Commons license. This lets us include that documentation on api.dartlang.org, which you'll see now if you look at the dart:dom and dart:html docs (for example: http://api.dartlang.org/html/UListElement.html).

I can't tell you how much we appreciate being able to share this documentation and how cool it is of Mozilla and the contributors to allow this. This was made possible by community members like you, and we encourage you to improve the web by contributing to The Mozilla Developer Network. (Mozilla has no other association with Dart or dartlang.org.)


Cheers,
- Bob

Popular posts from this blog

Dart in 2016: The fastest growing programming language at Google, 2nd fastest growing in TIOBE Index

Dart was the fastest growing programming language at Google in 2016 with millions of lines of code written. It also made it to TIOBE Index Top 20 this month (see TIOBE's methodology ). It takes time to build something as ambitious as Dart and, in some ways, Dart is still in its infancy. But we're glad the hard work is starting to pay off. Many thanks to our amazing community! We're going to celebrate by ... releasing 1.22 next week (as per our usual 6 week release schedule).

AngularDart is going all Dart

Until now, the multiple language flavors of Angular 2 were written as TypeScript source, and then automatically compiled to both JavaScript and Dart. We're happy to announce that we’re splitting the Angular 2 codebase into two flavors – a Dart version and a TypeScript/JavaScript version – and creating a dedicated AngularDart team. This is amazing news for Dart developers because: The framework will feel more like idiomatic Dart. It will make use of Dart features that couldn't work with the TypeScript flavor. It will be faster. This is equally great news for our TypeScript and JavaScript developers, by the way. Cleaner API, performance gains, easier contributions. Read more on the Angular blog. Angular 2 for Dart is used by many teams at Google. Most famously by the AdWords team, but many other Google teams build large, mobile-friendly web apps. Some of the top requests from these teams were: make the API feel like Dart, provide a faster edit-refresh cycle, and

The new AdWords UI uses Dart — we asked why

Google just announced a re-designed AdWords experience. In case you’re not familiar with AdWords: businesses use it to advertise on google.com and partner websites. Advertising makes up majority of Google’s revenue, so when Google decides to completely redo the customer-facing front end to it, it’s a big deal. The Dart team is proud to say that this new front end is built with Dart and Angular 2. Whenever you asked us whether Google is ‘even using Dart for anything,’ this is what we had in mind but couldn’t say aloud. Until now. We asked Joshy Joseph , the primary technical lead on the project, some questions. Joshy is focusing on things like infrastructure, application latency and development velocity, so he’s the right person to ask about Dart.   Q: What exactly did we launch on Monday? It’s a complete redesign of the AdWords customer experience that is rolling out slowly as a test to a small initial set of advertisers. The most noticeable thing is probably the Material