Not obvious how to import a Dart package

[DartBot]

This issue was originally filed by [email protected]

---

Libraries declare their 'name' in their #library directive. This is the name that a user browsing the code sees, and the name that tools like dartdoc and the editor see and expose, but it has no relationship to the name that the user actually needs - the name that should be imported.

This currently causes much confusion around libraries that ship with the SDK but aren't built-in (see mailing list and e.g. bug 3702) and will equally cause confusion when people start using user libraries through pub.

These names should be the same, at least by convention.
E.g. built in libraries should be #library('dart:html'), user libraries should be #library('package:mypkg');
SDK libraries should be #library('$SDK_ROOT/lib/i18n') or similar, however is the recommended way of importing them.

[sethladd]

Added Area-Language, Language-Import, Triaged labels.

[DartBot]

This comment was originally written by @jinmingjian

---

no need. the behavor of importing a uri is nice. The spec has suggested a good usage of library directive: "In the future it may also serve to define a default prefix when importing". But, it is "in the future":) waits Gilad's refinement!

[DartBot]

This comment was originally written by @seaneagan

---

if the metadata proposal (http://news.dartlang.org/2012/06/proposal-to-add-metadata-to-dart.html) included library-level annotations, then #library('package:mypkg') could just merely be @­Library('package:mypkg') or similar.

[gbracha]

Expect improvements in this space.

---

Removed Type-Defect, Language-Import labels.
Added Type-Enhancement, Duplicate labels.
Marked as being merged into #1378.