Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(213)

Unified Diff: third_party/polymer/components-chromium/core-meta/core-meta.html

Issue 1215543002: Remove Polymer 0.5. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: fix unit test Created 5 years, 6 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: third_party/polymer/components-chromium/core-meta/core-meta.html
diff --git a/third_party/polymer/components-chromium/core-meta/core-meta.html b/third_party/polymer/components-chromium/core-meta/core-meta.html
deleted file mode 100644
index 60f4b3bdf1a2c89aa01ca9109512b947f3b2a0b0..0000000000000000000000000000000000000000
--- a/third_party/polymer/components-chromium/core-meta/core-meta.html
+++ /dev/null
@@ -1,59 +0,0 @@
-<!--
-Copyright (c) 2014 The Polymer Project Authors. All rights reserved.
-This code may only be used under the BSD style license found at http://polymer.github.io/LICENSE.txt
-The complete set of authors may be found at http://polymer.github.io/AUTHORS.txt
-The complete set of contributors may be found at http://polymer.github.io/CONTRIBUTORS.txt
-Code distributed by Google as part of the polymer project is also
-subject to an additional IP rights grant found at http://polymer.github.io/PATENTS.txt
---><!--
-`core-meta` provides a method of constructing a self-organizing database.
-It is useful to collate element meta-data for things like catalogs and for
-designer.
-
-Example, an element folder has a `metadata.html` file in it, that contains a
-`core-meta`, something like this:
-
- <core-meta id="my-element" label="My Element">
- <property name="color" value="blue"></property>
- </core-meta>
-
-An application can import as many of these files as it wants, and then use
-`core-meta` again to access the collected data.
-
- <script>
- var meta = document.createElement('core-meta');
- console.log(meta.list); // dump a list of all meta-data elements that have been created
- </script>
-
-Use `byId(id)` to retrive a specific core-meta.
-
- <script>
- var meta = document.createElement('core-meta');
- console.log(meta.byId('my-element'));
- </script>
-
-By default all meta-data are stored in a single databse. If your meta-data
-have different types and want them to be stored separately, use `type` to
-differentiate them.
-
-Example:
-
- <core-meta id="x-foo" type="xElt"></core-meta>
- <core-meta id="x-bar" type="xElt"></core-meta>
- <core-meta id="y-bar" type="yElt"></core-meta>
-
- <script>
- var meta = document.createElement('core-meta');
- meta.type = 'xElt';
- console.log(meta.list);
- </script>
-
-@group Polymer Core Elements
-@element core-meta
-@homepage github.io
---><html><head><link rel="import" href="../polymer/polymer.html">
-
-</head><body><polymer-element name="core-meta" attributes="label type" hidden="" assetpath="">
-
-</polymer-element>
-<script charset="utf-8" src="core-meta-extracted.js"></script></body></html>

Powered by Google App Engine
This is Rietveld 408576698