Skip to content

Commit c0d7103

Browse files
joern@existsolutions.comjoern@existsolutions.com
[email protected]
authored and
[email protected]
committed
added 'assets' folder to repo;
made proper demo pages; renamed 'elements' folder to 'src' and moved 'demo' into it; new xf-json-data element replaces 'mockup' attribute on xf-form (for better demo display); new xf-key-value-list element to replace pure key/value XML lists; new xf-material-combo element with support for custom values and dynamic lists; added some config files;
1 parent 01baf54 commit c0d7103

File tree

1,654 files changed

+184887
-1022
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

1,654 files changed

+184887
-1022
lines changed

‎assets/.bin/loose-envify

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../loose-envify/cli.js

‎assets/.bin/marked

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../marked/bin/marked

‎assets/@polymer/font-roboto/CONTRIBUTING.md

+77
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
<!--
2+
This file is autogenerated based on
3+
https://github.com/PolymerElements/ContributionGuide/blob/master/CONTRIBUTING.md
4+
5+
If you edit that file, it will get updated everywhere else.
6+
If you edit this file, your changes will get overridden :)
7+
8+
You can however override the jsbin link with one that's customized to this
9+
specific element:
10+
11+
jsbin=https://jsbin.com/cagaye/edit?html,output
12+
-->
13+
14+
# Polymer Elements
15+
## Guide for Contributors
16+
17+
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:
18+
19+
### Filing Issues
20+
21+
**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:
22+
23+
1. **Who will use the feature?** _“As someone filling out a form…”_
24+
2. **When will they use the feature?** _“When I enter an invalid value…”_
25+
3. **What is the user’s goal?** _“I want to be visually notified that the value needs to be corrected…”_
26+
27+
**If you are filing an issue to report a bug**, please provide:
28+
29+
1. **A clear description of the bug and related expectations.** Consider using the following example template for reporting a bug:
30+
31+
```markdown
32+
The `paper-foo` element causes the page to turn pink when clicked.
33+
34+
## Expected outcome
35+
36+
The page stays the same color.
37+
38+
## Actual outcome
39+
40+
The page turns pink.
41+
42+
## Steps to reproduce
43+
44+
1. Put a `paper-foo` element in the page.
45+
2. Open the page in a web browser.
46+
3. Click the `paper-foo` element.
47+
```
48+
49+
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).
50+
51+
3. **A list of browsers where the problem occurs.** This can be skipped if the problem is the same across all browsers.
52+
53+
### Submitting Pull Requests
54+
55+
**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.
56+
57+
When submitting pull requests, please provide:
58+
59+
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:
60+
61+
```markdown
62+
(For a single issue)
63+
Fixes #20
64+
65+
(For multiple issues)
66+
Fixes #32, fixes #40
67+
```
68+
69+
2. **A succinct description of the design** used to fix any related issues. For example:
70+
71+
```markdown
72+
This fixes #20 by removing styles that leaked which would cause the page to turn pink whenever `paper-foo` is clicked.
73+
```
74+
75+
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.
76+
77+
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!

‎assets/@polymer/font-roboto/README.md

+77
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
[![Published on NPM](https://img.shields.io/npm/v/@polymer/font-roboto.svg)](https://www.npmjs.com/package/@polymer/paper-input)
2+
[![Build status](https://travis-ci.org/PolymerElements/font-roboto.svg?branch=master)](https://travis-ci.org/PolymerElements/paper-input)
3+
[![Published on webcomponents.org](https://img.shields.io/badge/webcomponents.org-published-blue.svg)](https://webcomponents.org/element/@polymer/font-roboto)
4+
5+
## font-roboto
6+
`font-roboto` loads the Roboto family of fonts from Google Fonts.
7+
8+
See: [Documentation](https://www.webcomponents.org/element/@polymer/font-roboto).
9+
10+
## Usage
11+
12+
### Installation
13+
```
14+
npm install --save @polymer/font-roboto
15+
```
16+
17+
### In an html file
18+
```html
19+
<html>
20+
<head>
21+
<script type="module">
22+
import '@polymer/font-roboto/roboto.js';
23+
</script>
24+
</head>
25+
<style>
26+
body {
27+
font-family: Roboto;
28+
}
29+
</style>
30+
<body>
31+
<p>This text is in Roboto.</p>
32+
</body>
33+
</html>
34+
```
35+
36+
### In a Polymer 3 element
37+
```js
38+
import {PolymerElement, html} from '@polymer/polymer';
39+
import '@polymer/font-roboto/roboto.js';
40+
41+
class SampleElement extends PolymerElement {
42+
static get template() {
43+
return html`
44+
<style>
45+
p {
46+
font-family: Roboto;
47+
}
48+
</style>
49+
<p>This text is in Roboto.</p>
50+
`;
51+
}
52+
}
53+
customElements.define('sample-element', SampleElement);
54+
```
55+
56+
## Contributing
57+
If you want to send a PR to this element, here are
58+
the instructions for running the tests and demo locally:
59+
60+
### Installation
61+
```sh
62+
git clone https://github.com/PolymerElements/font-roboto
63+
cd font-roboto
64+
npm install
65+
npm install -g polymer-cli
66+
```
67+
68+
### Running the demo locally
69+
```sh
70+
polymer serve --npm
71+
open http://127.0.0.1:<port>/demo/
72+
```
73+
74+
### Running the tests
75+
```sh
76+
polymer test --npm
77+
```

‎assets/@polymer/font-roboto/bower.json

+4
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
{
2+
"name": "font-roboto",
3+
"license": "http://polymer.github.io/LICENSE.txt"
4+
}

‎assets/@polymer/font-roboto/manifest.json

+8
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
{
2+
"files": {
3+
"roboto.html": {
4+
"convertedUrl": "roboto.js",
5+
"exports": {}
6+
}
7+
}
8+
}

‎assets/@polymer/font-roboto/package.json

+62
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
{
2+
"_from": "@polymer/font-roboto@^3.0.0-pre.25",
3+
"_id": "@polymer/[email protected]",
4+
"_inBundle": false,
5+
"_integrity": "sha512-tx5TauYSmzsIvmSqepUPDYbs4/Ejz2XbZ1IkD7JEGqkdNUJlh+9KU85G56Tfdk/xjEZ8zorFfN09OSwiMrIQWA==",
6+
"_location": "/@polymer/font-roboto",
7+
"_phantomChildren": {},
8+
"_requested": {
9+
"type": "range",
10+
"registry": true,
11+
"raw": "@polymer/font-roboto@^3.0.0-pre.25",
12+
"name": "@polymer/font-roboto",
13+
"escapedName": "@polymer%2ffont-roboto",
14+
"scope": "@polymer",
15+
"rawSpec": "^3.0.0-pre.25",
16+
"saveSpec": null,
17+
"fetchSpec": "^3.0.0-pre.25"
18+
},
19+
"_requiredBy": [
20+
"/@polymer/iron-demo-helpers",
21+
"/@polymer/paper-styles"
22+
],
23+
"_resolved": "https://registry.npmjs.org/@polymer/font-roboto/-/font-roboto-3.0.2.tgz",
24+
"_shasum": "80cdaa7225db2359130dfb2c6d9a3be1820020c3",
25+
"_spec": "@polymer/font-roboto@^3.0.0-pre.25",
26+
"_where": "/private/var/folders/p7/bz774dq9345cvlw_pqqxjz3w0000gn/T/asset_stageoLiYj0/node_modules/@polymer/iron-demo-helpers",
27+
"author": {
28+
"name": "The Polymer Authors"
29+
},
30+
"authors": [
31+
"The Polymer Authors"
32+
],
33+
"bugs": {
34+
"url": "https://github.com/PolymerElements/font-roboto/issues"
35+
},
36+
"bundleDependencies": false,
37+
"dependencies": {},
38+
"deprecated": false,
39+
"description": "An HTML import for Roboto",
40+
"devDependencies": {
41+
"@polymer/gen-typescript-declarations": "^1.5.1",
42+
"webmat": "^0.2.2"
43+
},
44+
"homepage": "https://github.com/PolymerElements/font-roboto/",
45+
"keywords": [
46+
"font",
47+
"roboto"
48+
],
49+
"license": "BSD-3-Clause",
50+
"main": "roboto.js",
51+
"name": "@polymer/font-roboto",
52+
"repository": {
53+
"type": "git",
54+
"url": "git://github.com/PolymerElements/font-roboto.git"
55+
},
56+
"scripts": {
57+
"format": "webmat",
58+
"generate-types": "gen-typescript-declarations --deleteExisting --outDir . --verify",
59+
"prepare": "npm run generate-types"
60+
},
61+
"version": "3.0.2"
62+
}

‎assets/@polymer/font-roboto/roboto.d.ts

+12
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
/**
2+
* DO NOT EDIT
3+
*
4+
* This file was automatically generated by
5+
* https://github.com/Polymer/tools/tree/master/packages/gen-typescript-declarations
6+
*
7+
* To modify these typings, edit the source file(s):
8+
* roboto.js
9+
*/
10+
11+
12+
export {};

‎assets/@polymer/font-roboto/roboto.js

+23
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
/// BareSpecifier=@polymer/font-roboto/roboto
2+
/**
3+
@license
4+
Copyright (c) 2015 The Polymer Project Authors. All rights reserved.
5+
This code may only be used under the BSD style license found at
6+
http://polymer.github.io/LICENSE.txt The complete set of authors may be found at
7+
http://polymer.github.io/AUTHORS.txt The complete set of contributors may be
8+
found at http://polymer.github.io/CONTRIBUTORS.txt Code distributed by Google as
9+
part of the polymer project is also subject to an additional IP rights grant
10+
found at http://polymer.github.io/PATENTS.txt
11+
*/
12+
13+
export {}; // ensure this file can only be parsed as a module.
14+
15+
// Give the user the choice to opt out of font loading.
16+
if (!window.polymerSkipLoadingFontRoboto) {
17+
const link = document.createElement('link');
18+
link.rel = 'stylesheet';
19+
link.type = 'text/css';
20+
link.crossOrigin = 'anonymous';
21+
link.href = 'https://fonts.googleapis.com/css?family=Roboto+Mono:400,700|Roboto:400,300,300italic,400italic,500,500italic,700,700italic';
22+
document.head.appendChild(link);
23+
}

‎assets/@polymer/iron-a11y-announcer/CONTRIBUTING.md

+77
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
<!--
2+
This file is autogenerated based on
3+
https://github.com/PolymerElements/ContributionGuide/blob/master/CONTRIBUTING.md
4+
5+
If you edit that file, it will get updated everywhere else.
6+
If you edit this file, your changes will get overridden :)
7+
8+
You can however override the jsbin link with one that's customized to this
9+
specific element:
10+
11+
jsbin=https://jsbin.com/cagaye/edit?html,output
12+
-->
13+
14+
# Polymer Elements
15+
## Guide for Contributors
16+
17+
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:
18+
19+
### Filing Issues
20+
21+
**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:
22+
23+
1. **Who will use the feature?** _“As someone filling out a form…”_
24+
2. **When will they use the feature?** _“When I enter an invalid value…”_
25+
3. **What is the user’s goal?** _“I want to be visually notified that the value needs to be corrected…”_
26+
27+
**If you are filing an issue to report a bug**, please provide:
28+
29+
1. **A clear description of the bug and related expectations.** Consider using the following example template for reporting a bug:
30+
31+
```markdown
32+
The `paper-foo` element causes the page to turn pink when clicked.
33+
34+
## Expected outcome
35+
36+
The page stays the same color.
37+
38+
## Actual outcome
39+
40+
The page turns pink.
41+
42+
## Steps to reproduce
43+
44+
1. Put a `paper-foo` element in the page.
45+
2. Open the page in a web browser.
46+
3. Click the `paper-foo` element.
47+
```
48+
49+
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).
50+
51+
3. **A list of browsers where the problem occurs.** This can be skipped if the problem is the same across all browsers.
52+
53+
### Submitting Pull Requests
54+
55+
**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.
56+
57+
When submitting pull requests, please provide:
58+
59+
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:
60+
61+
```markdown
62+
(For a single issue)
63+
Fixes #20
64+
65+
(For multiple issues)
66+
Fixes #32, fixes #40
67+
```
68+
69+
2. **A succinct description of the design** used to fix any related issues. For example:
70+
71+
```markdown
72+
This fixes #20 by removing styles that leaked which would cause the page to turn pink whenever `paper-foo` is clicked.
73+
```
74+
75+
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.
76+
77+
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!

0 commit comments

Comments
 (0)