| Index: third_party/pkg/angular/lib/core_dom/template_cache.dart
|
| diff --git a/third_party/pkg/angular/lib/core_dom/template_cache.dart b/third_party/pkg/angular/lib/core_dom/template_cache.dart
|
| deleted file mode 100644
|
| index ae1f423dbe618265130196fc7d1fc637a7dfe049..0000000000000000000000000000000000000000
|
| --- a/third_party/pkg/angular/lib/core_dom/template_cache.dart
|
| +++ /dev/null
|
| @@ -1,73 +0,0 @@
|
| -part of angular.core.dom;
|
| -
|
| -/**
|
| - * Infinite cache service for templates loaded from URLs.
|
| - *
|
| - * All templates that are loaded from a URL are cached indefinitely in the
|
| - * TemplateCache the first time they are needed. This includes templates loaded
|
| - * via `ng-include` or via the `templateUrl` field on components decorated with
|
| - * [NgComponent].
|
| - *
|
| - * All attempts that require loading a template from a URL are first checked
|
| - * against this cache. Only when there is a cache miss is a network request
|
| - * attempted.
|
| - *
|
| - * You are welcome to pre-load / seed the TemplateCache with templates for URLs
|
| - * in advance to avoid the network hit on first load.
|
| - *
|
| - * There are two ways to seed the TemplateCache – (1) imperatively via and
|
| - * `TemplateCache` service or (2) declaratively in HTML via the `<template>`
|
| - * element (handled by [NgTemplateElementDirective]).
|
| - *
|
| - * Here is an example that illustrates both techniques
|
| - * ([view in plunker](http://plnkr.co/edit/JCsxhH?p=info)):
|
| - *
|
| - * Example:
|
| - *
|
| - * // main.dart
|
| - * import 'package:angular/angular.dart';
|
| - *
|
| - * @NgDirective(selector: '[main-controller]')
|
| - * class LoadTemplateCacheDirective {
|
| - * LoadTemplateCacheDirective(TemplateCache templateCache, Scope scope) {
|
| - * // Method 1 (imperative): Via the injected TemplateCache service.
|
| - * templateCache.put(
|
| - * 'template_1.html', new HttpResponse(200, 't1: My name is {{name}}.'));
|
| - * scope.name = "chirayu";
|
| - * }
|
| - * }
|
| - *
|
| - * main() {
|
| - * ngBootstrap([new AngularModule()..type(LoadTemplateCacheDirective)], 'html');
|
| - * }
|
| - *
|
| - * and
|
| - *
|
| - * <!-- index.html -->
|
| - * <html>
|
| - * <head>
|
| - * <script src="packages/browser/dart.js"></script>
|
| - * <script src="main.dart" type="application/dart"></script>
|
| - *
|
| - * <!-- Method 2 (declarative): Via the template directive. -->
|
| - * <template id="template_2.html" type="text/ng-template">
|
| - * t2: My name is {{name}}.
|
| - * </template>
|
| - * </head>
|
| - * <body load-template-cache>
|
| - * template_1.html: <div ng-include="'template_1.html'"></div><br>
|
| - * template_2.html: <div ng-include="'template_2.html'"></div><br>
|
| - * </body>
|
| - * </html>
|
| - *
|
| - * Neither `ng-include` above will result in a network hit. This means that it
|
| - * isn't necessary for your webserver to even serve those templates.
|
| - *
|
| - * `template_1.html` is preloaded into the [TemplateCache] imperatively by
|
| - * `LoadTemplateCacheDirective` while `template_2.html` is preloaded via the
|
| - * `<template id="template_2.html" type="text/ng-template">` element
|
| - * declaratively in the `<head>` of HTML.
|
| - */
|
| -class TemplateCache extends LruCache<String, HttpResponse> {
|
| - TemplateCache({int capacity}): super(capacity: capacity);
|
| -}
|
|
|
Chromium Code Reviews
Issue 1058283006:
Update pubspecs and dependencies to get pkgbuild tests working. (Closed)
Base URL: https://dart.googlecode.com/svn/branches/bleeding_edge/dart