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