initial commit

.angular-cli.json

@@ -0,0 +1,67 @@
+{
+    "project": {
+        "version": "1.0.0-beta.20-4",
+        "name": "clarity-seed"
+    },
+    "apps": [
+        {
+            "root": "src",
+            "outDir": "dist",
+            "assets": [
+                "images",
+                "favicon.ico"
+            ],
+            "index": "index.html",
+            "main": "main.ts",
+            "test": "test.ts",
+            "tsconfig": "tsconfig.json",
+            "prefix": "app",
+            "mobile": false,
+            "styles": [
+                "../node_modules/@clr/icons/clr-icons.min.css",
+                "../node_modules/@clr/ui/clr-ui.min.css",
+                "styles.css"
+            ],
+            "scripts": [
+                "../node_modules/core-js/client/shim.min.js",
+                "../node_modules/mutationobserver-shim/dist/mutationobserver.min.js",
+                "../node_modules/@webcomponents/custom-elements/custom-elements.min.js",
+                "../node_modules/@clr/icons/clr-icons.min.js",
+                "../node_modules/web-animations-js/web-animations.min.js"
+            ],
+            "environmentSource": "environments/environment.ts",
+            "environments": {
+                "dev": "environments/environment.ts",
+                "prod": "environments/environment.prod.ts"
+            }
+        }
+    ],
+    "addons": [],
+    "packages": [],
+    "e2e": {
+        "protractor": {
+            "config": "./protractor.config.js"
+        }
+    },
+    "test": {
+        "karma": {
+            "config": "./karma.conf.js"
+        }
+    },
+    "defaults": {
+        "styleExt": "scss",
+        "prefixInterfaces": false,
+        "inline": {
+            "style": false,
+            "template": false
+        },
+        "spec": {
+            "class": false,
+            "component": true,
+            "directive": true,
+            "module": false,
+            "pipe": true,
+            "service": true
+        }
+    }
+}

.editorconfig

@@ -0,0 +1,20 @@
+# http://editorconfig.org
+root = true
+
+[*]
+charset = utf-8
+indent_style = space
+indent_size = 4
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+
+[*.md]
+max_line_length = 0
+trim_trailing_whitespace = true
+
+# Indentation override
+#[lib/**.js]
+#[{package.json,.travis.yml}]
+#[**/**.js]

.gitignore

@@ -0,0 +1,10 @@
+coverage/
+dist/
+html-report/
+node_modules/
+typings/
+**/*npm-debug.log.*
+**/*yarn-error.log.*
+.idea/
+.DS_Store
+.npmrc

.travis.yml

@@ -0,0 +1,19 @@
+language: node_js
+node_js:
+  - "8.9.3"
+
+sudo: required
+dist: trusty
+group: edge
+
+addons:
+  apt:
+    sources:
+      - ubuntu-toolchain-r-test
+      - google-chrome
+    packages:
+      - g++-4.8
+      - google-chrome-stable
+
+before_install:
+  - export CHROME_BIN=/usr/bin/google-chrome

CODE_OF_CONDUCT.md

@@ -0,0 +1,19 @@
+Contributor Code of Conduct
+======================
+
+As contributors and maintainers of the Clarity project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities.
+
+Communication through any of Clarity's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.
+
+We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to the Clarity project to do the same.
+
+If any member of the community violates this code of conduct, the maintainers of the Clarity project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate.
+
+If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us.
+
+If you have suggestions to improve this Code of Conduct, please submit an issue or PR.
+
+
+**Attribution**
+
+This Code of Conduct is adapted from the Angular project, version 0.3a-angular, available at this page:  https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md

CONTRIBUTING.md

@@ -0,0 +1,113 @@
+
+
+# Contributing to clarity-seed
+
+The clarity-seed project team welcomes contributions from the community. Follow the guidelines to contribute to the seed.
+
+## Contribution Guidelines
+
+Before you start working with Clarity, please complete the following steps:
+
+- Read our [code of conduct](/CODE_OF_CONDUCT.md).
+- Read our [Developer Certificate of Origin](https://cla.vmware.com/dco). All contributions to this repository must be signed as described on that page. Your signature certifies that you wrote the patch or have the right to pass it on as an open-source patch.
+
+## Contribution Flow
+
+Here are the typical steps in a contributor's workflow:
+
+- [Fork](https://help.github.com/articles/fork-a-repo/) the main Clarity seed repository. 
+- Clone your fork and set the upstream remote to the main Clarity repository.
+- Set your name and e-mail in the Git configuration for signing.
+- Create a topic branch from where you want to base your work.
+- Make commits of logical units.
+- Make sure your commit messages are in the proper format (see below).
+- Push your changes to a topic branch in your fork of the repository.
+- [Submit a pull request](https://help.github.com/articles/about-pull-requests/).
+
+Example:
+
+``` shell
+# Clone your forked repository
+git clone [email protected]:<github username>/clarity-seed.git
+
+# Navigate to the directory
+cd clarity-seed
+
+# Set name and e-mail configuration
+git config user.name "John Doe"
+git config user.email [email protected]
+
+# Setup the upstream remote
+git remote add upstream https://github.com/vmware/clarity-seed.git
+
+# Create a topic branch for your changes
+git checkout -b my-new-feature master
+
+# After making the desired changes, commit and push to your fork
+git commit -a -s
+git push origin my-new-feature
+```
+
+### Staying In Sync With Upstream
+
+When your branch gets out of sync with the master branch, use the following to update:
+
+``` shell
+git checkout my-new-feature
+git fetch -a
+git pull --rebase upstream master
+git push --force-with-lease origin my-new-feature
+```
+
+### Updating Pull Requests
+
+If your PR fails to pass CI, or requires changes based on code review, you'll most likely want to squash these changes into existing commits.
+
+If your pull request contains a single commit, or your changes are related to the most recent commit, you can amend the commit.
+
+``` shell
+git add .
+git commit --amend
+git push --force-with-lease origin my-new-feature
+```
+
+If you need to squash changes into an earlier commit, use the following:
+
+``` shell
+git add .
+git commit --fixup <commit>
+git rebase -i --autosquash master
+git push --force-with-lease origin my-new-feature
+```
+
+Make sure you add a comment to the PR indicating that your changes are ready to review. GitHub does not generate a notification when you use git push.
+
+### Formatting Commit Messages
+
+Use this format for your commit message:
+
+```
+<detailed commit message>
+<BLANK LINE>
+<reference to closing an issue>
+<BLANK LINE>
+Signed-off-by: Your Name <[email protected]>
+```
+
+#### Writing Guidelines
+
+These documents provide guidance creating a well-crafted commit message:
+
+ * [How to Write a Git Commit Message](http://chris.beams.io/posts/git-commit/)
+ * [Closing Issues Via Commit Messages](https://help.github.com/articles/closing-issues-via-commit-messages/)
+
+## Reporting Bugs and Creating Issues
+
+You can submit an issue or a bug to our [GitHub repository](https://github.com/vmware/clarity-seed/issues).  You must provide:
+
+* Instruction on how to replicate the issue
+* The version number of Angular
+* The version number of Clarity
+* The version number of Node
+* The browser name and version number
+* The OS running the seed

Clarity Seed_LICENSE_MIT.txt

@@ -0,0 +1,16 @@
+Clarity Seed
+
+Copyright � 2016 VMware, Inc.  All rights reserved				
+
+The MIT license (the �License�) set forth below applies to all parts of the Clarity Seed project.  You may not use this file except in compliance with the License.�
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do
+so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+

Clarity Seed_NOTICE.txt

@@ -0,0 +1,8 @@
+Clarity Seed
+
+Copyright (c) 2016 VMware, Inc. All Rights Reserved. 
+
+This product is licensed to you under the MIT license (the "MIT License").  You may not use this product except in compliance with the MIT License.  
+
+This product may include a number of subcomponents with separate copyright notices and license terms. Your use of these subcomponents is subject to the terms and conditions of the subcomponent's license, as noted in the LICENSE file. 
+