+
+
+
+
+
+
+
diff --git a/components/fontawesome-iconset/fa-icons.html b/components/fontawesome-iconset/fa-icons.html
new file mode 100644
index 0000000000..b3db19c01b
--- /dev/null
+++ b/components/fontawesome-iconset/fa-icons.html
@@ -0,0 +1,975 @@
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/iron-flex-layout/CONTRIBUTING.md b/components/iron-flex-layout/CONTRIBUTING.md
new file mode 100644
index 0000000000..f147978a3e
--- /dev/null
+++ b/components/iron-flex-layout/CONTRIBUTING.md
@@ -0,0 +1,77 @@
+
+
+# Polymer Elements
+## Guide for Contributors
+
+Polymer Elements are built in the open, and the Polymer authors eagerly encourage any and all forms of community contribution. When contributing, please follow these guidelines:
+
+### Filing Issues
+
+**If you are filing an issue to request a feature**, please provide a clear description of the feature. It can be helpful to describe answers to the following questions:
+
+ 1. **Who will use the feature?** _“As someone filling out a form…”_
+ 2. **When will they use the feature?** _“When I enter an invalid value…”_
+ 3. **What is the user’s goal?** _“I want to be visually notified that the value needs to be corrected…”_
+
+**If you are filing an issue to report a bug**, please provide:
+
+ 1. **A clear description of the bug and related expectations.** Consider using the following example template for reporting a bug:
+
+ ```markdown
+ The `paper-foo` element causes the page to turn pink when clicked.
+
+ ## Expected outcome
+
+ The page stays the same color.
+
+ ## Actual outcome
+
+ The page turns pink.
+
+ ## Steps to reproduce
+
+ 1. Put a `paper-foo` element in the page.
+ 2. Open the page in a web browser.
+ 3. Click the `paper-foo` element.
+ ```
+
+ 2. **A reduced test case that demonstrates the problem.** If possible, please include the test case as a JSBin. Start with this template to easily import and use relevant Polymer Elements: [https://jsbin.com/cagaye/edit?html,output](https://jsbin.com/cagaye/edit?html,output).
+
+ 3. **A list of browsers where the problem occurs.** This can be skipped if the problem is the same across all browsers.
+
+### Submitting Pull Requests
+
+**Before creating a pull request**, please ensure that an issue exists for the corresponding change in the pull request that you intend to make. **If an issue does not exist, please create one per the guidelines above**. The goal is to discuss the design and necessity of the proposed change with Polymer authors and community before diving into a pull request.
+
+When submitting pull requests, please provide:
+
+ 1. **A reference to the corresponding issue** or issues that will be closed by the pull request. Please refer to these issues in the pull request description using the following syntax:
+
+ ```markdown
+ (For a single issue)
+ Fixes #20
+
+ (For multiple issues)
+ Fixes #32, fixes #40
+ ```
+
+ 2. **A succinct description of the design** used to fix any related issues. For example:
+
+ ```markdown
+ This fixes #20 by removing styles that leaked which would cause the page to turn pink whenever `paper-foo` is clicked.
+ ```
+
+ 3. **At least one test for each bug fixed or feature added** as part of the pull request. Pull requests that fix bugs or add features without accompanying tests will not be considered.
+
+If a proposed change contains multiple commits, please [squash commits](https://www.google.com/url?q=http://blog.steveklabnik.com/posts/2012-11-08-how-to-squash-commits-in-a-github-pull-request) to as few as is necessary to succinctly express the change. A Polymer author can help you squash commits, so don’t be afraid to ask us if you need help with that!
diff --git a/components/iron-flex-layout/README.md b/components/iron-flex-layout/README.md
new file mode 100644
index 0000000000..219fca7d72
--- /dev/null
+++ b/components/iron-flex-layout/README.md
@@ -0,0 +1,55 @@
+
+
+
+[](https://travis-ci.org/PolymerElements/iron-flex-layout)
+
+_[Demo and API docs](https://elements.polymer-project.org/elements/iron-flex-layout)_
+
+
+##<iron-flex-layout>
+
+The `` component provides simple ways to use
+[CSS flexible box layout](https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Flexible_boxes),
+also known as flexbox. This component provides two different ways to use flexbox:
+
+1. [Layout classes](https://github.com/PolymerElements/iron-flex-layout/tree/master/iron-flex-layout-classes.html).
+The layout class stylesheet provides a simple set of class-based flexbox rules, that
+let you specify layout properties directly in markup. You must include this file
+in every element that needs to use them.
+
+Sample use:
+
+
+
+
+
+
+
cross axis start alignment
+
+
+1. [Custom CSS mixins](https://github.com/PolymerElements/iron-flex-layout/blob/master/iron-flex-layout.html).
+The mixin stylesheet includes custom CSS mixins that can be applied inside a CSS rule using the `@apply` function.
+
+
+
+Please note that the old [/deep/ layout classes](https://github.com/PolymerElements/iron-flex-layout/tree/master/classes)
+are deprecated, and should not be used. To continue using layout properties
+directly in markup, please switch to using the new `dom-module`-based
+[layout classes](https://github.com/PolymerElements/iron-flex-layout/tree/master/iron-flex-layout-classes.html).
+Please note that the new version does not use `/deep/`, and therefore requires you
+to import the `dom-modules` in every element that needs to use them.
+
+A complete [guide](https://elements.polymer-project.org/guides/flex-layout) to `` is available.
+
+
diff --git a/components/iron-flex-layout/bower.json b/components/iron-flex-layout/bower.json
new file mode 100644
index 0000000000..e175297334
--- /dev/null
+++ b/components/iron-flex-layout/bower.json
@@ -0,0 +1,31 @@
+{
+ "name": "iron-flex-layout",
+ "version": "1.3.1",
+ "description": "Provide flexbox-based layouts",
+ "keywords": [
+ "web-components",
+ "polymer",
+ "layout"
+ ],
+ "main": "iron-flex-layout.html",
+ "private": true,
+ "license": "http://polymer.github.io/LICENSE.txt",
+ "authors": [
+ "The Polymer Authors"
+ ],
+ "repository": {
+ "type": "git",
+ "url": "git://github.com/PolymerElements/iron-flex-layout.git"
+ },
+ "dependencies": {
+ "polymer": "Polymer/polymer#^1.1.0"
+ },
+ "devDependencies": {
+ "iron-component-page": "polymerelements/iron-component-page#^1.0.0",
+ "iron-demo-helpers": "PolymerElements/iron-demo-helpers#^1.0.0",
+ "test-fixture": "PolymerElements/test-fixture#^1.0.0",
+ "webcomponentsjs": "webcomponents/webcomponentsjs#^0.7.0",
+ "web-component-tester": "^4.0.0"
+ },
+ "ignore": []
+}
diff --git a/components/iron-flex-layout/classes/iron-flex-layout.html b/components/iron-flex-layout/classes/iron-flex-layout.html
new file mode 100644
index 0000000000..0c6aad604b
--- /dev/null
+++ b/components/iron-flex-layout/classes/iron-flex-layout.html
@@ -0,0 +1,311 @@
+
+
+
+
+
+
+
diff --git a/components/iron-flex-layout/classes/iron-shadow-flex-layout.html b/components/iron-flex-layout/classes/iron-shadow-flex-layout.html
new file mode 100644
index 0000000000..196df284c0
--- /dev/null
+++ b/components/iron-flex-layout/classes/iron-shadow-flex-layout.html
@@ -0,0 +1,307 @@
+
+
+
+
+
diff --git a/components/iron-flex-layout/demo/index.html b/components/iron-flex-layout/demo/index.html
new file mode 100644
index 0000000000..2c3f5f7d21
--- /dev/null
+++ b/components/iron-flex-layout/demo/index.html
@@ -0,0 +1,396 @@
+
+
+
+
+
+
+ iron-flex-layout demo
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Horizontal and vertical layout
+
+
+
+
+
one
+
two
+
three
+
+
+
+
+
Flexible children
+
+
+
+
+
+
one
+
two (flex)
+
three
+
+
+
+
+
Flexible children in vertical layouts
+
+
+
+
+
+
one
+
two (flex)
+
three
+
+
+
+
+
Flex ratios
+
+
+
+
+
+
one
+
two
+
three
+
+
+
+
+
Cross-axis stretch alignment (default)
+
+
+
+
+
+
stretch
+
+
+
+
+
Cross-axis center alignment
+
+
+
+
+
+
center
+
+
+
+
+
Cross-axis start alignment
+
+
+
+
+
+
start
+
+
+
+
+
Cross-axis end alignment
+
+
+
+
+
+
end
+
+
+
+
+
Justification, start justified
+
+
+
+
+
+
start-justified
+
+
+
+
+
Justification, start justified
+
+
+
+
+
+
center-justified
+
+
+
+
+
Justification, end justified
+
+
+
+
+
+
end-justified
+
+
+
+
+
Justification, equal space between elements
+
+
+
+
+
+
justified
+
justified
+
justified
+
+
+
+
+
Justification, equal space around each element
+
+
+
+
+
+
around-justified
+
around-justified
+
+
+
+
+
Self alignment
+
+
+
+
+
+
one
+
two
+
three
+
four
+
+
+
+
+
Wrapping
+
+
+
+
+
+
one
+
two
+
three
+
four
+
+
+
+
+
Reversed layouts
+
+
+
+
+
+
one
+
two
+
three
+
four
+
+
+
+
+
General purpose rules
+
+
+
+
+
+
Before [A Span] After
+
Before [A Block Span] After
+
Before invisible span Not displayed After invisible span
+
+
Fit
+
+
+
+
+
+
+
diff --git a/components/iron-flex-layout/index.html b/components/iron-flex-layout/index.html
new file mode 100644
index 0000000000..7d3b0881f8
--- /dev/null
+++ b/components/iron-flex-layout/index.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ iron-flex-layout
+
+
+
+
+
+
+
+
+
+
diff --git a/components/iron-flex-layout/iron-flex-layout-classes.html b/components/iron-flex-layout/iron-flex-layout-classes.html
new file mode 100644
index 0000000000..d382652b71
--- /dev/null
+++ b/components/iron-flex-layout/iron-flex-layout-classes.html
@@ -0,0 +1,431 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/iron-flex-layout/iron-flex-layout.html b/components/iron-flex-layout/iron-flex-layout.html
new file mode 100644
index 0000000000..d98e9d0fdd
--- /dev/null
+++ b/components/iron-flex-layout/iron-flex-layout.html
@@ -0,0 +1,399 @@
+
+
+
+
+
+
+
+
+
diff --git a/components/iron-icon/CONTRIBUTING.md b/components/iron-icon/CONTRIBUTING.md
new file mode 100644
index 0000000000..093090d435
--- /dev/null
+++ b/components/iron-icon/CONTRIBUTING.md
@@ -0,0 +1,77 @@
+
+
+# Polymer Elements
+## Guide for Contributors
+
+Polymer Elements are built in the open, and the Polymer authors eagerly encourage any and all forms of community contribution. When contributing, please follow these guidelines:
+
+### Filing Issues
+
+**If you are filing an issue to request a feature**, please provide a clear description of the feature. It can be helpful to describe answers to the following questions:
+
+ 1. **Who will use the feature?** _“As someone filling out a form…”_
+ 2. **When will they use the feature?** _“When I enter an invalid value…”_
+ 3. **What is the user’s goal?** _“I want to be visually notified that the value needs to be corrected…”_
+
+**If you are filing an issue to report a bug**, please provide:
+
+ 1. **A clear description of the bug and related expectations.** Consider using the following example template for reporting a bug:
+
+ ```markdown
+ The `paper-foo` element causes the page to turn pink when clicked.
+
+ ## Expected outcome
+
+ The page stays the same color.
+
+ ## Actual outcome
+
+ The page turns pink.
+
+ ## Steps to reproduce
+
+ 1. Put a `paper-foo` element in the page.
+ 2. Open the page in a web browser.
+ 3. Click the `paper-foo` element.
+ ```
+
+ 2. **A reduced test case that demonstrates the problem.** If possible, please include the test case as a JSBin. Start with this template to easily import and use relevant Polymer Elements: [https://jsbin.com/cagaye/edit?html,output](https://jsbin.com/cagaye/edit?html,output).
+
+ 3. **A list of browsers where the problem occurs.** This can be skipped if the problem is the same across all browsers.
+
+### Submitting Pull Requests
+
+**Before creating a pull request**, please ensure that an issue exists for the corresponding change in the pull request that you intend to make. **If an issue does not exist, please create one per the guidelines above**. The goal is to discuss the design and necessity of the proposed change with Polymer authors and community before diving into a pull request.
+
+When submitting pull requests, please provide:
+
+ 1. **A reference to the corresponding issue** or issues that will be closed by the pull request. Please refer to these issues in the pull request description using the following syntax:
+
+ ```markdown
+ (For a single issue)
+ Fixes #20
+
+ (For multiple issues)
+ Fixes #32, fixes #40
+ ```
+
+ 2. **A succinct description of the design** used to fix any related issues. For example:
+
+ ```markdown
+ This fixes #20 by removing styles that leaked which would cause the page to turn pink whenever `paper-foo` is clicked.
+ ```
+
+ 3. **At least one test for each bug fixed or feature added** as part of the pull request. Pull requests that fix bugs or add features without accompanying tests will not be considered.
+
+If a proposed change contains multiple commits, please [squash commits](https://www.google.com/url?q=http://blog.steveklabnik.com/posts/2012-11-08-how-to-squash-commits-in-a-github-pull-request) to as few as is necessary to succinctly express the change. A Polymer author can help you squash commits, so don’t be afraid to ask us if you need help with that!
diff --git a/components/iron-icon/README.md b/components/iron-icon/README.md
new file mode 100644
index 0000000000..0649f738ff
--- /dev/null
+++ b/components/iron-icon/README.md
@@ -0,0 +1,22 @@
+[](https://travis-ci.org/PolymerElements/iron-icon)
+
+##<iron-icon>
+
+The `iron-icon` element displays an icon. By default an icon renders as a 24px square.
+
+
+```html
+
+
+```
diff --git a/components/iron-icon/bower.json b/components/iron-icon/bower.json
new file mode 100644
index 0000000000..46239e00e1
--- /dev/null
+++ b/components/iron-icon/bower.json
@@ -0,0 +1,35 @@
+{
+ "name": "iron-icon",
+ "private": true,
+ "version": "1.0.12",
+ "license": "http://polymer.github.io/LICENSE.txt",
+ "description": "An element that supports displaying an icon",
+ "main": "iron-icon.html",
+ "author": [
+ "The Polymer Authors"
+ ],
+ "keywords": [
+ "web-components",
+ "polymer",
+ "icon"
+ ],
+ "repository": {
+ "type": "git",
+ "url": "git://github.com/PolymerElements/iron-icon.git"
+ },
+ "ignore": [],
+ "dependencies": {
+ "iron-flex-layout": "polymerelements/iron-flex-layout#^1.0.0",
+ "iron-meta": "polymerelements/iron-meta#^1.0.0",
+ "polymer": "Polymer/polymer#^1.1.0"
+ },
+ "devDependencies": {
+ "test-fixture": "polymerelements/test-fixture#^1.0.0",
+ "promise-polyfill": "polymerlabs/promise-polyfill#^1.0.0",
+ "iron-iconset": "polymerelements/iron-iconset#^1.0.0",
+ "iron-icons": "polymerelements/iron-icons#^1.0.0",
+ "iron-component-page": "polymerelements/iron-component-page#^1.0.0",
+ "web-component-tester": "^4.0.0",
+ "webcomponentsjs": "webcomponents/webcomponentsjs#^0.7.0"
+ }
+}
diff --git a/components/iron-icon/demo/async.html b/components/iron-icon/demo/async.html
new file mode 100644
index 0000000000..eaf40d1ba2
--- /dev/null
+++ b/components/iron-icon/demo/async.html
@@ -0,0 +1,62 @@
+
+
+
+
+ iron-icon demo
+
+
+
+
+
+
+
+
+
+ This demo is for an <iron-icon> with an asynchronously loaded
+ iconset.
+
This demo is for a single <iron-icon>. If you're looking for the
+ whole set of available icons, check out the <iron-icons> demo.
+
+
+
+
+
+
<iron-icon icon="example:location">
+
+
+
+
<iron-icon src="location.png">
+
+
+
+
+
diff --git a/components/iron-icon/demo/location.png b/components/iron-icon/demo/location.png
new file mode 100644
index 0000000000..9bb74236b8
Binary files /dev/null and b/components/iron-icon/demo/location.png differ
diff --git a/components/iron-icon/hero.svg b/components/iron-icon/hero.svg
new file mode 100755
index 0000000000..19f01c2fdb
--- /dev/null
+++ b/components/iron-icon/hero.svg
@@ -0,0 +1,19 @@
+
+
+
+
diff --git a/components/iron-icon/index.html b/components/iron-icon/index.html
new file mode 100644
index 0000000000..487bb5c38a
--- /dev/null
+++ b/components/iron-icon/index.html
@@ -0,0 +1,26 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/iron-icon/iron-icon.html b/components/iron-icon/iron-icon.html
new file mode 100644
index 0000000000..64ee2ac1fa
--- /dev/null
+++ b/components/iron-icon/iron-icon.html
@@ -0,0 +1,210 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/iron-iconset-svg/CONTRIBUTING.md b/components/iron-iconset-svg/CONTRIBUTING.md
new file mode 100644
index 0000000000..093090d435
--- /dev/null
+++ b/components/iron-iconset-svg/CONTRIBUTING.md
@@ -0,0 +1,77 @@
+
+
+# Polymer Elements
+## Guide for Contributors
+
+Polymer Elements are built in the open, and the Polymer authors eagerly encourage any and all forms of community contribution. When contributing, please follow these guidelines:
+
+### Filing Issues
+
+**If you are filing an issue to request a feature**, please provide a clear description of the feature. It can be helpful to describe answers to the following questions:
+
+ 1. **Who will use the feature?** _“As someone filling out a form…”_
+ 2. **When will they use the feature?** _“When I enter an invalid value…”_
+ 3. **What is the user’s goal?** _“I want to be visually notified that the value needs to be corrected…”_
+
+**If you are filing an issue to report a bug**, please provide:
+
+ 1. **A clear description of the bug and related expectations.** Consider using the following example template for reporting a bug:
+
+ ```markdown
+ The `paper-foo` element causes the page to turn pink when clicked.
+
+ ## Expected outcome
+
+ The page stays the same color.
+
+ ## Actual outcome
+
+ The page turns pink.
+
+ ## Steps to reproduce
+
+ 1. Put a `paper-foo` element in the page.
+ 2. Open the page in a web browser.
+ 3. Click the `paper-foo` element.
+ ```
+
+ 2. **A reduced test case that demonstrates the problem.** If possible, please include the test case as a JSBin. Start with this template to easily import and use relevant Polymer Elements: [https://jsbin.com/cagaye/edit?html,output](https://jsbin.com/cagaye/edit?html,output).
+
+ 3. **A list of browsers where the problem occurs.** This can be skipped if the problem is the same across all browsers.
+
+### Submitting Pull Requests
+
+**Before creating a pull request**, please ensure that an issue exists for the corresponding change in the pull request that you intend to make. **If an issue does not exist, please create one per the guidelines above**. The goal is to discuss the design and necessity of the proposed change with Polymer authors and community before diving into a pull request.
+
+When submitting pull requests, please provide:
+
+ 1. **A reference to the corresponding issue** or issues that will be closed by the pull request. Please refer to these issues in the pull request description using the following syntax:
+
+ ```markdown
+ (For a single issue)
+ Fixes #20
+
+ (For multiple issues)
+ Fixes #32, fixes #40
+ ```
+
+ 2. **A succinct description of the design** used to fix any related issues. For example:
+
+ ```markdown
+ This fixes #20 by removing styles that leaked which would cause the page to turn pink whenever `paper-foo` is clicked.
+ ```
+
+ 3. **At least one test for each bug fixed or feature added** as part of the pull request. Pull requests that fix bugs or add features without accompanying tests will not be considered.
+
+If a proposed change contains multiple commits, please [squash commits](https://www.google.com/url?q=http://blog.steveklabnik.com/posts/2012-11-08-how-to-squash-commits-in-a-github-pull-request) to as few as is necessary to succinctly express the change. A Polymer author can help you squash commits, so don’t be afraid to ask us if you need help with that!
diff --git a/components/iron-iconset-svg/README.md b/components/iron-iconset-svg/README.md
new file mode 100644
index 0000000000..971ab0c718
--- /dev/null
+++ b/components/iron-iconset-svg/README.md
@@ -0,0 +1,56 @@
+
+
+
+[](https://travis-ci.org/PolymerElements/iron-iconset-svg)
+
+_[Demo and API docs](https://elements.polymer-project.org/elements/iron-iconset-svg)_
+
+
+##<iron-iconset-svg>
+
+The `iron-iconset-svg` element allows users to define their own icon sets
+that contain svg icons. The svg icon elements should be children of the
+`iron-iconset-svg` element. Multiple icons should be given distinct id's.
+
+Using svg elements to create icons has a few advantages over traditional
+bitmap graphics like jpg or png. Icons that use svg are vector based so
+they are resolution independent and should look good on any device. They
+are stylable via css. Icons can be themed, colorized, and even animated.
+
+Example:
+
+```html
+
+
+
+```
+
+This will automatically register the icon set "my-svg-icons" to the iconset
+database. To use these icons from within another element, make a
+`iron-iconset` element and call the `byId` method
+to retrieve a given iconset. To apply a particular icon inside an
+element use the `applyIcon` method. For example:
+
+```javascript
+iconset.applyIcon(iconNode, 'car');
+```
+
+
diff --git a/components/iron-iconset-svg/bower.json b/components/iron-iconset-svg/bower.json
new file mode 100644
index 0000000000..fba891cdc0
--- /dev/null
+++ b/components/iron-iconset-svg/bower.json
@@ -0,0 +1,34 @@
+{
+ "name": "iron-iconset-svg",
+ "description": "Manages a set of svg icons",
+ "version": "1.1.0",
+ "keywords": [
+ "web-components",
+ "polymer",
+ "icon"
+ ],
+ "license": "http://polymer.github.io/LICENSE.txt",
+ "private": true,
+ "authors": [
+ "The Polymer Authors"
+ ],
+ "repository": {
+ "type": "git",
+ "url": "git://github.com/PolymerElements/iron-iconset-svg.git"
+ },
+ "dependencies": {
+ "polymer": "polymer/polymer#^1.0.0",
+ "iron-meta": "polymerelements/iron-meta#^1.0.0"
+ },
+ "devDependencies": {
+ "paper-styles": "polymerelements/paper-styles#^1.0.2",
+ "iron-component-page": "polymerelements/iron-component-page#^1.0.0",
+ "iron-icon": "polymerelements/iron-icon#^1.0.0",
+ "promise-polyfill": "polymerlabs/promise-polyfill#^1.0.0",
+ "test-fixture": "polymerelements/test-fixture#^1.0.0",
+ "webcomponentsjs": "webcomponents/webcomponentsjs#^0.7.0",
+ "web-component-tester": "^4.0.0"
+ },
+ "main": "iron-iconset-svg.html",
+ "ignore": []
+}
diff --git a/components/iron-iconset-svg/demo/index.html b/components/iron-iconset-svg/demo/index.html
new file mode 100644
index 0000000000..53b291aa35
--- /dev/null
+++ b/components/iron-iconset-svg/demo/index.html
@@ -0,0 +1,70 @@
+
+
+
+
+
+
+ iron-iconset-svg
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/iron-iconset-svg/demo/svg-sample-icons.html b/components/iron-iconset-svg/demo/svg-sample-icons.html
new file mode 100644
index 0000000000..3eed843f09
--- /dev/null
+++ b/components/iron-iconset-svg/demo/svg-sample-icons.html
@@ -0,0 +1,81 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/iron-iconset-svg/index.html b/components/iron-iconset-svg/index.html
new file mode 100644
index 0000000000..487bb5c38a
--- /dev/null
+++ b/components/iron-iconset-svg/index.html
@@ -0,0 +1,26 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/iron-iconset-svg/iron-iconset-svg.html b/components/iron-iconset-svg/iron-iconset-svg.html
new file mode 100644
index 0000000000..f2a79454c3
--- /dev/null
+++ b/components/iron-iconset-svg/iron-iconset-svg.html
@@ -0,0 +1,241 @@
+
+
+
+
+
+
diff --git a/components/iron-meta/CONTRIBUTING.md b/components/iron-meta/CONTRIBUTING.md
new file mode 100644
index 0000000000..093090d435
--- /dev/null
+++ b/components/iron-meta/CONTRIBUTING.md
@@ -0,0 +1,77 @@
+
+
+# Polymer Elements
+## Guide for Contributors
+
+Polymer Elements are built in the open, and the Polymer authors eagerly encourage any and all forms of community contribution. When contributing, please follow these guidelines:
+
+### Filing Issues
+
+**If you are filing an issue to request a feature**, please provide a clear description of the feature. It can be helpful to describe answers to the following questions:
+
+ 1. **Who will use the feature?** _“As someone filling out a form…”_
+ 2. **When will they use the feature?** _“When I enter an invalid value…”_
+ 3. **What is the user’s goal?** _“I want to be visually notified that the value needs to be corrected…”_
+
+**If you are filing an issue to report a bug**, please provide:
+
+ 1. **A clear description of the bug and related expectations.** Consider using the following example template for reporting a bug:
+
+ ```markdown
+ The `paper-foo` element causes the page to turn pink when clicked.
+
+ ## Expected outcome
+
+ The page stays the same color.
+
+ ## Actual outcome
+
+ The page turns pink.
+
+ ## Steps to reproduce
+
+ 1. Put a `paper-foo` element in the page.
+ 2. Open the page in a web browser.
+ 3. Click the `paper-foo` element.
+ ```
+
+ 2. **A reduced test case that demonstrates the problem.** If possible, please include the test case as a JSBin. Start with this template to easily import and use relevant Polymer Elements: [https://jsbin.com/cagaye/edit?html,output](https://jsbin.com/cagaye/edit?html,output).
+
+ 3. **A list of browsers where the problem occurs.** This can be skipped if the problem is the same across all browsers.
+
+### Submitting Pull Requests
+
+**Before creating a pull request**, please ensure that an issue exists for the corresponding change in the pull request that you intend to make. **If an issue does not exist, please create one per the guidelines above**. The goal is to discuss the design and necessity of the proposed change with Polymer authors and community before diving into a pull request.
+
+When submitting pull requests, please provide:
+
+ 1. **A reference to the corresponding issue** or issues that will be closed by the pull request. Please refer to these issues in the pull request description using the following syntax:
+
+ ```markdown
+ (For a single issue)
+ Fixes #20
+
+ (For multiple issues)
+ Fixes #32, fixes #40
+ ```
+
+ 2. **A succinct description of the design** used to fix any related issues. For example:
+
+ ```markdown
+ This fixes #20 by removing styles that leaked which would cause the page to turn pink whenever `paper-foo` is clicked.
+ ```
+
+ 3. **At least one test for each bug fixed or feature added** as part of the pull request. Pull requests that fix bugs or add features without accompanying tests will not be considered.
+
+If a proposed change contains multiple commits, please [squash commits](https://www.google.com/url?q=http://blog.steveklabnik.com/posts/2012-11-08-how-to-squash-commits-in-a-github-pull-request) to as few as is necessary to succinctly express the change. A Polymer author can help you squash commits, so don’t be afraid to ask us if you need help with that!
diff --git a/components/iron-meta/README.md b/components/iron-meta/README.md
new file mode 100644
index 0000000000..3f2ebb321f
--- /dev/null
+++ b/components/iron-meta/README.md
@@ -0,0 +1,110 @@
+
+
+
+[](https://travis-ci.org/PolymerElements/iron-meta)
+
+_[Demo and API docs](https://elements.polymer-project.org/elements/iron-meta)_
+
+
+##<iron-meta>
+
+`iron-meta` is a generic element you can use for sharing information across the DOM tree.
+It uses [monostate pattern](http://c2.com/cgi/wiki?MonostatePattern) such that any
+instance of iron-meta has access to the shared
+information. You can use `iron-meta` to share whatever you want (or create an extension
+[like x-meta] for enhancements).
+
+The `iron-meta` instances containing your actual data can be loaded in an import,
+or constructed in any way you see fit. The only requirement is that you create them
+before you try to access them.
+
+Examples:
+
+If I create an instance like this:
+
+```html
+
+```
+
+Note that value="foo/bar" is the metadata I've defined. I could define more
+attributes or use child nodes to define additional metadata.
+
+Now I can access that element (and it's metadata) from any iron-meta instance
+via the byKey method, e.g.
+
+```javascript
+meta.byKey('info');
+```
+
+Pure imperative form would be like:
+
+```javascript
+document.createElement('iron-meta').byKey('info');
+```
+
+Or, in a Polymer element, you can include a meta in your template:
+
+```html
+
+...
+this.$.meta.byKey('info');
+```
+
+
+
+##<iron-meta-query>
+
+`iron-meta` is a generic element you can use for sharing information across the DOM tree.
+It uses [monostate pattern](http://c2.com/cgi/wiki?MonostatePattern) such that any
+instance of iron-meta has access to the shared
+information. You can use `iron-meta` to share whatever you want (or create an extension
+[like x-meta] for enhancements).
+
+The `iron-meta` instances containing your actual data can be loaded in an import,
+or constructed in any way you see fit. The only requirement is that you create them
+before you try to access them.
+
+Examples:
+
+If I create an instance like this:
+
+```html
+
+```
+
+Note that value="foo/bar" is the metadata I've defined. I could define more
+attributes or use child nodes to define additional metadata.
+
+Now I can access that element (and it's metadata) from any iron-meta instance
+via the byKey method, e.g.
+
+```javascript
+meta.byKey('info');
+```
+
+Pure imperative form would be like:
+
+```javascript
+document.createElement('iron-meta').byKey('info');
+```
+
+Or, in a Polymer element, you can include a meta in your template:
+
+```html
+
+...
+this.$.meta.byKey('info');
+```
+
+
diff --git a/components/iron-meta/bower.json b/components/iron-meta/bower.json
new file mode 100644
index 0000000000..d457e06e49
--- /dev/null
+++ b/components/iron-meta/bower.json
@@ -0,0 +1,30 @@
+{
+ "name": "iron-meta",
+ "version": "1.1.2",
+ "keywords": [
+ "web-components",
+ "polymer"
+ ],
+ "license": "http://polymer.github.io/LICENSE.txt",
+ "description": "Useful for sharing information across a DOM tree",
+ "private": true,
+ "authors": [
+ "The Polymer Authors"
+ ],
+ "repository": {
+ "type": "git",
+ "url": "git://github.com/PolymerElements/iron-meta.git"
+ },
+ "dependencies": {
+ "polymer": "Polymer/polymer#^1.0.0"
+ },
+ "devDependencies": {
+ "paper-styles": "polymerelements/paper-styles#^1.0.4",
+ "iron-component-page": "polymerelements/iron-component-page#^1.0.0",
+ "test-fixture": "polymerelements/test-fixture#^1.0.0",
+ "web-component-tester": "^4.0.0",
+ "webcomponentsjs": "webcomponents/webcomponentsjs#^0.7.0"
+ },
+ "main": "iron-meta.html",
+ "ignore": []
+}
diff --git a/components/iron-meta/demo/index.html b/components/iron-meta/demo/index.html
new file mode 100644
index 0000000000..0fc39e30ef
--- /dev/null
+++ b/components/iron-meta/demo/index.html
@@ -0,0 +1,76 @@
+
+
+
+
+
+
+
+
+ iron-meta
+
+
+
+
+
+
+
+
+
<iron-meta>
+
Key Query
+
+
+
+ The value stored at key="info" is .
+
+
+
+
Type Query
+
+
+
+
+
+
+ The value(s) stored at type="type1" are: .
Download awips2-cave.dmg (263 MB), click to open and drag to your Applications folder. The application will write to a local data cache directory ~/Library/CAVE.
All package dependencies should be resolved by yum.
+
+
How to run CAVE
-
/awips2/cave/cave.sh
-
+
Find CAVE in the GNOME menu Applications > Internet > AWIPS CAVE
-
-
AWIPS was originally built for 32-bit Red Hat 5 (which is what the old AWIPS I system runs on). As of 2016, 64-bit RHEL and CentOS 6 are supported, and Fedora Linux 9-12 should work as well. Unsupported distros include CentOS 7, Ubuntu, Debian, and pretty much everthing else.
-
+
Or from the command line, simply type cave
AWIPS Data in the Cloud
@@ -131,8 +129,9 @@ chmod 755 ./installCAVE.sh
Troubleshooting
-
~/caveData
-
You can always reset CAVE by manually removing the ~caveData directory (on OS X remove ~/Library/CAVE. Then run /awips2/cave/cave.sh again and you will be prompted to connect to an EDEX server again. Your local files have been removed, but if user and workstation-specific files exist on the EDEX server (meaning you are re-connecting to one you have used before), the remote files will sync again to ~/caveData or ~/Library/CAVE (custom colormaps, bundles, etc.). So even if you delete your local sync, you can retrieve any saved bundles from EDEX just by connecting again and selecting the files from the File > Import menu.
+
Localization Preferences Error
+
+
You can reset CAVE by removing the ~/caveData directory (on OS X ~/Library/CAVE) and then run cave again to connect to an EDEX server. Your local files have been removed, but if you are re-connecting to an EDEX server you have used before, the remote files will sync again to your local ~/caveData (bundles, colormaps, etc.).
No Images Displayed
diff --git a/docs/install/install-edex.html b/docs/install/install-edex.html
index e97d34d090..ecc6aa0067 100644
--- a/docs/install/install-edex.html
+++ b/docs/install/install-edex.html
@@ -6,7 +6,7 @@
-
+
@@ -16,7 +16,7 @@
Unidata AWIPS User Manual
- - EDEX Install and Config
+ - EDEX Data Server Installation
@@ -35,7 +35,7 @@
-
+
@@ -59,7 +59,7 @@
- EDEX Install and Config
+ EDEX Data Server Installation
@@ -71,119 +71,139 @@
- : EDEX Install and Config
+ : EDEX Data Server Installation
16GB RAM (32+GB recommended for full IDD processing)
-
500GB disk space, more if you plan to build a data archive.
-
An SSD mounted to /awips2 contain the entire software system and data files.
-
-
-
-
Notes
-
EDEX can scale to any system by reducing the volume of incoming data and/or turning off certain decoders (for example, with 4 core
-
As of AWIPS 16.2.2, scouring of /awips2/data_store is performed at 30 minutes past every hour, and the default retention rate is
+
64-bit CentOS/RHEL 6 or 7
+
8 CPU cores (16 recommended)
+
16GB RAM (32+GB recommended for full IDD processing)
+
500GB disk space, more if you build a data archive. An SSD is an especially good idea here, mounted to /awips2/edex/data/hdf5 to contain the decoded data files, or mounted to /awips2 to contain the entire AWIPS software system.
-
Linux One-Time Setup
+
EDEX can scale to any system, either by adjusting the incoming data feeds, or the resources allocated to each data type (read more), but when selecting a server, more is always better.
-
Create user and group awips:fxalpha. IP tables will need to be configured to allow specific TCP connections for EDEX: ports 5672, 9581 and 9582.
-
-
-
-
groupadd fxalpha && useradd -G fxalpha awips
-
-
-
mkdir -p /awips2/data_store
-
-
-
vi /etc/sysconfig/iptables
-
-
# Firewall configuration written by system-config-firewall
- # Manual customization of this file is not recommended.
- *filter
- :INPUT ACCEPT [0:0]
- :FORWARD ACCEPT [0:0]
- :OUTPUT ACCEPT [0:0]
- -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
- -A INPUT -p icmp -j ACCEPT
- -A INPUT -i lo -j ACCEPT
- -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
- -A INPUT -m state --state NEW -m tcp -p tcp --dport 5672 -j ACCEPT
- -A INPUT -m state --state NEW -m tcp -p tcp --dport 9581 -j ACCEPT
- -A INPUT -m state --state NEW -m tcp -p tcp --dport 9582 -j ACCEPT
- -A INPUT -j REJECT --reject-with icmp-host-prohibited
- -A FORWARD -j REJECT --reject-with icmp-host-prohibited
- COMMIT
-
-
-
-
service iptables restart
-
-
-
vi /etc/sysconfig/selinux
-
-
# This file controls the state of SELinux on the system.
- # SELINUX= can take one of these three values:
- # enforcing - SELinux security policy is enforced.
- # permissive - SELinux prints warnings instead of enforcing.
- # disabled - No SELinux policy is loaded.
- SELINUX=disabled
- # SELINUXTYPE= can take one of these two values:
- # targeted - Targeted processes are protected,
- # mls - Multi Level Security protection.
- SELINUXTYPE=targeted
-
-
-
-
reboot
-
-
Only required if iptables was updated in step 5.
-
-
-
df -h
-
-
Make sure you have 15GB of storage on / for the /awips2 software, and then ensure you have 500GB (or more) of fast IO file storage (SSD or NFS) available to mount the directories /awips2/edex/data/hdf5 and /awips2/data_store.
64-bit CentOS/RHEL 6 and 7 are the only supported Linux operating systems. You may have luck with Fedora Core 12 to 14 and Scientific Linux. EDEX is not developed, tested, or supported on Debian, Ubuntu, SUSE, Solaris, OS X, or Windows.
-
EDEX Install
+
Linux One-Time Setup (as root)
+
+
1. Create user and group awips:fxalpha
+
+
groupadd fxalpha && useradd -G fxalpha awips
+
+
2. Configure iptables to allow TCP connections on ports 5672, 9581 and 9582
+
+
+
+
To open ports to all connections
+
+
vi /etc/sysconfig/iptables
+
+
*filter
+ :INPUT ACCEPT [0:0]
+ :FORWARD ACCEPT [0:0]
+ :OUTPUT ACCEPT [0:0]
+ -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
+ -A INPUT -p icmp -j ACCEPT
+ -A INPUT -i lo -j ACCEPT
+ -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
+ -A INPUT -m state --state NEW -m tcp -p tcp --dport 5672 -j ACCEPT
+ -A INPUT -m state --state NEW -m tcp -p tcp --dport 9581 -j ACCEPT
+ -A INPUT -m state --state NEW -m tcp -p tcp --dport 9582 -j ACCEPT
+ -A INPUT -j REJECT --reject-with icmp-host-prohibited
+ -A FORWARD -j REJECT --reject-with icmp-host-prohibited
+ COMMIT
+
+
+
+
To open ports to specific IP addresses
+
+
vi /etc/sysconfig/iptables
+
+
*filter
+ :INPUT DROP [0:0]
+ :FORWARD DROP [0:0]
+ :OUTPUT ACCEPT [0:0]
+ :EXTERNAL - [0:0]
+ :EDEX - [0:0]
+
+ -A INPUT -i lo -j ACCEPT
+ -A INPUT -p icmp --icmp-type any -j ACCEPT
+ -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
+ -A INPUT -s 128.117.140.0/24 -j EDEX
+ -A INPUT -s 128.117.156.0/24 -j EDEX
+ -A INPUT -j EXTERNAL
+ -A EXTERNAL -j REJECT
+
+ -A EDEX -m state --state NEW -p tcp --dport 22 -j ACCEPT
+ -A EDEX -m state --state NEW -p tcp --dport 5672 -j ACCEPT
+ -A EDEX -m state --state NEW -p tcp --dport 9581 -j ACCEPT
+ -A EDEX -m state --state NEW -p tcp --dport 9582 -j ACCEPT
+ -A EDEX -j REJECT
+ COMMIT
+
+
+
+
In this example, the IP range 128.117.140.0/24 will match all 128.117.140.* addresses, while 128.117.156.0/24 will match 128.117.156.*.
+
+
+
+
+
3. Restart iptables
+
+
service iptables restart
+
+
4. Disable SELinux
+
+
vi /etc/sysconfig/selinux
+
+
# This file controls the state of SELinux on the system.
+# SELINUX= can take one of these three values:
+# enforcing - SELinux security policy is enforced.
+# permissive - SELinux prints warnings instead of enforcing.
+# disabled - No SELinux policy is loaded.
+SELINUX=disabled
+# SELINUXTYPE= can take one of these two values:
+# targeted - Targeted processes are protected,
+# mls - Multi Level Security protection.
+SELINUXTYPE=targeted
+
/awips2/data_store will contain the last hours’ worth of raw data written by the LDM (~20GB). Scouring of this directory is performed by EDEX to only retain the last hours worth of data (previously with ldmadmin scour the minimum was 24 hours).
+
+
/awips2/edex/data/hdf5 requires 500GB for live data ingest of all IDD feeds. We recommend mounting an SSD here, or to the entire /awips2 filesystem (or both, as shown):
This will install to /awips2/edex, /awips2/data and other directories.
+
What does installEDEX.sh do?
-
64-bit CentOS/RHEL 6 and 7 are the only supported Linux operating systems. You may have luck with Fedora Core 12 to 14 and Scientific Linux. EDEX is not supported on Debian, Ubuntu, SUSE, Solaris, OS X, or Windows.
The command edex setup attempts to add the domain name of your server.
-
/awips2/edex/bin/setup.env should contain the fully-qualified domain name which can be externally resolved (localhost will not work). The command edex setup attempts to add the domain name of your EDEX machine to the file, but you should always confirm this manually.
+
/awips2/edex/bin/setup.envshould contain the fully-qualified domain name, externally resolved, localhost will not work.
/awips2/ldm/etc/ldmd.conf contains the upstream server (default idd.unidata.ucar.edu, which requires you connect form a .edu domain). This file also contains the edexBridge hostname (default localhost).
Qpid is known to crash on systems without a high security limit for user processes and files. The file /etc/security/limits.conf defines the number of each for the awips user (This is automatically configured by the installEDEX.sh script).
/etc/security/limits.conf defines the number of user processes and files (this step is automatically performed by installEDEX.sh). Without these definitions, Qpid is known to crash during periods of high ingest.