OLD | NEW |
---|---|
1 Name: Polymer | 1 Name: Polymer |
2 Short Name: polymer | 2 Short Name: polymer |
3 URL: http://www.polymer-project.org | 3 URL: http://www.polymer-project.org |
4 Version: 0.5.2-4 | 4 Version: 1.2.3 |
5 Revision: (See components/<component>/.bower.json) | 5 Revision: (see v1_0/components_summary.txt) |
6 License: BSD | 6 License: BSD |
7 License File: LICENSE.polymer | 7 License File: LICENSE.polymer |
8 Security Critical: no | 8 Security Critical: no |
9 | 9 |
10 Description: | 10 Description: |
11 This directory contains a copy of the following components which are a part of | 11 This directory contains a copy of the Polymer framework and some elements from |
12 the Polymer project: | 12 the Polymer elements catalog (https://elements.polymer-project.org/). See |
13 -polymer | 13 v1_0/components_summary.txt for a full list of components. |
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. | |
18 | |
19 The version can be found in header of polymer/polymer.js. The license can | |
20 be found in polymer/LICENSE. | |
21 | 14 |
22 The source git repositories can be found at: | 15 The source git repositories can be found at: |
23 https://github.com/Polymer/<component> | 16 https://github.com/Polymer/polymer |
17 https://github.com/PolymerElements/<component-name> | |
michaelpg
2016/01/23 04:28:15
+PolymerLabs for polymer-externs
dzhioev (left Google)
2016/01/25 23:31:35
Done.
| |
24 | 18 |
25 Polymer is comprised of two efforts: | 19 Polymer is comprised of two efforts: |
26 1. A set of core platform features (Shadow DOM, Custom Elements, MDV). | 20 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 | 21 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 | 22 browsers begin to implement these new primitives, the polyfill platform layer |
29 becomes smaller and better over time. | 23 becomes smaller and better over time. |
30 2. A next-generation web application framework built upon these core | 24 2. A next-generation web application framework built upon these core |
31 technologies called the Polymer. | 25 technologies called the Polymer. |
32 | 26 |
33 Local Modifications: | 27 Local Modifications: |
34 - Removed executable bit from the files in 'components/core-list'. | 28 - Applied modifications that can be found in v1_0/chromium.patch. |
35 - Created a copy 'components-chromium' of the 'components' directory with the | 29 - All inline JavaScript blocks are extracted from Polymer HTML elements to |
36 only difference that all inline JavaScript blocks are extracted from Polymer | 30 external JS files. This version of the Polymer is used in a web UI, where CSP |
37 HTML elements to external JS files. This version of the Polymer is used in a web | 31 forbids an execution of inline scripts. The extraction was made with the help of |
38 UI, where CSP forbids an execution of inline scripts. The extraction was made | 32 the Crisper tool (https://github.com/PolymerLabs/crisper). |
39 with the help of the Vulcanize tool (https://github.com/Polymer/vulcanize). | 33 - Removed executable bit from some files. |
34 - Resolved encoding issues. | |
40 - Replaced CRLF line endings with LF line endings in text files. | 35 - Replaced CRLF line endings with LF line endings in text files. |
41 | 36 |
42 To restore a content of the 'components', 'components-chromium' directorires | 37 To restore a content of the 'components-chromium' directory from scratch, run |
43 from scratch, run ./reproduce.sh (requires bower and vulcanize >= 0.7.2). | 38 ./v1_0/reproduce.sh (requires bower and crisper) on a Linux machine. |
44 | 39 |
45 Note on Bower: | 40 Note on Bower: |
46 The directory can be updated by running "bower update". A new component can be | 41 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 | 42 installed by running "bower install -S PolymerElements/<component>#version". |
48 add the .bower.json file to the repository as it includes the revision | 43 Be sure to add the .bower.json file to the repository as it includes the |
49 information of the polymer component. | 44 revision information of the polymer component. |
50 Also be sure that you listed all the added packages and **all their | 45 Also be sure that you listed all the added packages in bower.json. |
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). | |
OLD | NEW |