3 URL: http://www.polymer-project.org
5 Revision: (See components/<component>/.bower.json)
7 License File: LICENSE.polymer
11 This directory contains a copy of the following components which are a part of
14 -all core elements and their dependencies (except "core-docs",
15 "core-component-page", and "core-doc-viewer")
16 -all paper elements and their dependencies (except "paper-menu-button")
17 See bower.json for a full list of components.
19 The version can be found in header of polymer/polymer.js. The license can
20 be found in polymer/LICENSE.
22 The source git repositories can be found at:
23 https://github.com/Polymer/<component>
25 Polymer is comprised of two efforts:
26 1. A set of core platform features (Shadow DOM, Custom Elements, MDV).
27 Initially, these core features will be enabled with a set of polyfills. As
28 browsers begin to implement these new primitives, the polyfill platform layer
29 becomes smaller and better over time.
30 2. A next-generation web application framework built upon these core
31 technologies called the Polymer.
34 - Removed executable bit from the files in 'components/core-list'.
35 - Created a copy 'components-chromium' of the 'components' directory with the
36 only difference that all inline JavaScript blocks are extracted from Polymer
37 HTML elements to external JS files. This version of the Polymer is used in a web
38 UI, where CSP forbids an execution of inline scripts. The extraction was made
39 with the help of the Vulcanize tool (https://github.com/Polymer/vulcanize).
40 - Replaced CRLF line endings with LF line endings in text files.
42 To restore a content of the 'components', 'components-chromium' directorires
43 from scratch, run ./reproduce.sh (requires bower and vulcanize >= 0.7.2).
46 The directory can be updated by running "bower update". A new component can be
47 installed by running "bower install -S Polymer/<component>#version". Be sure to
48 add the .bower.json file to the repository as it includes the revision
49 information of the polymer component.
50 Also be sure that you listed all the added packages and **all their
51 dependencies** in bower.json, and specified **exact** versions of every package
52 explicitly. That is needed because Bower can't handle recursive dependencies
53 correctly (see http://stackoverflow.com/q/25899532).