Test persistence with multiple namespaces

Co-authored-by: Joe Pea <joe.pea@nasa.gov>

.circleci/config.yml

@@ -0,0 +1,190 @@
+version: 2.1
+executors:
+  pw-focal-development:
+    docker:
+      - image: mcr.microsoft.com/playwright:v1.17.2-focal
+    environment:
+      NODE_ENV: development # Needed to ensure 'dist' folder created and devDependencies installed
+parameters:
+  BUST_CACHE:
+    description: "Set this with the CircleCI UI Trigger Workflow button (boolean = true) to bust the cache!"
+    default: false
+    type: boolean
+commands:
+  build_and_install:
+    description: "All steps used to build and install. Will not work on node10"
+    parameters:
+      node-version:
+        type: string
+    steps:
+      - checkout
+      - restore_cache_cmd:
+          node-version: << parameters.node-version >>
+      - node/install:
+          install-npm: true
+          node-version: << parameters.node-version >>
+      - run: npm install
+  restore_cache_cmd:
+    description: "Custom command for restoring cache with the ability to bust cache. When BUST_CACHE is set to true, jobs will not restore cache"
+    parameters:
+      node-version:
+        type: string
+    steps:
+      - when:
+          condition: 
+            equal: [false, << pipeline.parameters.BUST_CACHE >> ]
+          steps:
+            - restore_cache:
+                key: deps-{{ .Branch }}--<< parameters.node-version >>--{{ checksum "package.json" }}-{{ checksum ".circleci/config.yml" }}
+  save_cache_cmd:
+    description: "Custom command for saving cache."
+    parameters:
+      node-version:
+        type: string
+    steps:    
+      - save_cache:
+          key: deps-{{ .Branch }}--<< parameters.node-version >>--{{ checksum "package.json" }}-{{ checksum ".circleci/config.yml" }}
+          paths:
+            - ~/.npm
+            - node_modules
+  generate_and_store_version_and_filesystem_artifacts:
+    description: "Track important packages and files"
+    steps:
+      - run: |
+          mkdir /tmp/artifacts
+          printenv NODE_ENV >> /tmp/artifacts/NODE_ENV.txt
+          npm -v >> /tmp/artifacts/npm-version.txt
+          node -v >> /tmp/artifacts/node-version.txt
+          ls -latR >> /tmp/artifacts/dir.txt
+      - store_artifacts:
+          path: /tmp/artifacts/
+  upload_code_covio:
+    description: "Command to upload code coverage reports to codecov.io"
+    steps:
+        - run: curl -Os https://uploader.codecov.io/latest/linux/codecov;chmod +x codecov;./codecov 
+orbs:
+  node: circleci/node@4.9.0
+  browser-tools: circleci/browser-tools@1.2.3
+jobs:
+  npm-audit:
+    parameters:
+      node-version:
+        type: string
+    executor: pw-focal-development
+    steps:
+      - build_and_install:
+          node-version: <<parameters.node-version>>
+      - run: npm audit --audit-level=low
+      - generate_and_store_version_and_filesystem_artifacts
+  node14-lint:
+    parameters:
+      node-version:
+        type: string
+    executor: pw-focal-development
+    steps:
+      - build_and_install:
+          node-version: <<parameters.node-version>>
+      - run: npm run lint
+      - generate_and_store_version_and_filesystem_artifacts
+  unit-test:
+    parameters:
+      node-version:
+        type: string
+      browser:
+        type: string
+    executor: pw-focal-development
+    steps:
+      - build_and_install:
+          node-version: <<parameters.node-version>>
+      - when:
+          condition:
+            equal: [ "FirefoxESR", <<parameters.browser>> ]
+          steps:
+            - browser-tools/install-firefox:
+                version: "91.4.0esr" #https://archive.mozilla.org/pub/firefox/releases/          
+      - when:
+          condition:
+            equal: [ "FirefoxHeadless", <<parameters.browser>> ]
+          steps:
+            - browser-tools/install-firefox
+      - when:
+          condition:
+            equal: [ "ChromeHeadless", <<parameters.browser>> ]
+          steps:
+            - browser-tools/install-chrome:
+                replace-existing: false
+      - run: npm run test:coverage -- --browsers=<<parameters.browser>>
+      - save_cache_cmd:
+          node-version: <<parameters.node-version>>
+      - store_test_results:
+          path: dist/reports/tests/
+      - store_artifacts:
+          path: dist/reports/
+      - generate_and_store_version_and_filesystem_artifacts
+  e2e-test:
+    parameters:
+      node-version:
+        type: string
+      suite:
+        type: string
+    executor: pw-focal-development
+    steps:
+      - build_and_install:
+          node-version: <<parameters.node-version>>
+      - run: npx playwright install
+      - run: npm run test:e2e:<<parameters.suite>>
+      - store_test_results:
+          path: test-results/results.xml
+      - store_artifacts:
+          path: test-results
+      - generate_and_store_version_and_filesystem_artifacts
+workflows:
+  overall-circleci-commit-status: #These jobs run on every commit
+    jobs:
+      - node14-lint:
+          node-version: lts/fermium
+      - unit-test:
+          name: node12-chrome
+          node-version: lts/erbium
+          browser: ChromeHeadless
+      - unit-test: 
+          name: node14-chrome
+          node-version: lts/fermium
+          browser: ChromeHeadless
+          post-steps:
+            - upload_code_covio               
+      - e2e-test:
+          name: e2e-ci
+          node-version: lts/fermium
+          suite: ci
+  the-nightly: #These jobs do not run on PRs, but against master at night
+    jobs:
+      - unit-test:
+          name: node12-firefoxESR-nightly
+          node-version: lts/erbium
+          browser: FirefoxESR
+      - unit-test:
+          name: node12-chrome-nightly
+          node-version: lts/erbium
+          browser: ChromeHeadless
+      - unit-test:
+          name: node14-firefox-nightly
+          node-version: lts/fermium
+          browser: FirefoxHeadless
+      - unit-test:
+          name: node14-chrome-nightly
+          node-version: lts/fermium
+          browser: ChromeHeadless
+      - npm-audit:
+          node-version: lts/fermium
+      - e2e-test:
+          name: e2e-full-nightly
+          node-version: lts/fermium
+          suite: full
+    triggers:
+      - schedule:
+          cron: "0 0 * * *"
+          filters:
+            branches:
+              only:
+                - master

.eslintrc.js

@@ -0,0 +1,270 @@
+const LEGACY_FILES = ["platform/**", "example/**"];
+module.exports = {
+    "env": {
+        "browser": true,
+        "es6": true,
+        "jasmine": true,
+        "amd": true
+    },
+    "globals": {
+        "_": "readonly"
+    },
+    "extends": [
+        "eslint:recommended",
+        "plugin:vue/recommended",
+        "plugin:you-dont-need-lodash-underscore/compatible"
+    ],
+    "parser": "vue-eslint-parser",
+    "parserOptions": {
+        "parser": "babel-eslint",
+        "allowImportExportEverywhere": true,
+        "ecmaVersion": 2015,
+        "ecmaFeatures": {
+            "impliedStrict": true
+        }
+    },
+    "rules": {
+        "you-dont-need-lodash-underscore/omit": "off",
+        "you-dont-need-lodash-underscore/throttle": "off",
+        "you-dont-need-lodash-underscore/flatten": "off",
+        "no-bitwise": "error",
+        "curly": "error",
+        "eqeqeq": "error",
+        "guard-for-in": "error",
+        "no-extend-native": "error",
+        "no-inner-declarations": "off",
+        "no-use-before-define": ["error", "nofunc"],
+        "no-caller": "error",
+        "no-sequences": "error",
+        "no-irregular-whitespace": "error",
+        "no-new": "error",
+        "no-shadow": "error",
+        "no-undef": "error",
+        "no-unused-vars": [
+            "error",
+            {
+                "vars": "all",
+                "args": "none"
+            }
+        ],
+        "no-console": "off",
+        "no-trailing-spaces": "error",
+        "space-before-function-paren": [
+            "error",
+            {
+                "anonymous": "always",
+                "asyncArrow": "always",
+                "named": "never"
+            }
+        ],
+        "array-bracket-spacing": "error",
+        "space-in-parens": "error",
+        "space-before-blocks": "error",
+        "comma-dangle": "error",
+        "eol-last": "error",
+        "new-cap": [
+            "error",
+            {
+                "capIsNew": false,
+                "properties": false
+            }
+        ],
+        "dot-notation": "error",
+        "indent": ["error", 4],
+
+        // https://eslint.org/docs/rules/no-case-declarations
+        "no-case-declarations": "error",
+        // https://eslint.org/docs/rules/max-classes-per-file
+        "max-classes-per-file": ["error", 1],
+        // https://eslint.org/docs/rules/no-eq-null
+        "no-eq-null": "error",
+        // https://eslint.org/docs/rules/no-eval
+        "no-eval": "error",
+        // https://eslint.org/docs/rules/no-floating-decimal
+        "no-floating-decimal": "error",
+        // https://eslint.org/docs/rules/no-implicit-globals
+        "no-implicit-globals": "error",
+        // https://eslint.org/docs/rules/no-implied-eval
+        "no-implied-eval": "error",
+        // https://eslint.org/docs/rules/no-lone-blocks
+        "no-lone-blocks": "error",
+        // https://eslint.org/docs/rules/no-loop-func
+        "no-loop-func": "error",
+        // https://eslint.org/docs/rules/no-new-func
+        "no-new-func": "error",
+        // https://eslint.org/docs/rules/no-new-wrappers
+        "no-new-wrappers": "error",
+        // https://eslint.org/docs/rules/no-octal-escape
+        "no-octal-escape": "error",
+        // https://eslint.org/docs/rules/no-proto
+        "no-proto": "error",
+        // https://eslint.org/docs/rules/no-return-await
+        "no-return-await": "error",
+        // https://eslint.org/docs/rules/no-script-url
+        "no-script-url": "error",
+        // https://eslint.org/docs/rules/no-self-compare
+        "no-self-compare": "error",
+        // https://eslint.org/docs/rules/no-sequences
+        "no-sequences": "error",
+        // https://eslint.org/docs/rules/no-unmodified-loop-condition
+        "no-unmodified-loop-condition": "error",
+        // https://eslint.org/docs/rules/no-useless-call
+        "no-useless-call": "error",
+        // https://eslint.org/docs/rules/wrap-iife
+        "wrap-iife": "error",
+        // https://eslint.org/docs/rules/no-nested-ternary
+        "no-nested-ternary": "error",
+        // https://eslint.org/docs/rules/switch-colon-spacing
+        "switch-colon-spacing": "error",
+        // https://eslint.org/docs/rules/no-useless-computed-key
+        "no-useless-computed-key": "error",
+        // https://eslint.org/docs/rules/rest-spread-spacing
+        "rest-spread-spacing": ["error"],
+        // https://eslint.org/docs/rules/no-var
+        "no-var": "error",
+        // https://eslint.org/docs/rules/one-var
+        "one-var": ["error", "never"],
+        // https://eslint.org/docs/rules/default-case-last
+        "default-case-last": "error",
+        // https://eslint.org/docs/rules/default-param-last
+        "default-param-last": "error",
+        // https://eslint.org/docs/rules/grouped-accessor-pairs
+        "grouped-accessor-pairs": "error",
+        // https://eslint.org/docs/rules/no-constructor-return
+        "no-constructor-return": "error",
+        // https://eslint.org/docs/rules/array-callback-return
+        "array-callback-return": "error",
+        // https://eslint.org/docs/rules/no-invalid-this
+        "no-invalid-this": "error", // Believe this one actually surfaces some bugs
+        // https://eslint.org/docs/rules/func-style
+        "func-style": ["error", "declaration"],
+        // https://eslint.org/docs/rules/no-unused-expressions
+        "no-unused-expressions": "error",
+        // https://eslint.org/docs/rules/no-useless-concat
+        "no-useless-concat": "error",
+        // https://eslint.org/docs/rules/radix
+        "radix": "error",
+        // https://eslint.org/docs/rules/require-await
+        "require-await": "error",
+        // https://eslint.org/docs/rules/no-alert
+        "no-alert": "error",
+        // https://eslint.org/docs/rules/no-useless-constructor
+        "no-useless-constructor": "error",
+        // https://eslint.org/docs/rules/no-duplicate-imports
+        "no-duplicate-imports": "error",
+
+        // https://eslint.org/docs/rules/no-implicit-coercion
+        "no-implicit-coercion": "error",
+        //https://eslint.org/docs/rules/no-unneeded-ternary
+        "no-unneeded-ternary": "error",
+        // https://eslint.org/docs/rules/semi
+        "semi": ["error", "always"],
+        // https://eslint.org/docs/rules/no-multi-spaces
+        "no-multi-spaces": "error",
+        // https://eslint.org/docs/rules/key-spacing
+        "key-spacing": ["error", {
+            "afterColon": true
+        }],
+        // https://eslint.org/docs/rules/keyword-spacing
+        "keyword-spacing": ["error", {
+            "before": true,
+            "after": true
+        }],
+        // https://eslint.org/docs/rules/comma-spacing
+        // Also requires one line code fix
+        "comma-spacing": ["error", {
+            "after": true
+        }],
+        //https://eslint.org/docs/rules/no-whitespace-before-property
+        "no-whitespace-before-property": "error",
+        // https://eslint.org/docs/rules/object-curly-newline
+        "object-curly-newline": ["error", {
+            "consistent": true,
+            "multiline": true
+        }],
+        // https://eslint.org/docs/rules/object-property-newline
+        "object-property-newline": "error",
+        // https://eslint.org/docs/rules/brace-style
+        "brace-style": "error",
+        // https://eslint.org/docs/rules/no-multiple-empty-lines
+        "no-multiple-empty-lines": ["error", {"max": 1}],
+        // https://eslint.org/docs/rules/operator-linebreak
+        "operator-linebreak": ["error", "before", {"overrides": {"=": "after"}}],
+        // https://eslint.org/docs/rules/padding-line-between-statements
+        "padding-line-between-statements": ["error", {
+            "blankLine": "always",
+            "prev": "multiline-block-like",
+            "next": "*"
+        }, {
+            "blankLine": "always",
+            "prev": "*",
+            "next": "return"
+        }],
+        // https://eslint.org/docs/rules/space-infix-ops
+        "space-infix-ops": "error",
+        // https://eslint.org/docs/rules/space-unary-ops
+        "space-unary-ops": ["error", {
+            "words": true,
+            "nonwords": false
+        }],
+        // https://eslint.org/docs/rules/arrow-spacing
+        "arrow-spacing": "error",
+        // https://eslint.org/docs/rules/semi-spacing
+        "semi-spacing": ["error", {
+            "before": false,
+            "after": true
+        }],
+
+        "vue/html-indent": [
+            "error",
+            4,
+            {
+                "attribute": 1,
+                "baseIndent": 0,
+                "closeBracket": 0,
+                "alignAttributesVertically": true,
+                "ignores": []
+            }
+        ],
+        "vue/html-self-closing": ["error",
+            {
+                "html": {
+                    "void": "never",
+                    "normal": "never",
+                    "component": "always"
+                },
+                "svg": "always",
+                "math": "always"
+            }
+        ],
+        "vue/max-attributes-per-line": ["error", {
+            "singleline": 1,
+            "multiline": {
+                "max": 1,
+                "allowFirstLine": true
+            }
+        }],
+        "vue/multiline-html-element-content-newline": "off",
+        "vue/singleline-html-element-content-newline": "off",
+        "vue/no-mutating-props": "off"
+
+    },
+    "overrides": [
+        {
+            "files": LEGACY_FILES,
+            "rules": {
+                "no-unused-vars": [
+                    "warn",
+                    {
+                        "vars": "all",
+                        "args": "none",
+                        "varsIgnorePattern": "controller"
+                    }
+                ],
+                "no-nested-ternary": "off",
+                "no-var": "off",
+                "one-var": "off"
+            }
+        }
+    ]
+};

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,44 @@
+---
+name: Bug report
+about: File a Bug !
+title: ''
+labels: type:bug
+assignees: ''
+
+---
+
+<!--- Focus on user impact in the title. Use the Summary Field to -->
+<!--- describe the problem technically. -->
+
+#### Summary
+<!--- A description of the issue encountered. When possible, a description -->
+<!--- of the impact of the issue. What use case does it impede?-->
+
+#### Expected vs Current Behavior
+<!--- Tell us what should have happened -->
+
+#### Impact Check List
+<!--- Please select from the following options -->
+
+- [ ] Data loss or misrepresented data?
+- [ ] Regression? Did this used to work or has it always been broken?
+- [ ] Is there a workaround available?
+- [ ] Does this impact a critical component?
+- [ ] Is this just a visual bug with no functional impact?
+
+#### Steps to Reproduce
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+<!--- reproduce this bug. Include code to reproduce, if relevant -->
+1.
+2.
+3.
+4.
+
+#### Environment
+* Open MCT Version: <!--- date of build, version, or SHA -->
+* Deployment Type: <!--- npm dev? VIPER Dev? openmct-yamcs? -->
+* OS:
+* Browser:
+
+#### Additional Information
+<!--- Include any screenshots, gifs, or logs which will expedite triage -->

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Discussions
+    url: https://github.com/nasa/openmct/discussions
+    about: Have a question about the project?

.github/ISSUE_TEMPLATE/enhancement-request.md

@@ -0,0 +1,20 @@
+---
+name: Enhancement request
+about: Suggest an enhancement or new improvement for this project
+title: ''
+labels: type:enhancement
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/maintenance-type.md

@@ -0,0 +1,11 @@
+---
+name: Maintenance
+about: Add, update or remove documentation, tests, or dependencies.
+title: ''
+labels: type:maintenance
+assignees: ''
+
+---
+
+#### Summary
+<!--- Generally describe the purpose of the change. -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,13 @@
+### All Submissions:
+
+* [ ] Have you followed the guidelines in our [Contributing document](https://github.com/nasa/openmct/blob/master/CONTRIBUTING.md)?
+* [ ] Have you checked to ensure there aren't other open [Pull Requests](https://github.com/nasa/openmct/pulls) for the same update/change?
+* [ ] Is this change backwards compatible? For example, developers won't need to change how they are calling the API or how they've extended core plugins such as Tables or Plots.
+
+### Author Checklist
+
+* [ ] Changes address original issue?
+* [ ] Unit tests included and/or updated with changes?
+* [ ] Command line build passes?
+* [ ] Has this been smoke tested?
+* [ ] Testing instructions included in associated issue?

.github/dependabot.yml

@@ -0,0 +1,27 @@
+
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "daily"  
+    open-pull-requests-limit: 4
+    labels:
+      - "type:maintenance"
+      - "dependencies"
+      - "pr:e2e"
+    allow:
+      - dependency-name: "*eslint*"
+      - dependency-name: "*karma*"
+      - dependency-name: "*jasmine*"
+      - dependency-name: "*playwright*"
+      - dependency-name: "*percy*"
+      - dependency-name: "*vue-loader*"
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "daily"    
+    labels:
+      - "type:maintenance"
+      - "dependencies"

.github/workflows/codeql-analysis.yml

@@ -0,0 +1,43 @@
+
+name: "CodeQL"
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+    paths-ignore:
+      - '**/*Spec.js'
+      - '**/*.md'
+      - '**/*.txt'
+      - '**/*.yml'
+      - '**/*.yaml'
+      - '**/*.spec.js'
+      - '**/*.config.js'
+  schedule:
+    - cron: '28 21 * * 3'
+
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: ubuntu-latest
+    permissions:
+      actions: read
+      contents: read
+      security-events: write
+
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v2
+
+    # Initializes the CodeQL tools for scanning.
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v1
+      with:
+        languages: javascript
+
+    - name: Autobuild
+      uses: github/codeql-action/autobuild@v1
+
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v1

.github/workflows/e2e-pr.yml

@@ -0,0 +1,53 @@
+name: "e2e-pr"
+on:
+  workflow_dispatch:
+  pull_request:
+    types: [ labeled ]
+
+jobs:
+  e2e-full:
+    if: ${{ github.event.label.name == 'pr:e2e' }}
+    runs-on: ubuntu-latest
+    steps:
+      - name: Trigger Success
+        uses: actions/github-script@v5
+        with:
+          script: |
+            github.rest.issues.createComment({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              body: 'Started e2e Run. Follow along: https://github.com/nasa/openmct/actions/runs/' + context.runId
+            })
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '14'
+      - run: npm install
+      - run: npm run test:e2e:full
+      - name: Archive test results
+        uses: actions/upload-artifact@v2
+        with:
+          path: test-results
+      - name: Test success
+        if: ${{ success() }}
+        uses: actions/github-script@v5
+        with:
+          script: |
+            github.rest.issues.createComment({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              body: 'Success ✅ ! Build artifacts are here: https://github.com/nasa/openmct/actions/runs/' + context.runId
+            })
+      - name: Test failure
+        if: ${{ failure() }}
+        uses: actions/github-script@v5
+        with:
+          script: |
+            github.rest.issues.createComment({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              body: 'Failure ❌ ! Build artifacts are here: https://github.com/nasa/openmct/actions/runs/' + context.runId
+            })

.github/workflows/e2e-visual.yml

@@ -0,0 +1,23 @@
+name: "e2e-visual"
+on:
+  workflow_dispatch:
+  pull_request:
+    types: 
+      - labeled
+  schedule:
+    - cron: '28 21 * * 1-5'
+
+jobs:
+  e2e-visual:
+    if: ${{ github.event.label.name == 'pr:visual' }} || ${{ github.event.workflow_dispatch }} || ${{ github.event.schedule }}
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '14'
+      - run: npm install
+      - name: Run the e2e visual tests
+        run: npm run test:e2e:visual
+        env:
+          PERCY_TOKEN: ${{ secrets.PERCY_TOKEN }}

.github/workflows/e2e.yml

@@ -0,0 +1,21 @@
+name: "e2e"
+on:
+  workflow_dispatch:
+    inputs: 
+      version:
+        description: 'Which branch do you want to test?' # Limited to branch for now
+        required: false
+        default: 'master' 
+jobs:
+  e2e:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+        with:
+          ref: ${{ github.event.inputs.version }}
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '14'
+      - run: npm install
+      - name: Run the e2e tests
+        run: npm run test:e2e:ci

.github/workflows/lighthouse.yml

@@ -0,0 +1,20 @@
+name: lighthouse
+on:
+  workflow_dispatch:
+    inputs: 
+      version:
+        description: 'Which branch do you want to test?' # Limited to branch for now
+        required: false
+        default: 'master' 
+jobs:
+  lighthouse:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+        with:
+          ref: ${{ github.event.inputs.version }}
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '14'
+      - run: npm install && npm install -g @lhci/cli #Don't want to include this in our deps
+      - run: lhci autorun

.github/workflows/npm-prerelease.yml

@@ -0,0 +1,33 @@
+# This workflow will run tests using node and then publish a package to npmjs when a prerelease is created
+# For more information see: https://help.github.com/actions/language-and-framework-guides/publishing-nodejs-packages
+
+name: npm_prerelease
+
+on:
+  release:
+    types: [prereleased]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
+        with:
+          node-version: 14
+      - run: npm install
+      - run: npm test
+
+  publish-npm-prerelease:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
+        with:
+          node-version: 14
+          registry-url: https://registry.npmjs.org/
+      - run: npm install
+      - run: npm publish --access public --tag unstable
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

.gitignore

@@ -3,6 +3,7 @@
 *.gzip
 *.tgz
 *.DS_Store
+*.swp
 
 # Compiled CSS, unless directly added
 *.sass-cache
@@ -35,3 +36,18 @@ protractor/logs
 
 # npm-debug log
 npm-debug.log
+
+# karma reports
+report.*.json
+
+# Lighthouse reports
+.lighthouseci
+
+# e2e test artifacts
+test-results
+allure-results
+
+package-lock.json
+
+#codecov artifacts
+codecov

.jscsrc

@@ -1,3 +0,0 @@
-{
-    "preset": "crockford"
-}

.jshintrc

@@ -1,4 +0,0 @@
-{
-    "validthis": true,
-    "laxbreak": true
-}

.npmignore

@@ -33,3 +33,12 @@ protractor/logs
 
 # npm-debug log
 npm-debug.log
+
+# Infra and tests
+.circleci
+.github
+e2e
+codecov.yml
+lighthouserc.yml
+*.Spec.js
+karma.conf.js

.npmrc

@@ -0,0 +1,6 @@
+loglevel=warn
+
+# Temporary: istanbul-instrumenter-loader is working with webpack 5, but states
+# webpack 4 being the latest version it supports, so this legacy-peer-deps
+# allows us to install it anyway.
+legacy-peer-deps=true

CONTRIBUTING.md

@@ -1,6 +1,6 @@
-# Contributing to Open MCT Web
+# Contributing to Open MCT
 
-This document describes the process of contributing to Open MCT Web as well
+This document describes the process of contributing to Open MCT as well
 as the standards that will be applied when evaluating contributions.
 
 Please be aware that additional agreements will be necessary before we can
@@ -10,7 +10,7 @@ accept changes from external contributors.
 
 The short version:
 
-1. Write your contribution.
+1. Write your contribution or describe your idea in the form of an [GitHub issue](https://github.com/nasa/openmct/issues/new/choose) or [Starting a GitHub Discussion](https://github.com/nasa/openmct/discussions)
 2. Make sure your contribution meets code, test, and commit message
    standards as described below.
 3. Submit a pull request from a topic branch back to `master`. Include a check
@@ -18,12 +18,13 @@ The short version:
    for review.)
 4. Respond to any discussion. When the reviewer decides it's ready, they
    will merge back `master` and fill out their own check list.
+5. If you are a first-time contributor, please see [this discussion](https://github.com/nasa/openmct/discussions/3821) for further information.   
 
 ## Contribution Process
 
-Open MCT Web uses git for software version control, and for branching and
+Open MCT uses git for software version control, and for branching and
 merging. The central repository is at
-https://github.com/nasa/openmctweb.git.
+https://github.com/nasa/openmct.git.
 
 ### Roles
 
@@ -43,9 +44,9 @@ the check-in process. These roles are:
 
 Three basic types of branches may be included in the above repository:
 
-1. Master branch.
+1. Master branch
-2. Topic branches.
+2. Topic branches
-3. Developer branches.
+3. Developer branches
 
 Branches which do not fit into the above categories may be created and used
 during the course of development for various reasons, such as large-scale
@@ -103,116 +104,132 @@ the name chosen could not be mistaken for a topic or master branch.
 ### Merging
 
 When development is complete on an issue, the first step toward merging it
-back into the master branch is to file a Pull Request. The contributions
+back into the master branch is to file a Pull Request (PR). The contributions
 should meet code, test, and commit message standards as described below,
 and the pull request should include a completed author checklist, also
 as described below. Pull requests may be assigned to specific team
-members when appropriate (e.g. to draw to a specific person's attention.)
+members when appropriate (e.g. to draw to a specific person's attention).
 
 Code review should take place using discussion features within the pull
 request. When the reviewer is satisfied, they should add a comment to
 the pull request containing the reviewer checklist (from below) and complete
 the merge back to the master branch.
 
+Additionally:
+* Every pull request must link to the issue that it addresses. Eg. “Addresses #1234” or “Closes #1234”. This is the responsibility of the pull request’s __author__. If no issue exists, [create one](https://github.com/nasa/openmct/issues/new/choose).
+* Every __author__ must include testing instructions. These instructions should identify the areas of code affected, and some minimal test steps. If addressing a bug, reproduction steps should be included, if they were not included in the original issue. If reproduction steps were included on the original issue, and are sufficient, refer to them.
+* A pull request that closes an issue should say so in the description. Including the text “Closes #1234” will cause the linked issue to be automatically closed when the pull request is merged. This is the responsibility of the pull request’s __author__.
+* When a pull request is merged, and the corresponding issue closed, the __reviewer__ must add the tag “unverified” to the original issue. This will indicate that although the issue is closed, it has not been tested yet.
+* Every PR must have two reviewers assigned, though only one approval is necessary for merge.
+* Changes to API require approval by a senior developer.
+* When creating a PR, it is the author's responsibility to apply any priority label from the issue to the PR as well. This helps with prioritization.
+
 ## Standards
 
-Contributions to Open MCT Web are expected to meet the following standards.
+Contributions to Open MCT are expected to meet the following standards.
 In addition, reviewers should use general discretion before accepting
 changes.
 
 ### Code Standards
 
-JavaScript sources in Open MCT Web must satisfy JSLint under its default
+JavaScript sources in Open MCT must satisfy the ESLint rules defined in 
-settings. This is verified by the command line build.
+this repository. This is verified by the command line build.
 
 #### Code Guidelines
 
-JavaScript sources in Open MCT Web should:
+The following guidelines are provided for anyone contributing source code to the Open MCT project:
 
-* Use four spaces for indentation. Tabs should not be used.
+1. Write clean code. Here’s a good summary - https://github.com/ryanmcdermott/clean-code-javascript.
-* Include JSDoc for any exposed API (e.g. public methods, constructors.)
+1. Include JSDoc for any exposed API (e.g. public methods, classes).
-* Include non-JSDoc comments as-needed for explaining private variables,
+1. Include non-JSDoc comments as-needed for explaining private variables,
-  methods, or algorithms when they are non-obvious.
+   methods, or algorithms when they are non-obvious. Otherwise code 
-* Define one public class per script, expressed as a constructor function
+   should be self-documenting.
-  returned from an AMD-style module.
+1. Classes and Vue components should use camel case, first letter capitalized
-* Follow “Java-like” naming conventions. These includes:
+   (e.g. SomeClassName).
-  * Classes should use camel case, first letter capitalized
+1. Methods, variables, fields, events, and function names should use camelCase,
-    (e.g. SomeClassName.)
+   first letter lower-case (e.g. someVariableName).
-  * Methods, variables, fields, and function names should use camel case,
+1. Source files that export functions should use camelCase, first letter lower-case (eg. testTools.js)
-    first letter lower-case (e.g. someVariableName.) Constants
+1. Constants (variables or fields which are meant to be declared and 
-    (variables or fields which are meant to be declared and initialized
+   initialized statically, and never changed) should use only capital 
-    statically, and never changed) should use only capital letters, with
+   letters, with underscores between words (e.g. SOME_CONSTANT). They should always be declared as `const`s
-    underscores between words (e.g. SOME_CONSTANT.)
+1. File names should be the name of the exported class, plus a .js extension
-  * File name should be the name of the exported class, plus a .js extension
+   (e.g. SomeClassName.js).
-    (e.g. SomeClassName.js)
+1. Avoid anonymous functions, except when functions are short (one or two lines)
-* Avoid anonymous functions, except when functions are short (a few lines)
+   and their inclusion makes sense within the flow of the code
-  and/or their inclusion makes sense within the flow of the code
+   (e.g. as arguments to a forEach call). Anonymous functions should always be arrow functions.
-  (e.g. as arguments to a forEach call.)
+1. Named functions are preferred over functions assigned to variables.
-* Avoid deep nesting (especially of functions), except where necessary
+   eg.
-  (e.g. due to closure scope.)
+   ```JavaScript
-* End with a single new-line character.
+   function renameObject(object, newName) {
-* Expose public methods by declaring them on the class's prototype.
+       Object.name = newName;
-* Within a given function's scope, do not mix declarations and imperative
+   }
-  code, and  present these in the following order:
+   ```
-  * First, variable declarations and initialization.
+   is preferable to
-  * Second, function declarations.
+   ```JavaScript
-  * Third, imperative statements.
+   const rename = (object, newName) => {
-  * Finally, the returned value.
+       Object.name = newName;
-
+   }
-Deviations from Open MCT Web code style guidelines require two-party agreement,
+   ```
+1. Avoid deep nesting (especially of functions), except where necessary
+   (e.g. due to closure scope).
+1. End with a single new-line character.
+1. Always use ES6 `Class`es and inheritence rather than the pre-ES6 prototypal 
+   pattern.
+1. Within a given function's scope, do not mix declarations and imperative
+   code, and  present these in the following order:
+   * First, variable declarations and initialization.
+   * Secondly, imperative statements.
+   * Finally, the returned value. A single return statement at the end of the function should be used, except where an early return would improve code clarity.
+1. Avoid the use of "magic" values.
+   eg.
+   ```JavaScript
+   const UNAUTHORIZED = 401;
+   if (responseCode === UNAUTHORIZED)
+   ```
+   is preferable to
+   ```JavaScript
+   if (responseCode === 401)
+   ```
+1. Use the ternary operator only for simple cases such as variable assignment. Nested ternaries should be avoided in all cases.
+1. Test specs should reside alongside the source code they test, not in a separate directory.
+1. Organize code by feature, not by type.
+   eg.
+   ```
+   - telemetryTable
+       - row
+           TableRow.js
+           TableRowCollection.js
+           TableRow.vue
+       - column
+           TableColumn.js
+           TableColumn.vue
+       plugin.js
+       pluginSpec.js
+   ```
+   is preferable to
+   ```
+   - telemetryTable
+       - components
+           TableRow.vue
+           TableColumn.vue
+       - collections
+           TableRowCollection.js
+       TableColumn.js
+       TableRow.js
+       plugin.js
+       pluginSpec.js
+   ```
+Deviations from Open MCT code style guidelines require two-party agreement,
 typically from the author of the change and its reviewer.
 
-#### Code Example
-
-```js
-/*global define*/
-
-/**
- * Bundles should declare themselves as namespaces in whichever source
- * file is most like the "main point of entry" to the bundle.
- * @namespace some/bundle
- */
-define(
-    ['./OtherClass'],
-    function (OtherClass) {
-        "use strict";
-
-        /**
-         * A summary of how to use this class goes here.
-         *
-         * @constructor
-         * @memberof some/bundle
-         */
-        function ExampleClass() {
-        }
-
-        // Methods which are not intended for external use should
-        // not have JSDoc (or should be marked @private)
-        ExampleClass.prototype.privateMethod = function () {
-        };
-
-        /**
-         * A summary of this method goes here.
-         * @param {number} n a parameter
-         * @returns {number} a return value
-         */
-        ExampleClass.prototype.publicMethod = function (n) {
-            return n * 2;
-        }
-
-        return ExampleClass;
-    }
-);
-```
-
 ### Test Standards
 
 Automated testing shall occur whenever changes are merged into the main
 development branch and must be confirmed alongside any pull request.
 
-Automated tests are typically unit tests which exercise individual software
+Automated tests are tests which exercise plugins, API, and utility classes. 
-components. Tests are subject to code review along with the actual
+Tests are subject to code review along with the actual implementation, to 
-implementation, to ensure that tests are applicable and useful.
+ensure that tests are applicable and useful.
 
 Examples of useful tests:
 * Tests which replicate bugs (or their root causes) to verify their
@@ -222,8 +239,26 @@ Examples of useful tests:
 * Tests which verify expected interactions with other components in the
   system.
 
-During automated testing, code coverage metrics will be reported. Line
+#### Guidelines
-coverage must remain at or above 80%.
+* 100% statement coverage is achievable and desirable.
+* Do blackbox testing. Test external behaviors, not internal details. Write tests that describe what your plugin is supposed to do. How it does this doesn't matter, so don't test it.
+* Unit test specs for plugins should be defined at the plugin level. Start with one test spec per plugin named pluginSpec.js, and as this test spec grows too big, break it up into multiple test specs that logically group related tests.
+* Unit tests for API or for utility functions and classes may be defined at a per-source file level.
+* Wherever possible only use and mock public API, builtin functions, and UI in your test specs. Do not directly invoke any private functions. ie. only call or mock functions and objects exposed by openmct.* (eg. openmct.telemetry, openmct.objectView, etc.), and builtin browser functions (fetch, requestAnimationFrame, setTimeout, etc.).
+* Where builtin functions have been mocked, be sure to clear them between tests.
+* Test at an appropriate level of isolation. Eg. 
+    * If you’re testing a view, you do not need to test the whole application UI, you can just fetch the view provider using the public API and render the view into an element that you have created. 
+    * You do not need to test that the view switcher works, there should be separate tests for that. 
+    * You do not need to test that telemetry providers work, you can mock openmct.telemetry.request() to feed test data to the view.
+    * Use your best judgement when deciding on appropriate scope.
+* Automated tests for plugins should start by actually installing the plugin being tested, and then test that installing the plugin adds the desired features and behavior to Open MCT, observing the above rules.
+* All variables used in a test spec, including any instances of the Open MCT API should be declared inside of an appropriate block scope (not at the root level of the source file), and should be initialized in the relevant beforeEach block. `beforeEach` is preferable to `beforeAll` to avoid leaking of state between tests.
+* A `afterEach` or `afterAll` should be used to do any clean up necessary to prevent leakage of state between test specs. This can happen when functions on `window` are wrapped, or when the URL is changed. [A convenience function](https://github.com/nasa/openmct/blob/master/src/utils/testing.js#L59) is provided for resetting the URL and clearing builtin spies between tests.
+* If writing unit tests for legacy Angular code be sure to follow [best practices in order to avoid memory leaks](https://www.thecodecampus.de/blog/avoid-memory-leaks-angularjs-unit-tests/).
+
+#### Examples
+* [Example of an automated test spec for an object view plugin](https://github.com/nasa/openmct/blob/master/src/plugins/telemetryTable/pluginSpec.js)
+* [Example of an automated test spec for API](https://github.com/nasa/openmct/blob/master/src/api/time/TimeAPISpec.js)
 
 ### Commit Message Standards
 
@@ -234,7 +269,7 @@ Commit messages should:
   line of white space.
 * Contain a short (usually one word) reference to the feature or subsystem
   the commit effects, in square brackets, at the start of the subject line
-  (e.g. `[Documentation] Draft of check-in process`)
+  (e.g. `[Documentation] Draft of check-in process`).
 * Contain a reference to a relevant issue number in the body of the commit.
   * This is important for traceability; while branch names also provide this,
     you cannot tell from looking at a commit what branch it was authored on.
@@ -250,9 +285,9 @@ Commit messages should:
 Commit messages should not:
 
 * Exceed 54 characters in length on the subject line.
-* Exceed 72 characters in length in the body of the commit.
+* Exceed 72 characters in length in the body of the commit,
   * Except where necessary to maintain the structure of machine-readable or
-    machine-generated text (e.g. error messages)
+    machine-generated text (e.g. error messages).
 
 See [Contributing to a Project](http://git-scm.com/book/ch5-2.html) from
 Pro Git by Shawn Chacon and Ben Straub for a bit of the rationale behind
@@ -260,42 +295,37 @@ these standards.
 
 ## Issue Reporting
 
-Issues are tracked at https://github.com/nasa/openmctweb/issues
+Issues are tracked at https://github.com/nasa/openmct/issues.
-
-Issues should include:
-
-* A short description of the issue encountered.
-* A longer-form description of the issue encountered. When possible, steps to
-  reproduce the issue.
-* When possible, a description of the impact of the issue. What use case does
-  it impede?
-* An assessment of the severity of the issue.
 
 Issue severity is categorized as follows (in ascending order):
 
-* _Trivial_: Minimal impact on the usefulness and functionality of the
+* _Trivial_: Minimal impact on the usefulness and functionality of the software; a "nice-to-have." Visual impact without functional impact,
-  software; a "nice-to-have."
+* _Medium_: Some impairment of use, but simple workarounds exist
-* _(Unspecified)_: Major loss of functionality or impairment of use.
+* _Critical_: Significant loss of functionality or impairment of use. Display of telemetry data is not affected though.
-* _Critical_: Large-scale loss of functionality or impairment of use,
+* _Blocker_: Major functionality is impaired or lost, threatening mission success. Display of telemetry data is impaired or blocked by the bug, which could lead to loss of situational awareness.
-  such that remaining utility becomes marginal.
-* _Blocker_: Harmful or otherwise unacceptable behavior. Must fix.
 
 ## Check Lists
 
 The following check lists should be completed and attached to pull requests
 when they are filed (author checklist) and when they are merged (reviewer
-checklist.)
+checklist).
 
 ### Author Checklist
 
-1. Changes address original issue?
+[Within PR Template](.github/PULL_REQUEST_TEMPLATE.md)
-2. Unit tests included and/or updated with changes?
-3. Command line build passes?
-4. Changes have been smoke-tested?
 
 ### Reviewer Checklist
 
-1. Changes appear to address issue?
+* [ ] Changes appear to address issue?
-2. Appropriate unit tests included?
+* [ ] Changes appear not to be breaking changes?
-3. Code style and in-line documentation are appropriate?
+* [ ] Appropriate unit tests included?
-4. Commit messages meet standards?
+* [ ] Code style and in-line documentation are appropriate?
+* [ ] Commit messages meet standards?
+* [ ] Has associated issue been labelled `unverified`? (only applicable if this PR closes the issue)
+* [ ] Has associated issue been labelled `bug`? (only applicable if this PR is for a bug fix)
+* [ ] List of Acceptance Tests Performed.
+
+Write out a small list of tests performed with just enough detail for another developer on the team 
+to execute. 
+
+i.e. ```When Clicking on Add button, new `object` appears in dropdown.```

LICENSE.md

@@ -0,0 +1,7 @@
+# Open MCT License
+
+Open MCT, Copyright (c) 2014-2021, United States Government as represented by the Administrator of the National Aeronautics and Space Administration. All rights reserved.
+
+Open MCT is licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License.  You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.
+
+Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

LICENSES.md

@@ -1,562 +0,0 @@
-# Open MCT Web Licenses
-
-Open MCT Web, Copyright (c) 2014-2015, United States Government as represented by the Administrator of the National Aeronautics and Space Administration. All rights reserved.
-
-Open MCT Web is licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License.  You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.
-
-Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
-
-Open MCT Web includes source code licensed under additional open source licenses as follows.
-
-## Software Components Licenses
-
-This software includes components released under the following licenses:
-
----
-
-### SuperSocket
-
-#### Info
-
-* Link: https://supersocket.codeplex.com/
-
-* Version: 0.9.0.2
-
-* Author: Kerry Jiang
-
-* Description: Supports SuperWebSocket
-
-#### License
-
-Copyright 2012 Kerry Jiang (kerry-jiang@hotmail.com)
-
-SuperSocket is licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License.  You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.
-
-Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
-
----
-
-### SuperWebSocket
-
-#### Info
-
-* Link: https://superswebocket.codeplex.com/
-
-* Version: 0.9.0.2
-
-* Author: Kerry Jiang
-
-* Description: WebSocket implementation for client-server communication
-
-#### License
-
-Copyright 2010-2013 Kerry Jiang (kerry-jiang@hotmail.com)
-
-SuperWebSocket is licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License.  You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.
-
-Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
-
-
----
-
-### log4net
-
-#### Info
-
-* Link: http://logging.apache.org/log4net/
-
-* Version: 1.2.13
-
-* Author: Apache Software Foundation
-
-* Description: Logging.
-
-#### License
-
-Copyright © 2004-2015 Apache Software Foundation.
-
-log4net is licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License.  You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.
-
-Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
-
----
-
-### Blanket.js
-
-#### Info
-
-* Link: http://blanketjs.org/
-
-* Version: 1.1.5
-
-* Author: Alex Seville
-
-* Description: Code coverage measurement and reporting
-
-#### License
-
-Copyright (c) 2013 Alex Seville
-
-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.
-
----
-
-### Jasmine
-
-#### Info
-
-* Link: http://jasmine.github.io/
-
-* Version: 1.3.1
-
-* Author: Pivotal Labs
-
-* Description: Unit testing
-
-#### License
-
-Copyright (c) 2008-2011 Pivotal Labs
-
-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.
-
----
-
-### RequireJS
-
-#### Info
-
-* Link: http://requirejs.org/
-
-* Version: 2.1.22
-
-* Author: The Dojo Foundation
-
-* Description: Script loader
-
-#### License
-
-Copyright (c) 2010-2015, The Dojo Foundation
-
-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.
-
----
-
-### requirejs-text
-
-#### Info
-
-* Link: https://github.com/requirejs/text
-
-* Version: 2.0.14
-
-* Author: The Dojo Foundation
-
-* Description: Text loading plugin for RequireJS
-
-#### License
-
-Copyright (c) 2010-2014, The Dojo Foundation
-
-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.
-
----
-
-### AngularJS
-
-#### Info
-
-* Link: http://angularjs.org/
-
-* Version: 1.4.4
-
-* Author: Google
-
-* Description: Client-side web application framework
-
-#### License
-
-Copyright (c) 2010-2015 Google, Inc. http://angularjs.org
-
-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.
-
----
-
-### Angular-Route
-
-#### Info
-
-* Link: http://angularjs.org/
-
-* Version: 1.4.4
-
-* Author: Google
-
-* Description: Client-side view routing
-
-#### License
-
-Copyright (c) 2010-2015 Google, Inc. http://angularjs.org
-
-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.
-
----
-
-### ES6-Promise
-
-#### Info
-
-* Link: https://github.com/jakearchibald/es6-promise
-
-* Version: 3.0.2
-
-* Authors: Yehuda Katz, Tom Dale, Stefan Penner and contributors
-
-* Description: Promise polyfill for pre-ECMAScript 6 browsers
-
-#### License
-
-Copyright (c) 2014 Yehuda Katz, Tom Dale, Stefan Penner and contributors
-
-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.
-
----
-
-### screenfull.js
-
-#### Info
-
-* Link: https://github.com/sindresorhus/screenfull.js/
-
-* Version: 3.0.0
-
-* Author: Sindre Sorhus
-
-* Description: Wrapper for cross-browser usage of fullscreen API
-
-#### License
-
-Copyright (c) Sindre Sorhus <sindresorhus@gmail.com> (sindresorhus.com)
-
-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.
-
----
-
-### Math.uuid.js
-
-#### Info
-
-* Link: https://github.com/broofa/node-uuid
-
-* Version: 1.4.7
-
-* Author: Robert Kieffer
-
-* Description: Unique identifer generation.
-
-#### License
-
-Copyright (c) 2010-2012 Robert Kieffer
-
-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.
-
----
-
-### Normalize.css
-
-#### Info
-
-* Link: https://github.com/necolas/normalize.css
-
-* Version: 1.1.2
-
-* Authors: Nicolas Gallagher, Jonathan Neal
-
-* Description: Browser style normalization
-
-#### License
-
-Copyright (c) Nicolas Gallagher and Jonathan Neal
-
-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.
-
----
-
-### Moment.js
-
-#### Info
-
-* Link: http://momentjs.com
-
-* Version: 2.11.1
-
-* Authors: Tim Wood, Iskren Chernev, Moment.js contributors
-
-* Description: Time/date parsing/formatting
-
-#### License
-
-Copyright (c) 2011-2014 Tim Wood, Iskren Chernev, Moment.js contributors
-
-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.
-
----
-
-### moment-duration-format
-
-#### Info
-
-* Link: https://github.com/jsmreese/moment-duration-format
-
-* Version: 1.3.0
-
-* Authors: John Madhavan-Reese
-
-* Description: Duration parsing/formatting
-
-#### License
-
-Copyright 2014 John Madhavan-Reese
-
-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.
-
----
-
-### CSV.js
-
-#### Info
-
-* Link: https://github.com/knrz/CSV.js
-
-* Version: 3.6.4
-
-* Authors: Kash Nouroozi
-
-* Description: Encoder for CSV (comma separated values) export
-
-#### License
-
-Copyright (c) 2014 Kash Nouroozi
-
-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.
-
----
-
-### FileSaver.js
-
-#### Info
-
-* Link: https://github.com/eligrey/FileSaver.js/
-
-* Version: 0.0.2
-
-* Authors: Eli Grey
-
-* Description: File download initiator (for file exports)
-
-#### License
-
-Copyright © 2015 Eli Grey.
-
-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.
-
----
-
-### Zepto
-
-#### Info
-
-* Link: http://zeptojs.com/
-
-* Version: 1.1.6
-
-* Authors: Thomas Fuchs
-
-* Description: DOM manipulation
-
-#### License
-
-Copyright (c) 2010-2016 Thomas Fuchs
-http://zeptojs.com/
-
-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.
-
----
-
-### Json.NET
-
-#### Info
-
-* Link: http://www.newtonsoft.com/json
-
-* Version: 6.0.8
-
-* Author: Newtonsoft
-
-* Description: JSON serialization/deserialization
-
-#### License
-
-Copyright (c) 2007 James Newton-King
-
-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.
-
----
-
-### Nancy
-
-#### Info
-
-* Link: http://nancyfx.org
-
-* Version: 0.23.2
-
-* Author: Andreas Håkansson, Steven Robbins and contributors
-
-* Description: Embedded web server
-
-#### License
-
-Copyright © 2010 Andreas Håkansson, Steven Robbins and contributors
-
-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.
-
----
-
-### Nancy.Hosting.Self
-
-#### Info
-
-* Link: http://nancyfx.org
-
-* Version: 0.23.2
-
-* Author: Andreas Håkansson, Steven Robbins and contributors
-
-* Description: Embedded web server
-
-#### License
-
-Copyright © 2010 Andreas Håkansson, Steven Robbins and contributors
-
-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.
-

README.md

@@ -1,28 +1,73 @@
-# Open MCT Web
+# Open MCT [![license](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](http://www.apache.org/licenses/LICENSE-2.0) [![Language grade: JavaScript](https://img.shields.io/lgtm/grade/javascript/g/nasa/openmct.svg?logo=lgtm&logoWidth=18)](https://lgtm.com/projects/g/nasa/openmct/context:javascript) [![codecov](https://codecov.io/gh/nasa/openmct/branch/master/graph/badge.svg?token=7DQIipp3ej)](https://codecov.io/gh/nasa/openmct) [![This project is using Percy.io for visual regression testing.](https://percy.io/static/images/percy-badge.svg)](https://percy.io/b2e34b17/openmct) [![npm version](https://img.shields.io/npm/v/openmct.svg)](https://www.npmjs.com/package/openmct) 
 
-Open MCT Web is a web-based platform for mission operations user interface
+Open MCT (Open Mission Control Technologies) is a next-generation mission control framework for visualization of data on desktop and mobile devices. It is developed at NASA's Ames Research Center, and is being used by NASA for data analysis of spacecraft missions, as well as planning and operation of experimental rover systems. As a generalizable and open source framework, Open MCT could be used as the basis for building applications for planning, operation, and analysis of any systems producing telemetry data.
-software.
 
-## Bundles
+Please visit our [Official Site](https://nasa.github.io/openmct/) and [Getting Started Guide](https://nasa.github.io/openmct/getting-started/)
 
-A bundle is a group of software components (including source code, declared
+Once you've created something amazing with Open MCT, showcase your work in our GitHub Discussions [Show and Tell](https://github.com/nasa/openmct/discussions/categories/show-and-tell) section. We love seeing unique and wonderful implementations of Open MCT!
-as AMD modules, as well as resources such as images and HTML templates)
-that are intended to be added or removed as a single unit. A plug-in for
-Open MCT Web will be expressed as a bundle; platform components are also
-expressed as bundles.
 
-A bundle is also just a directory which contains a file `bundle.json`,
+## See Open MCT in Action
-which declares its contents.
 
-The file `bundles.json` (note the plural), at the top level of the
+Try Open MCT now with our [live demo](https://openmct-demo.herokuapp.com/).
-repository, is a JSON file containing an array of all bundles (expressed as
+![Demo](https://nasa.github.io/openmct/static/res/images/Open-MCT.Browse.Layout.Mars-Weather-1.jpg)
-directory names) to include in a running instance of Open MCT Web. Adding or
+
-removing paths from this list will add or remove bundles from the running
+## Building and Running Open MCT Locally
-application.
+
+Building and running Open MCT in your local dev environment is very easy. Be sure you have [Git](https://git-scm.com/downloads) and [Node.js](https://nodejs.org/) installed, then follow the directions below. Need additional information? Check out the [Getting Started](https://nasa.github.io/openmct/getting-started/) page on our website.
+(These instructions assume you are installing as a non-root user; developers have [reported issues](https://github.com/nasa/openmct/issues/1151) running these steps with root privileges.)
+
+1. Clone the source code
+
+ `git clone https://github.com/nasa/openmct.git`
+
+2. Install development dependencies
+
+ `npm install`
+
+3. Run a local development server
+
+ `npm start`
+
+Open MCT is now running, and can be accessed by pointing a web browser at [http://localhost:8080/](http://localhost:8080/)
+
+## Open MCT v1.0.0
+This represents a major overhaul of Open MCT with significant changes under the hood. We aim to maintain backward compatibility but if you do find compatibility issues, please let us know by filing an issue in this repository. If you are having major issues with v1.0.0 please check-out the v0.14.0 tag until we can resolve them for you.
+
+If you are migrating an application built with Open MCT as a dependency to v1.0.0 from an earlier version, please refer to [our migration guide](https://nasa.github.io/openmct/documentation/migration-guide).
+
+## Documentation
+
+Documentation is available on the [Open MCT website](https://nasa.github.io/openmct/documentation/).
+
+### Examples
+
+The clearest examples for developing Open MCT plugins are in the
+[tutorials](https://github.com/nasa/openmct-tutorial) provided in
+our documentation.
+
+We want Open MCT to be as easy to use, install, run, and develop for as
+possible, and your feedback will help us get there! Feedback can be provided via [GitHub issues](https://github.com/nasa/openmct/issues/new/choose), [Starting a GitHub Discussion](https://github.com/nasa/openmct/discussions), or by emailing us at [arc-dl-openmct@mail.nasa.gov](mailto:arc-dl-openmct@mail.nasa.gov).
+
+## Building Applications With Open MCT
+
+Open MCT is built using [`npm`](http://npmjs.com/) and [`webpack`](https://webpack.js.org/).
+
+See our documentation for a guide on [building Applications with Open MCT](https://github.com/nasa/openmct/blob/master/API.md#starting-an-open-mct-application).
+
+## Plugins
+
+Open MCT can be extended via plugins that make calls to the Open MCT API. A plugin is a group 
+of software components (including source code and resources such as images and HTML templates)
+that is intended to be added or removed as a single unit.
+
+As well as providing an extension mechanism, most of the core Open MCT codebase is also 
+written as plugins.
+
+For information on writing plugins, please see [our API documentation](https://github.com/nasa/openmct/blob/master/API.md#plugins).
 
 ## Tests
 
-Tests are written for [Jasmine 1.3](http://jasmine.github.io/1.3/introduction.html)
+Tests are written for [Jasmine 3](https://jasmine.github.io/api/3.1/global)
 and run by [Karma](http://karma-runner.github.io). To run:
 
 `npm test`
@@ -38,68 +83,20 @@ naming convention is otherwise the same.)
 ### Test Reporting
 
 When `npm test` is run, test results will be written as HTML to
-`target/tests`. Code coverage information is written to `target/coverage`.
+`dist/reports/tests/`. Code coverage information is written to `dist/reports/coverage`.
 
-
+Code Coverage Reports are available from [codecov.io](https://app.codecov.io/gh/nasa/openmct/)
-### Functional Testing
-
-The tests described above are all at the unit-level; an additional
-test suite using [Protractor](https://angular.github.io/protractor/)
-is under development, in the `protractor` folder.
-
-To run:
-
-* Install protractor following the instructions above.
-* `cd protractor`
-* `npm install`
-* `npm run all`
-
-## Build
-
-Open MCT Web is built using [`npm`](http://npmjs.com/)
-and [`gulp`](http://gulpjs.com/).
-
-To build:
-
-`npm run prepublish`
-
-This will compile and minify JavaScript sources, as well as copy over assets.
-The contents of the `dist` folder will contain a runnable Open MCT Web
-instance (e.g. by starting an HTTP server in that directory), including:
-
-* A `main.js` file containing Open MCT Web source code.
-* Various assets in the `example` and `platform` directories.
-* An `index.html` that runs Open MCT Web in its default configuration.
-
-Additional `gulp` tasks are defined in [the gulpfile](gulpfile.js).
-
-### Building Documentation
-
-Open MCT Web's documentation is generated by an
-[npm](https://www.npmjs.com/)-based build.  It has additional dependencies that
-may not be available on every platform and thus is not covered in the standard
-npm install.  Ensure your system has [libcairo](http://cairographics.org/)
-installed and then run the following commands:
-
-* `npm install`
-* `npm install canvas nomnoml`
-* `npm run docs`
-
-Documentation will be generated in `target/docs`.
 
 # Glossary
 
-Certain terms are used throughout Open MCT Web with consistent meanings
+Certain terms are used throughout Open MCT with consistent meanings
 or conventions. Any deviations from the below are issues and should be
 addressed (either by updating this glossary or changing code to reflect
 correct usage.) Other developer documentation, particularly in-line
 documentation, may presume an understanding of these terms.
 
-* _bundle_: A bundle is a removable, reusable grouping of software elements.
+* _plugin_: A plugin is a removable, reusable grouping of software elements.
-  The application is composed of bundles. Plug-ins are bundles. For more
+  The application is composed of plugins.
-  information, refer to framework documentation (under `platform/framework`.)
-* _capability_: An object which exposes dynamic behavior or non-persistent
-  state associated with a domain object.
 * _composition_: In the context of a domain object, this refers to the set of
   other domain objects that compose or are contained by that object. A domain
   object's composition is the set of domain objects that should appear
@@ -112,15 +109,10 @@ documentation, may presume an understanding of these terms.
   (Most often used in the context of extensions, domain
   object models, or other similar application-specific objects.)
 * _domain object_: A meaningful object to the user; a distinct thing in
-  the work support by Open MCT Web. Anything that appears in the left-hand
+  the work support by Open MCT. Anything that appears in the left-hand
   tree is a domain object.
-* _extension_: An extension is a unit of functionality exposed to the
+* _identifier_: A tuple consisting of a namespace and a key, which together uniquely
-  platform in a declarative fashion by a bundle. For more
+  identifies a domain object.
-  information, refer to framework documentation (under `platform/framework`.)
-* _id_: A string which uniquely identifies a domain object.
-* _key_: When used as an object property, this refers to the machine-readable
-  identifier for a specific thing in a set of things. (Most often used in the
-  context of extensions or other similar application-specific object sets.)
 * _model_: The persistent state associated with a domain object. A domain
   object's model is a JavaScript object which can be converted to JSON
   without losing information (that is, it contains no methods.)
@@ -132,7 +124,5 @@ documentation, may presume an understanding of these terms.
   a user clicks on a domain object in the tree, they are _navigating_ to
   it, and it is thereafter considered the _navigated_ object (until the
   user makes another such choice.)
-* _space_: A name used to identify a persistence store. Interactions with
+* _namespace_: A name used to identify a persistence store. A running open MCT 
-  persistence with generally involve a `space` parameter in some form, to
+application could potentially use multiple persistence stores, with the 
-  distinguish multiple persistence stores from one another (for cases
-  where there are multiple valid persistence locations available.)

SECURITY.md

@@ -0,0 +1,31 @@
+# Security Policy
+
+The Open MCT team secures our code base using a combination of code review, dependency review, and periodic security reviews. Static analysis performed during automated verification additionally safeguards against common coding errors which may result in vulnerabilities.
+
+### Reporting a Vulnerability
+
+For general defects, please for a [Bug Report](https://github.com/nasa/openmct/issues/new/choose)
+
+To report a vulnerability for Open MCT please send a detailed report to [arc-dl-openmct](mailto:arc-dl-openmct@mail.nasa.gov). 
+
+See our [top-level security policy](https://github.com/nasa/openmct/security/policy) for additional information.
+
+### CodeQL and LGTM
+
+The [CodeQL GitHub Actions workflow](https://github.com/nasa/openmct/blob/master/.github/workflows/codeql-analysis.yml) is available to the public. To review the results, fork the repository and run the CodeQL workflow. 
+
+CodeQL is run for every pull-request in GitHub Actions.
+
+The project is also monitored by [LGTM](https://lgtm.com/projects/g/nasa/openmct/) and is available to public.
+
+### ESLint
+
+Static analysis is run for every push on the master branch and every pull request on all branches in Github Actions. 
+
+For more information about ESLint, visit https://eslint.org/.
+
+### General Support
+
+For additional support, please open a [Github Discussion](https://github.com/nasa/openmct/discussions). 
+
+If you wish to report a cybersecurity incident or concern, please contact the NASA Security Operations Center either by phone at 1-877-627-2732 or via email address soc@nasa.gov.

api/README.md

@@ -1,20 +0,0 @@
-# API
-
-This directory is for draft API documentation and design.  The API is organized into a few major components, which are documented in their own READMEs.  See the following:
-
-* Domain Objects
-    Capabilities
-    Events
-    Mutation
-    Etc
-
-* [Object API](object-api/README.md) (encapsulates persistence), should include roots
-* [Region API](region-api/README.md) 
-* [Telemetry API](telemetry-api/README.md)
-* [Type API](type-api/README.md)
-
-Not yet started:
-
-* [Action API](action-api/README.md)
-* [Indicators API](indicators-api/README.md) -- potentially compress into regions?
-* [Plugin API](plugin-api/README.md)

api/composition-api/CompositionAPI.js

@@ -1,93 +0,0 @@
-define([
-
-], function (
-
-) {
-
-
-    var PROVIDER_REGISTRY = [];
-
-    function getProvider (object) {
-        return PROVIDER_REGISTRY.filter(function (p) {
-            return p.appliesTo(object);
-        })[0];
-    };
-
-    function composition(object) {
-        var provider = getProvider(object);
-
-        if (!provider) {
-            return;
-        }
-
-        return new CompositionCollection(object, provider);
-    };
-
-    composition.addProvider = function (provider) {
-        PROVIDER_REGISTRY.unshift(provider);
-    };
-
-    window.MCT = window.MCT || {};
-    window.MCT.composition = composition;
-
-    function CompositionCollection(domainObject, provider) {
-        this.domainObject = domainObject;
-        this.provider = provider;
-    };
-
-    CompositionCollection.prototype.add = function (child, skipMutate) {
-        if (!this._children) {
-            throw new Error("Must load composition before you can add!");
-        }
-        // we probably should not add until we have loaded.
-        // todo: should we modify parent?
-        if (!skipMutate) {
-            this.provider.add(this.domainObject, child);
-        }
-        this.children.push(child);
-        this.emit('add', child);
-    };
-
-    CompositionCollection.prototype.load = function () {
-        return this.provider.load(this.domainObject)
-            .then(function (children) {
-                this._children = [];
-                children.map(function (c) {
-                    this.add(c, true);
-                }, this);
-                this.emit('load');
-                // Todo: set up listener for changes via provider?
-            }.bind(this));
-    };
-
-    CompositionCollection.prototype.remove = function (child) {
-        var index = this.children.indexOf(child);
-        if (index === -1) {
-            throw new Error("Unable to remove child: not found in composition");
-        }
-        this.provider.remove(this.domainObject, child);
-        this.children.splice(index, 1);
-        this.emit('remove', index, child);
-    };
-
-    var DefaultCompositionProvider = {
-        appliesTo: function (domainObject) {
-            return !!domainObject.composition;
-        },
-        load: function (domainObject) {
-            return Promise.all(domainObject.composition.map(MCT.objects.get));
-        },
-        add: function (domainObject, child) {
-            domainObject.composition.push(child.key);
-        }
-    };
-
-    composition.addProvider(DefaultCompositionProvider);
-
-    function Injector() {
-        console.log('composition api injected!');
-    }
-
-    return Injector;
-
-});

api/composition-api/README.md

@@ -1,35 +0,0 @@
-# Composition API - Overview
-
-The composition API is straightforward:
-
-MCT.composition(object) -- returns a `CompositionCollection` if the object has 
-composition, returns undefined if it doesn't.
-
-## CompositionCollection
-
-Has three events:
-* `load`: when the collection has completed loading.
-* `add`: when a new object has been added to the collection.
-* `remove` when an object has been removed from the collection.
-
-Has three methods:
-
-`Collection.load()` -- returns a promise that is fulfilled when the composition 
-    has loaded.
-`Collection.add(object)` -- add a domain object to the composition.
-`Collection.remove(object)` -- remove the object from the composition.
-
-## Composition providers
-composition providers are anything that meets the following interface:
-
-* `provider.appliesTo(domainObject)` -> return true if this provider can provide 
-    composition for a given domain object.
-* `provider.add(domainObject, childObject)` -> adds object 
-* `provider.remove(domainObject, childObject)` -> immediately removes objects
-* `provider.load(domainObject)` -> returns promise for array of children
-
-There is a default composition provider which handles loading composition for 
-any object with a `composition` property.  If you want specialized composition 
-loading behavior, implement your own composition provider and register it with
-
-`MCT.composition.addProvider(myProvider)`

api/object-api/ObjectAPI.js

@@ -1,200 +0,0 @@
-define([
-    'lodash'
-], function (
-    _
-) {
-
-    /**
-        Object API.  Intercepts the existing object API while also exposing
-        A new Object API.
-
-        MCT.objects.get('mine')
-            .then(function (root) {
-                console.log(root);
-                MCT.objects.getComposition(root)
-                    .then(function (composition) {
-                        console.log(composition)
-                    })
-            });
-    */
-
-    var Objects = {},
-        ROOT_REGISTRY = [],
-        PROVIDER_REGISTRY = {},
-        FALLBACK_PROVIDER;
-
-    window.MCT = window.MCT || {};
-    window.MCT.objects = Objects;
-
-    // take a key string and turn it into a key object
-    // 'scratch:root' ==> {namespace: 'scratch', identifier: 'root'}
-    function parseKeyString(key) {
-        if (typeof key === 'object') {
-            return key;
-        }
-        var namespace = '',
-            identifier = key;
-        for (var i = 0, escaped = false, len=key.length; i < len; i++) {
-            if (key[i] === ":" && !escaped) {
-                namespace = key.slice(0, i);
-                identifier = key.slice(i + 1);
-                break;
-            }
-        }
-        return {
-            namespace: namespace,
-            identifier: identifier
-        };
-    };
-
-    // take a key and turn it into a key string
-    // {namespace: 'scratch', identifier: 'root'} ==> 'scratch:root'
-    function makeKeyString(key) {
-        if (typeof key === 'string') {
-            return key;
-        }
-        if (!key.namespace) {
-            return key.identifier;
-        }
-        return [
-            key.namespace.replace(':', '\\:'),
-            key.identifier.replace(':', '\\:')
-        ].join(':');
-    };
-
-    // Converts composition to use key strings instead of keys
-    function toOldFormat(model) {
-        delete model.key;
-        if (model.composition) {
-            model.composition = model.composition.map(makeKeyString);
-        }
-        return model;
-    };
-
-    // converts composition to use keys instead of key strings
-    function toNewFormat(model, key) {
-        model.key = key;
-        if (model.composition) {
-            model.composition = model.composition.map(parseKeyString);
-        }
-        return model;
-    };
-
-    // Root provider is hardcoded in; can't be skipped.
-    var RootProvider = {
-        'get': function () {
-            return Promise.resolve({
-                name: 'The root object',
-                type: 'root',
-                composition: ROOT_REGISTRY
-            });
-        }
-    };
-
-    // Retrieve the provider for a given key.
-    function getProvider(key) {
-        if (key.identifier === 'ROOT') {
-            return RootProvider;
-        }
-        return PROVIDER_REGISTRY[key.namespace] || FALLBACK_PROVIDER;
-    };
-
-    Objects.addProvider = function (namespace, provider) {
-        PROVIDER_REGISTRY[namespace] = provider;
-    };
-
-    [
-        'save',
-        'delete',
-        'get'
-    ].forEach(function (method) {
-        Objects[method] = function () {
-            var key = arguments[0],
-                provider = getProvider(key);
-
-            if (!provider) {
-                throw new Error('No Provider Matched');
-            }
-
-            if (!provider[method]) {
-                throw new Error('Provider does not support [' + method + '].');
-            }
-
-            return provider[method].apply(provider, arguments);
-        };
-    });
-
-    Objects.addRoot = function (key) {
-        ROOT_REGISTRY.unshift(key);
-    };
-
-    Objects.removeRoot = function (key) {
-        ROOT_REGISTRY = ROOT_REGISTRY.filter(function (k) {
-            return (
-                k.identifier !== key.identifier ||
-                k.namespace !== key.namespace
-            );
-        });
-    };
-
-    function ObjectServiceProvider(objectService, instantiate) {
-        this.objectService = objectService;
-        this.instantiate = instantiate;
-    }
-
-    ObjectServiceProvider.prototype.save = function (object) {
-        var key = object.key,
-            keyString = makeKeyString(key),
-            newObject = this.instantiate(toOldFormat(object), keyString);
-
-        return object.getCapability('persistence')
-                .persist()
-                .then(function () {
-                    return toNewFormat(object, key);
-                });
-    };
-
-    ObjectServiceProvider.prototype.delete = function (object) {
-        // TODO!
-    };
-
-    ObjectServiceProvider.prototype.get = function (key) {
-        var keyString = makeKeyString(key);
-        return this.objectService.getObjects([keyString])
-            .then(function (results) {
-                var model = JSON.parse(JSON.stringify(results[keyString].getModel()));
-                return toNewFormat(model, key);
-            });
-    };
-
-    // Injects new object API as a decorator so that it hijacks all requests.
-    // Object providers implemented on new API should just work, old API should just work, many things may break.
-    function ObjectAPIInjector(ROOTS, instantiate, objectService) {
-        this.getObjects = function (keys) {
-            var results = {},
-                promises = keys.map(function (keyString) {
-                    var key = parseKeyString(keyString);
-                    return Objects.get(key)
-                        .then(function (object) {
-                            object = toOldFormat(object)
-                            results[keyString] = instantiate(object, keyString);
-                        });
-                });
-
-            return Promise.all(promises)
-                .then(function () {
-                    return results;
-                });
-        };
-
-        FALLBACK_PROVIDER = new ObjectServiceProvider(objectService, instantiate);
-
-        ROOTS.forEach(function (r) {
-            ROOT_REGISTRY.push(parseKeyString(r.id));
-        });
-
-        return this;
-    }
-
-    return ObjectAPIInjector;
-});

api/object-api/README.md

@@ -1,101 +0,0 @@
-# Object API - Overview
-
-The object API provides methods for fetching domain objects.
-
-# Keys
-Keys are a composite identifier that is used to create and persist objects.  Ex:
-```javascript
-{
-    namespace: 'elastic',
-    identifier: 'myIdentifier'
-}
-```
-
-In old MCT days, we called this an "id", and we encoded it in a single string.  
-The above key would encode into the identifier, `elastic:myIdentifier`.
-
-When interacting with the API you will be dealing with key objects.
-
-# Configuring the Object API
-
-The following methods should be used before calling run.  They allow you to 
-configure the persistence space of MCT.
-
-* `MCT.objects.addRoot(key)` -- add a "ROOT" to Open MCT by specifying it's 
-    key.
-* `MCT.objects.removeRoot(key)` -- Remove a "ROOT" from Open MCT by key.
-* `MCT.objects.addProvider(namespace, provider)` -- register an object provider
-    for a specific namespace.  See below for documentation on the provider 
-    interface.
-    
-# Using the object API
-
-The object API provides methods for getting, saving, and deleting objects.
-
-* MCT.objects.get(key) -> returns promise for an object
-* MCT.objects.save(object) -> returns promise that is resolved when object
-    has been saved
-* MCT.objects.delete(object) -> returns promise that is resolved when object has 
-    been deleted
-
-## Configuration Example: Adding a groot
-
-The following example adds a new root object for groot and populates it with
-some pieces of groot.
-
-```javascript
-
-var ROOT_KEY = {
-    namespace: 'groot',
-    identifier: 'groot'
-};
-
-var GROOT_ROOT = {
-    name: 'I am groot',
-    type: 'folder',
-    composition: [
-        {
-            namespace: 'groot',
-            identifier: 'arms'
-        },
-        {
-            namespace: 'groot',
-            identifier: 'legs'
-        },
-        {
-            namespace: 'groot',
-            identifier: 'torso'
-        }
-    ]
-};
-
-var GrootProvider = {
-    get: function (key) {
-        if (key.identifier === 'groot') {
-            return Promise.resolve(GROOT_ROOT);
-        }
-        return Promise.resolve({
-            name: 'Groot\'s ' + key.identifier
-        });
-    }
-};
-
-MCT.objects.addRoot(ROOT_KEY);
-
-MCT.objects.addProvider('groot', GrootProvider);
-
-MCT.run();
-```
-
-### Making a custom provider:
-
-All methods on the provider interface are optional, so you do not need
-to modify them.
-
-* `provider.get(key)` -> promise for a domain object.
-* `provider.save(domainObject)` -> returns promise that is fulfilled when object 
-    has been saved.
-* `provider.delete(domainObject)` -> returns promise that is fulfilled when 
-    object has been deleted.
-
-

api/region-api/README.md

@@ -1,64 +0,0 @@
-# Region API - Overview
-
-The region API provides a method for specifying which views should display in a given region for a given domain object.  As such, they also define the basic view interface that components must define.
-
-### MCT.region.Region
-
-The base region type, all regions implement this interface.
-
-`register(view)`
-
-`getViews(domainObject)`
-
-Additionally, Regions may have subregions for different modes of the application.  Specifying a view for a region 
-
-### MCT.region.View
-
-The basic type for views.  You can extend this to implement your own functionality, or you can create your own object so long as it meets the interface.
-
-`attribute` | `type` | `note`
---- | --- | ---
-`label` | `string` or `Function` | The name of the view.  Used in the view selector when more than one view exists for an object.
-`glyph` | `string` or `Function` | The glyph to associate with this view.  Used in the view selector when more than one view exists for an object.
-`instantiate` | `Function` | constructor for a view.  Will be invoked with two arguments, `container` and `domainObject`.  It should return an object with a `destroy` method that is called when the view is removed.
-`appliesTo` | `Function` | Determines if a view applies to a specific domain object.  Will be invoked with a domainObject.  Should return a number, `priority` if the view applies to a given object.  If multiple views return a truthy value for a given object, they will be ordered by priority, and the largest priority value will be the default view for the object.  Return `false` if a view should not apply to an object.
-
-Basic Hello World:
-
-```javascript
-
-function HelloWorldView(container, domainObject) {
-    container.innerHTML = 'Hello World!';
-}
-
-HelloWorldView.label = 'Hello World';
-HelloWorldView.glyph = 'whatever';
-
-HelloWorldView.appliesTo = function (domainObject) {
-    return 10;
-};
-
-HelloWorldView.prototype.destroy = function () {
-    // clean up outstanding handlers;
-};
-
-MCT.regions.Main.register(HelloWorldView);
-
-```
-
-## Region Hierarchy
-
-Regions are organized in a hierarchy, with the most specific region taking precedence over less specific regions.
-
-If you specify a view for the Main Region, it will be used for both Edit and View modes.  You can override the Main Region view for a specific mode by registering the view with that specific mode.
-
-### MCT.regions.Tree
-### MCT.regions.Main
-### MCT.regions.Main.View
-### MCT.regions.Main.Edit
-### MCT.regions.Inspector
-### MCT.regions.Inspector.View
-### MCT.regions.Inspector.Edit
-### MCT.regions.Toolbar
-### MCT.regions.Toolbar.View
-### MCT.regions.Toolbar.Edit

api/region-api/RegionAPI.js

@@ -1,11 +0,0 @@
-define([
-    
-], function () {
-    
-    function RegionAPI() {
-        window.MCT = window.MCT || {};
-        window.MCT.regions = {};
-    }
-    
-    return RegionAPI;
-})

api/telemetry-api/README.md

@@ -1,71 +0,0 @@
-# Telemetry API - Overview
-
-The Telemetry API provides basic methods for retrieving historical and realtime telemetry data, retrieving telemetry metadata, and registering additional telemetry providers.   
-
-The Telemetry API also provides a set of helpers built upon these basics-- TelemetryFormatters help you format telemetry values for display purposes, LimitEvaluators help you display evaluate and display alarm states, while TelemetryCollections provide a method for seamlessly combining historical and realtime data, while supporting more advanced client side filtering and interactivity.
-
-
-## Getting Telemetry Data
-
-
-### `MCT.telemetry.request(domainObject, options)`
-
-Request historical telemetry for a domain object.  Options allows you to specify filters (start, end, etc.), sort order, and strategies for retrieving telemetry (aggregation, latest available, etc.).
-
-Returns a `Promise` for an array of telemetry values.
-
-### `MCT.telemetry.subscribe(domainObject, callback, options)`
-
-Subscribe to realtime telemetry for a specific domain object.  callback will be called whenever data is received from a realtime provider.  Options allows you to specify ???
-
-## Understanding Telemetry
-
-### `MCT.telemetry.getMetadata(domainObject)`
-
-Retrieve telemetry metadata for a domain object.  Telemetry metadata helps you understand the sort of telemetry data a domain object can provide-- for instances, the possible enumerations or states, the units, and more.
-
-### `MCT.telemetry.Formatter`
-
-Telemetry formatters help you format telemetry values for display.  Under the covers, they use telemetry metadata to interpret your telemetry data, and then they use the format API to format that data for display.
-
-
-### `MCT.telemetry.LimitEvaluator`
-
-Limit Evaluators help you evaluate limit and alarm status of individual telemetry datums for display purposes without having to interact directly with the Limit API.  
-
-## Adding new telemetry sources
-
-### `MCT.telemetry.registerProvider(telemetryProvider)`
-
-Register a telemetry provider with the telemetry service.  This allows you to connect alternative telemetry sources to   For more information, see the `MCT.telemetry.BaseProvider`
-
-### `MCT.telemetry.BaseProvider`
-
-The base provider is a great starting point for developers who would like to implement their own telemetry provider.  At the same time, you can implement your own telemetry provider as long as it meets the TelemetryProvider (see other docs).
-
-## Other tools
-
-### `MCT.telemetry.TelemetryCollection`
-
-The TelemetryCollection is a useful tool for building advanced displays.  It helps you seamlessly handle both historical and realtime telemetry data, while making it easier to deal with large data sets and interactive displays that need to frequently requery data.
-
-
-
-# API Reference (TODO)
-
-* Telemetry Metadata
-* Request Options
-    -- start
-    -- end
-    -- sort
-    -- ???
-    -- strategies -- specify which strategies you want.  an array provides for fallback strategies without needing decoration.  Design fallbacks into API.
-
-### `MCT.telemetry.request(domainObject, options)`
-### `MCT.telemetry.subscribe(domainObject, callback, options)`
-### `MCT.telemetry.getMetadata(domainObject)`
-### `MCT.telemetry.Formatter`
-### `MCT.telemetry.LimitEvaluator`
-### `MCT.telemetry.registerProvider(telemetryProvider)`
-### `MCT.telemetry.BaseProvider`
-### `MCT.telemetry.TelemetryCollection`

api/telemetry-api/TelemetryAPI.js

@@ -1,239 +0,0 @@
-/*global define,window,console,MCT*/
-
-/**
-
-var key = '114ced6c-deb7-4169-ae71-68c571665514';
-MCT.objects.getObject([key])
-    .then(function (results) {
-        console.log('got results');
-        return results[key];
-    })
-    .then(function (domainObject) {
-        console.log('got object');
-        MCT.telemetry.subscribe(domainObject, function (datum) {
-            console.log('gotData!', datum);
-        });
-    });
-});
-
-
-*/
-
-define([
-    'lodash',
-    'eventemitter2'
-], function (
-    _,
-    EventEmitter
-) {
-
-    // format map is a placeholder until we figure out format service.
-    var FORMAT_MAP = {
-        generic: function (range) {
-            return function (datum) {
-                return datum[range.key];
-            };
-        },
-        enum: function (range) {
-            var enumMap = _.indexBy(range.enumerations, 'value');
-            return function (datum) {
-                try {
-                    return enumMap[datum[range.valueKey]].text;
-                } catch (e) {
-                    return datum[range.valueKey];
-                }
-            };
-        }
-    };
-
-    FORMAT_MAP.number =
-        FORMAT_MAP.float =
-        FORMAT_MAP.integer =
-        FORMAT_MAP.ascii =
-        FORMAT_MAP.generic;
-
-
-
-    function TelemetryAPI(
-        formatService
-    ) {
-
-        var FORMATTER_CACHE = new WeakMap(),
-            EVALUATOR_CACHE = new WeakMap();
-
-        function testAPI() {
-            var key = '114ced6c-deb7-4169-ae71-68c571665514';
-            window.MCT.objects.getObjects([key])
-                .then(function (results) {
-                    console.log('got results');
-                    return results[key];
-                })
-                .then(function (domainObject) {
-                    var formatter = new MCT.telemetry.Formatter(domainObject);
-                    console.log('got object');
-                    window.MCT.telemetry.subscribe(domainObject, function (datum) {
-                        var formattedValues = {};
-                        Object.keys(datum).forEach(function (key) {
-                            formattedValues[key] = formatter.format(datum, key);
-                        });
-                        console.log(
-                            'datum:',
-                            datum,
-                            'formatted:',
-                            formattedValues
-                        );
-                    });
-                });
-        }
-
-        function getFormatter(range) {
-            if (FORMAT_MAP[range.type]) {
-                return FORMAT_MAP[range.type](range);
-            }
-            try {
-                var format = formatService.getFormat(range.type).format.bind(
-                        formatService.getFormat(range.type)
-                    ),
-                    formatter = function (datum) {
-                        return format(datum[range.key]);
-                    };
-                return formatter;
-            } catch (e) {
-                console.log('could not retrieve format', range, e, e.message);
-                return FORMAT_MAP.generic(range);
-            }
-        }
-
-        function TelemetryFormatter(domainObject) {
-            this.metadata = domainObject.getCapability('telemetry').getMetadata();
-            this.formats = {};
-            var ranges = this.metadata.ranges.concat(this.metadata.domains);
-
-            ranges.forEach(function (range) {
-                this.formats[range.key] = getFormatter(range);
-            }, this);
-        }
-
-        /**
-         * Retrieve the 'key' from the datum and format it accordingly to
-         * telemetry metadata in domain object.
-         */
-        TelemetryFormatter.prototype.format = function (datum, key) {
-            return this.formats[key](datum);
-        };
-
-        function LimitEvaluator(domainObject) {
-            this.domainObject = domainObject;
-            this.evaluator = domainObject.getCapability('limit');
-            if (!this.evaluator) {
-                this.evalute = function () {
-                    return '';
-                }
-            }
-        }
-
-        /** TODO: Do we need a telemetry parser, or do we assume telemetry
-        is numeric by default? */
-
-        LimitEvaluator.prototype.evaluate = function (datum, key) {
-            return this.evaluator.evaluate(datum, key);
-        };
-
-        /** Basic telemetry collection, needs more magic. **/
-        function TelemetryCollection(domainObject) {
-            this.domainObject = domainObject;
-            this.data = [];
-        }
-
-        _.extend(TelemetryCollection.prototype, EventEmitter.prototype);
-
-        TelemetryCollection.prototype.request = function (options) {
-            request(this.domainObject, options).then(function (data) {
-                data.forEach(function (datum) {
-                    this.addDatum(datum);
-                }, this);
-            }.bind(this));
-        };
-
-        TelemetryCollection.prototype.addDatum = function (datum) {
-            this.data.push(datum);
-            this.emit('add', datum);
-        };
-
-        TelemetryCollection.prototype.subscribe = function (options) {
-            if (this.unsubscribe) {
-                this.unsubscribe();
-                delete this.unsubscribe;
-            }
-
-            this.unsubscribe = subscribe(
-                this.domainObject,
-                function (telemetrySeries) {
-                    telemetrySeries.getData().forEach(this.addDatum, this);
-                }.bind(this),
-                options
-            );
-        };
-
-        function registerProvider(provider) {
-            // Not yet implemented.
-            console.log('registering provider', provider);
-        }
-
-        function registerEvaluator(evaluator) {
-            // not yet implemented.
-            console.log('registering evaluator', evaluator);
-        }
-
-        function request(domainObject, options) {
-            return domainObject.getCapability('telemetry')
-                .requestData(options)
-                .then(function (telemetrySeries) {
-                    return telemetrySeries.getData();
-                });
-        }
-
-        function subscribe(domainObject, callback, options) {
-            return domainObject.getCapability('telemetry')
-                .subscribe(function (series) {
-                    series.getData().forEach(callback);
-                }, options);
-        }
-
-        var Telemetry = {
-            registerProvider: registerProvider,
-            registerEvaluator: registerEvaluator,
-            request: request,
-            subscribe: subscribe,
-            getMetadata: function (domainObject) {
-                return domainObject.getCapability('telemetry').getMetadata();
-            },
-            Formatter: function (domainObject) {
-                if (!FORMATTER_CACHE.has(domainObject)) {
-                    FORMATTER_CACHE.set(
-                        domainObject,
-                        new TelemetryFormatter(domainObject)
-                    );
-                }
-                return FORMATTER_CACHE.get(domainObject);
-            },
-            LimitEvaluator: function (domainObject) {
-                if (!EVALUATOR_CACHE.has(domainObject)) {
-                    EVALUATOR_CACHE.set(
-                        domainObject,
-                        new LimitEvaluator(domainObject)
-                    );
-                }
-                return EVALUATOR_CACHE.get(domainObject);
-            }
-        };
-
-        window.MCT = window.MCT || {};
-        window.MCT.telemetry = Telemetry;
-        window.testAPI = testAPI;
-
-        return Telemetry;
-    }
-
-    return TelemetryAPI;
-});

api/telemetry-api/bundle.js

@@ -1,46 +0,0 @@
-/*****************************************************************************
- * Open MCT Web, Copyright (c) 2014-2015, United States Government
- * as represented by the Administrator of the National Aeronautics and Space
- * Administration. All rights reserved.
- *
- * Open MCT Web is licensed under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- * http://www.apache.org/licenses/LICENSE-2.0.
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
- * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
- * License for the specific language governing permissions and limitations
- * under the License.
- *
- * Open MCT Web includes source code licensed under additional open source
- * licenses. See the Open Source Licenses file (LICENSES.md) included with
- * this source code distribution or the Licensing information page available
- * at runtime from the About dialog for additional information.
- *****************************************************************************/
-/*global define*/
-
-define([
-    './TelemetryAPI',
-    'legacyRegistry'
-], function (
-    TelemetryAPI,
-    legacyRegistry
-) {
-    legacyRegistry.register('api/telemetry-api', {
-        name: 'Telemetry API',
-        description: 'The public Telemetry API',
-        extensions: {
-            runs: [
-                {
-                    key: "TelemetryAPI",
-                    implementation: TelemetryAPI,
-                    depends: [
-                        'formatService'
-                    ]
-                }
-            ]
-        }
-    });
-});

api/type-api/README.md

@@ -1,31 +0,0 @@
-# Type API - Overview
-
-The Type API allows you to register type information for domain objects, and allows you to retrieve type information about a given domain object.  Crucially, type information allows you to add new creatible object types.
-
-### MCT.types.Type
-
-The basic interface for a type.  You can extend this to implement your own type,
-or you can provide an object that implements the same interface.
-
-`attribute` | `type` | `note`
---- | --- | ---
-`label` | `String` | The human readible name of the type.
-`key` | `String` | The unique identifier for this type.  
-`glyph` | `String` | The glyph identifier for the type.  Displayed in trees, labels, and other locations.
-`description` | `String` | A basic description of the type visible in the create menu.
-`isCreatible` | `Boolean`, `Number`, or `Function` | If truthy, this type will be visible in the create menu.  Note that objects not in the create menu can be instantiated via other means.
-`namespace` | `String` | The object namespace that provides instances of this type.  This allows you to implement custom object providers for specific types while still utilizing other namespaces for persistence.
-`properties` | `Object` | Object defining properties of an instance of this class.  Properties are used for automatic form generation and automated metadata display.  For more information on the definition of this object, look at (some resource-- jsonschema?)
-`canContain` | `Function` | determins whether objects of this type can contain other objects.  Will be invoked with a domain object.  Return true to allow composition, return false to disallow composition.
-
-### MCT.types.register(type)
-
-Register a type with the type API.  Registering a type with the same key as another type will replace the original type definition.
-
-### MCT.types.getType(typeKey)
-
-Returns the type definition for a given typeKey.  returns undefined if type does not exist.
-
-### MCT.types.getType(domainObject)
-
-Return the type definition for a given domain object.

api/type-api/TypeAPI.js

@@ -1,10 +0,0 @@
-define([
-    
-], function () {
-    function TypeAPI() {
-        window.MCT = window.MCT || {};
-        window.MCT.types = {};
-    }
-    
-    return TypeAPI;
-});

app.js

@@ -7,72 +7,78 @@
  * node app.js [options]
  */
 
-(function () {
+const options = require('minimist')(process.argv.slice(2));
-    "use strict";
+const express = require('express');
+const app = express();
+const fs = require('fs');
+const request = require('request');
 
-    var BUNDLE_FILE = 'bundles.json',
+// Defaults
-        options = require('minimist')(process.argv.slice(2)),
+options.port = options.port || options.p || 8080;
-        express = require('express'),
+options.host = options.host || 'localhost';
-        app = express(),
+options.directory = options.directory || options.D || '.';
-        fs = require('fs'),
-        request = require('request');
 
-    // Defaults
+// Show command line options
-    options.port = options.port || options.p || 8080;
+if (options.help || options.h) {
-    ['include', 'exclude', 'i', 'x'].forEach(function (opt) {
+    console.log("\nUsage: node app.js [options]\n");
-        options[opt] = options[opt] || [];
+    console.log("Options:");
-        // Make sure includes/excludes always end up as arrays
+    console.log("  --help, -h               Show this message.");
-        options[opt] = Array.isArray(options[opt]) ?
+    console.log("  --port, -p <number>      Specify port.");
-                options[opt] : [options[opt]];
+    console.log("  --directory, -D <bundle>   Serve files from specified directory.");
-    });
+    console.log("");
-    options.include = options.include.concat(options.i);
+    process.exit(0);
-    options.exclude = options.exclude.concat(options.x);
+}
 
-    // Show command line options
+app.disable('x-powered-by');
-    if (options.help || options.h) {
+
-        console.log("\nUsage: node app.js [options]\n");
+app.use('/proxyUrl', function proxyRequest(req, res, next) {
-        console.log("Options:");
+    console.log('Proxying request to: ', req.query.url);
-        console.log("  --help, -h               Show this message.");
+    req.pipe(request({
-        console.log("  --port, -p <number>      Specify port.");
+        url: req.query.url,
-        console.log("  --include, -i <bundle>   Include the specified bundle.");
+        strictSSL: false
-        console.log("  --exclude, -x <bundle>   Exclude the specified bundle.");
+    }).on('error', next)).pipe(res);
-        console.log("");
+});
-        process.exit(0);
+
+class WatchRunPlugin {
+    apply(compiler) {
+        compiler.hooks.emit.tapAsync('WatchRunPlugin', (compilation, callback) => {
+            console.log('Begin compile at ' + new Date());
+            callback();
+        });
     }
+}
 
-    // Override bundles.json for HTTP requests
+const webpack = require('webpack');
-    app.use('/' + BUNDLE_FILE, function (req, res) {
+const webpackConfig = require('./webpack.dev.js');
-        var bundles;
+webpackConfig.plugins.push(new webpack.HotModuleReplacementPlugin());
+webpackConfig.plugins.push(new WatchRunPlugin());
 
-        try {
+webpackConfig.entry.openmct = [
-            bundles = JSON.parse(fs.readFileSync(BUNDLE_FILE, 'utf8'));
+    'webpack-hot-middleware/client?reload=true',
-        } catch (e) {
+    webpackConfig.entry.openmct
-            bundles = [];
+];
-        }
 
-        // Handle command line inclusions/exclusions
+const compiler = webpack(webpackConfig);
-        bundles = bundles.concat(options.include);
-        bundles = bundles.filter(function (bundle) {
-            return options.exclude.indexOf(bundle) === -1;
-        });
-        bundles = bundles.filter(function (bundle, index) { // Uniquify
-            return bundles.indexOf(bundle) === index;
-        });
 
-        res.send(JSON.stringify(bundles));
+app.use(require('webpack-dev-middleware')(
-    });
+    compiler,
+    {
+        publicPath: '/dist',
+        logLevel: 'warn'
+    }
+));
 
-    app.use('/proxyUrl', function proxyRequest(req, res, next) {
+app.use(require('webpack-hot-middleware')(
-        console.log('Proxying request to: ', req.query.url);
+    compiler,
-        req.pipe(request({
+    {}
-            url: req.query.url,
+));
-            strictSSL: false
-        }).on('error', next)).pipe(res);
-    });
 
-    // Expose everything else as static files
+// Expose index.html for development users.
-    app.use(express['static']('.'));
+app.get('/', function (req, res) {
+    fs.createReadStream('index.html').pipe(res);
+});
 
-    // Finally, open the HTTP server
+// Finally, open the HTTP server and log the instance to the console
-    app.listen(options.port);
+app.listen(options.port, options.host, function() {
-}());
+    console.log('Open MCT application running at %s:%s', options.host, options.port);
+});

bower.json

@@ -1,25 +0,0 @@
-{
-  "name": "openmctweb",
-  "description": "The OpenMCTWeb core platform",
-  "main": "",
-  "license": "Apache-2.0",
-  "moduleType": [],
-  "homepage": "http://nasa.github.io/openmctweb/",
-  "private": true,
-  "dependencies": {
-    "angular": "1.4.4",
-    "angular-route": "1.4.4",
-    "moment": "^2.11.1",
-    "moment-duration-format": "^1.3.0",
-    "requirejs": "~2.1.22",
-    "text": "requirejs-text#^2.0.14",
-    "es6-promise": "^3.0.2",
-    "screenfull": "^3.0.0",
-    "node-uuid": "^1.4.7",
-    "comma-separated-values": "^3.6.4",
-    "FileSaver.js": "^0.0.2",
-    "zepto": "^1.1.6",
-    "eventemitter2": "^1.0.0",
-    "lodash": "3.10.1"
-  }
-}

build-docs.sh

@@ -1,11 +1,11 @@
 #!/bin/bash
 
 #*****************************************************************************
-#* Open MCT Web, Copyright (c) 2014-2015, United States Government
+#* Open MCT, Copyright (c) 2014-2021, United States Government
 #* as represented by the Administrator of the National Aeronautics and Space
 #* Administration. All rights reserved.
 #*
-#* Open MCT Web is licensed under the Apache License, Version 2.0 (the
+#* Open MCT is licensed under the Apache License, Version 2.0 (the
 #* "License"); you may not use this file except in compliance with the License.
 #* You may obtain a copy of the License at
 #* http://www.apache.org/licenses/LICENSE-2.0.
@@ -16,23 +16,25 @@
 #* License for the specific language governing permissions and limitations
 #* under the License.
 #*
-#* Open MCT Web includes source code licensed under additional open source
+#* Open MCT includes source code licensed under additional open source
 #* licenses. See the Open Source Licenses file (LICENSES.md) included with
 #* this source code distribution or the Licensing information page available
 #* at runtime from the About dialog for additional information.
 #*****************************************************************************
 
-# Script to build and deploy docs to github pages.
+# Script to build and deploy docs.
 
-OUTPUT_DIRECTORY="target/docs"
+OUTPUT_DIRECTORY="dist/docs"
-REPOSITORY_URL="git@github.com:nasa/openmctweb.git"
+# Docs, once built, are pushed to the private website repo
+REPOSITORY_URL="git@github.com:nasa/openmct-website.git"
+WEBSITE_DIRECTORY="website"
 
-BUILD_SHA=`git rev-parse head`
+BUILD_SHA=`git rev-parse HEAD`
 
 # A remote will be created for the git repository we are pushing to.
-# Don't worry, as this entire directory will get trashed inbetween builds.
+# Don't worry, as this entire directory will get trashed in between builds.
 REMOTE_NAME="documentation"
-WEBSITE_BRANCH="gh-pages"
+WEBSITE_BRANCH="master"
 
 # Clean output directory, JSDOC will recreate
 if [ -d $OUTPUT_DIRECTORY ]; then
@@ -40,23 +42,21 @@ if [ -d $OUTPUT_DIRECTORY ]; then
 fi
 
 npm run docs
-cd $OUTPUT_DIRECTORY || exit 1
 
-echo "git init"
+echo "git clone $REPOSITORY_URL website"
-git init
+git clone $REPOSITORY_URL website || exit 1
+echo "cp -r $OUTPUT_DIRECTORY $WEBSITE_DIRECTORY"
+cp -r $OUTPUT_DIRECTORY $WEBSITE_DIRECTORY
+echo "cd $WEBSITE_DIRECTORY"
+cd $WEBSITE_DIRECTORY || exit 1
 
 # Configure github for CircleCI user.
 git config user.email "buildbot@circleci.com"
 git config user.name "BuildBot"
 
-echo "git remote add $REMOTE_NAME $REPOSITORY_URL"
-git remote add $REMOTE_NAME $REPOSITORY_URL
 echo "git add ."
 git add .
-echo "git commit -m \"Generate docs from build $BUILD_SHA\""
+echo "git commit -m \"Docs updated from build $BUILD_SHA\""
-git commit -m "Generate docs from build $BUILD_SHA"
+git commit -m "Docs updated from build $BUILD_SHA"
-
+# Push to the website repo
-echo "git push $REMOTE_NAME HEAD:$WEBSITE_BRANCH -f"
+git push
-git push $REMOTE_NAME HEAD:$WEBSITE_BRANCH -f
-
-echo "Documentation pushed to gh-pages branch."

circle.yml

@@ -1,18 +0,0 @@
-deployment:
-  production:
-    branch: master
-    commands:
-      - npm install canvas nomnoml
-      - ./build-docs.sh
-      - git push git@heroku.com:openmctweb-demo.git $CIRCLE_SHA1:refs/heads/master
-  openmctweb-staging-un:
-    branch: nem_prototype
-    heroku:
-      appname: openmctweb-staging-un
-  openmctweb-staging-deux:
-    branch: mobile
-    heroku:
-      appname: openmctweb-staging-deux
-test:
-  post:
-    - npm run jshint --silent

codecov.yml

@@ -0,0 +1,31 @@
+codecov:
+  require_ci_to_pass: false #This setting will update the bot regardless of whether or not tests pass
+
+coverage:
+  status:
+    project:
+      default:
+        informational: true
+    patch:
+      default:
+        informational: true
+  precision: 2
+  round: down
+  range: "66...100"
+
+ignore:
+  - "**/*Spec.js"
+  - "e2e"
+
+parsers:
+  gcov:
+    branch_detection:
+      conditional: true
+      loop: true
+      method: false
+      macro: false
+
+comment:
+  layout: "reach,diff,flags,files,footer"
+  behavior: default
+  require_changes: false

copyright-notice.html

@@ -1,9 +1,9 @@
 <!--
- Open MCT Web, Copyright (c) 2014-2015, United States Government
+ Open MCT, Copyright (c) 2014-2021, United States Government
  as represented by the Administrator of the National Aeronautics and Space
  Administration. All rights reserved.
 
- Open MCT Web is licensed under the Apache License, Version 2.0 (the
+ Open MCT is licensed under the Apache License, Version 2.0 (the
  "License"); you may not use this file except in compliance with the License.
  You may obtain a copy of the License at
  http://www.apache.org/licenses/LICENSE-2.0.
@@ -14,12 +14,8 @@
  License for the specific language governing permissions and limitations
  under the License.
 
- Open MCT Web includes source code licensed under additional open source
+ Open MCT includes source code licensed under additional open source
  licenses. See the Open Source Licenses file (LICENSES.md) included with
  this source code distribution or the Licensing information page available
  at runtime from the About dialog for additional information.
 -->
-<mct-container key="overlay">
-    <mct-include key="'about-dialog'">
-    </mct-include>
-</mct-container>

copyright-notice.js

@@ -0,0 +1,21 @@
+/*****************************************************************************
+ * Open MCT, Copyright (c) 2014-2021, United States Government
+ * as represented by the Administrator of the National Aeronautics and Space
+ * Administration. All rights reserved.
+ *
+ * Open MCT is licensed under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0.
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+ * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+ * License for the specific language governing permissions and limitations
+ * under the License.
+ *
+ * Open MCT includes source code licensed under additional open source
+ * licenses. See the Open Source Licenses file (LICENSES.md) included with
+ * this source code distribution or the Licensing information page available
+ * at runtime from the About dialog for additional information.
+ *****************************************************************************/

docs/footer.html

@@ -1,9 +1,3 @@
         <hr>
-        <cite>
-            This document is styled using
-            <a href="https://github.com/jasonm23/markdown-css-themes">
-                https://github.com/jasonm23/markdown-css-themes
-            </a>.
-        </cite>
     </body>
 </html>

docs/gendocs.js

@@ -1,9 +1,9 @@
 /*****************************************************************************
- * Open MCT Web, Copyright (c) 2014-2015, United States Government
+ * Open MCT, Copyright (c) 2014-2021, United States Government
  * as represented by the Administrator of the National Aeronautics and Space
  * Administration. All rights reserved.
  *
- * Open MCT Web is licensed under the Apache License, Version 2.0 (the
+ * Open MCT is licensed under the Apache License, Version 2.0 (the
  * "License"); you may not use this file except in compliance with the License.
  * You may obtain a copy of the License at
  * http://www.apache.org/licenses/LICENSE-2.0.
@@ -14,7 +14,7 @@
  * License for the specific language governing permissions and limitations
  * under the License.
  *
- * Open MCT Web includes source code licensed under additional open source
+ * Open MCT includes source code licensed under additional open source
  * licenses. See the Open Source Licenses file (LICENSES.md) included with
  * this source code distribution or the Licensing information page available
  * at runtime from the About dialog for additional information.

docs/header.html

@@ -1,7 +1,9 @@
 <html>
     <head>
         <link rel="stylesheet"
-              href="http://jasonm23.github.io/markdown-css-themes/avenir-white.css">
+              href="//nasa.github.io/openmct/static/res/css/styles.css">
+        <link rel="stylesheet"
+              href="//nasa.github.io/openmct/static/res/css/documentation.css">
     </head>
     <body>
 

docs/src/architecture/framework.md

@@ -5,7 +5,7 @@ software components to communicate. The software components it recognizes
 are:
 
 * _Extensions_: Individual units of functionality that can be added to
-  or removed from Open MCT Web. _Extension categories_ distinguish what
+  or removed from Open MCT. _Extension categories_ distinguish what
   type of functionality is being added/removed.
 * _Bundles_: A grouping of related extensions
   (named after an analogous concept from [OSGi](http://www.osgi.org/))
@@ -19,7 +19,7 @@ manner which the framework layer can understand.
 
 ```nomnoml
 #direction: down
-[Open MCT Web|
+[Open MCT|
   [Dependency injection framework]-->[Platform bundle #1]
   [Dependency injection framework]-->[Platform bundle #2]
   [Dependency injection framework]-->[Plugin bundle #1]
@@ -35,7 +35,7 @@ manner which the framework layer can understand.
 ```
 
 The "dependency injection framework" in this case is
-[AngularJS](https://angularjs.org/). Open MCT Web's framework layer
+[AngularJS](https://angularjs.org/). Open MCT's framework layer
 is really just a thin wrapper over Angular that recognizes the
 concepts of bundles and extensions (as declared in JSON files) and
 registering extensions with Angular. It additionally acts as a
@@ -60,7 +60,7 @@ activities which were performed by the framework component.
 
 ## Application Initialization
 
-The framework component initializes an Open MCT Web application following
+The framework component initializes an Open MCT application following
 a simple sequence of steps.
 
 ```nomnoml
@@ -97,7 +97,7 @@ a simple sequence of steps.
 [Extension]o->[Dependency #3]
 ```
 
-Open MCT Web's architecture relies on a simple premise: Individual units
+Open MCT's architecture relies on a simple premise: Individual units
 (extensions) only have access to the dependencies they declare that they
 need, and they acquire references to these dependencies via dependency
 injection. This has several desirable traits:
@@ -121,17 +121,17 @@ injection. This has several desirable traits:
   the framework.
 
 A drawback to this approach is that it makes it difficult to define
-"the architecture" of Open MCT Web, in terms of describing the specific
+"the architecture" of Open MCT, in terms of describing the specific
 units that interact at run-time. The run-time architecture is determined
 by the framework as the consequence of wiring together dependencies.
 As such, the specific architecture of any given application built on
-Open MCT Web can look very different.
+Open MCT can look very different.
 
 Keeping that in mind, there are a few useful patterns supported by the
 framework that are useful to keep in mind.
 
 The specific service infrastructure provided by the platform is described
-in the [Platform Architecture](Platform.md).
+in the [Platform Architecture](platform.md).
 
 ## Extension Categories
 

docs/src/architecture/index.md

@@ -1,14 +1,14 @@
 # Introduction
 
 The purpose of this document is to familiarize developers with the
-overall architecture of Open MCT Web.
+overall architecture of Open MCT.
 
 The target audience includes:
 
 * _Platform maintainers_: Individuals involved in developing,
-  extending, and maintaing capabilities of the platform.
+  extending, and maintaining capabilities of the platform.
 * _Integration developers_: Individuals tasked with integrated
-  Open MCT Web into a larger system, who need to understand
+  Open MCT into a larger system, who need to understand
   its inner workings sufficiently to complete this integration.
 
 As the focus of this document is on architecture, whenever possible
@@ -17,25 +17,25 @@ omitted. These details may be found in the developer guide.
 
 # Overview
 
-Open MCT Web is client software: It runs in a web browser and
+Open MCT is client software: It runs in a web browser and
 provides a user interface, while communicating with various
 server-side resources through browser APIs.
 
 ```nomnoml
 #direction: right
-[Client|[Browser|[Open MCT Web]->[Browser APIs]]]
+[Client|[Browser|[Open MCT]->[Browser APIs]]]
 [Server|[Web services]]
 [Client]<->[Server]
 ```
 
-While Open MCT Web can be configured to run as a standalone client,
+While Open MCT can be configured to run as a standalone client,
 this is rarely very useful. Instead, it is intended to be used as a
 display and interaction layer for information obtained from a
 variety of back-end services. Doing so requires authoring or utilizing
-adapter plugins which allow Open MCT Web to interact with these services.
+adapter plugins which allow Open MCT to interact with these services.
 
 Typically, the pattern here is to provide a known interface that
-Open MCT Web can utilize, and implement it such that it interacts with
+Open MCT can utilize, and implement it such that it interacts with
 whatever back-end provides the relevant information.
 Examples of back-ends that can be utilized in this fashion include
 databases for the persistence of user-created objects, or sources of
@@ -43,13 +43,13 @@ telemetry data.
 
 ## Software Architecture
 
-The simplest overview of Open MCT Web is to look at it as a "layered"
+The simplest overview of Open MCT is to look at it as a "layered"
 architecture, where each layer more clearly specifies the behavior
 of the software.
 
 ```nomnoml
 #direction: down
-[Open MCT Web|
+[Open MCT|
   [Platform]<->[Application]
   [Framework]->[Application]
   [Framework]->[Platform]
@@ -64,15 +64,13 @@ These layers are:
   established an abstraction by which different software components
   may communicate and/or interact.
 * [_Platform_](platform.md): The platform layer defines the general look,
-  feel, and behavior of Open MCT Web. This includes user-facing components like
+  feel, and behavior of Open MCT. This includes user-facing components like
   Browse mode and Edit mode, as well as underlying elements of the
   information model and the general service infrastructure.
 * _Application_: The application layer defines specific features of
-  an application built on Open MCT Web. This includes adapters to
+  an application built on Open MCT. This includes adapters to
   specific back-ends, new types of things for users to create, and
   new ways of visualizing objects within the system. This layer
-  typically consists of a mix of custom plug-ins to Open MCT Web,
+  typically consists of a mix of custom plug-ins to Open MCT,
   as well as optional features (such as Plot view) included alongside
   the platform.
-
-

docs/src/architecture/platform.md

@@ -1,6 +1,6 @@
 # Overview
 
-The Open MCT Web platform utilizes the [framework layer](Framework.md)
+The Open MCT platform utilizes the [framework layer](framework.md)
 to provide an extensible baseline for applications which includes:
 
 * A common user interface (and user interface paradigm) for dealing with
@@ -16,7 +16,7 @@ building application, the platform adds more specificity by defining
 additional extension types and allowing for integration with back end
 components.
 
-The run-time architecture of an Open MCT Web application can be categorized
+The run-time architecture of an Open MCT application can be categorized
 into certain high-level tiers:
 
 ```nomnoml
@@ -29,7 +29,7 @@ into certain high-level tiers:
 [Browser APIs]->[Back-end]
 ```
 
-Applications built using Open MCT Web may add or configure functionality
+Applications built using Open MCT may add or configure functionality
 in __any of these tiers__.
 
 * _DOM_: The rendered HTML document, composed from HTML templates which
@@ -38,7 +38,7 @@ in __any of these tiers__.
   are initiated from here and invoke behavior in the presentation layer. HTML 
   templates are written in Angular’s template syntax; see the [Angular documentation on templates](https://docs.angularjs.org/guide/templates)​. 
   These describe the page as actually seen by the user. Conceptually, 
-  stylesheets (controlling the look­and­feel of the rendered templates) belong 
+  stylesheets (controlling the look-and-feel of the rendered templates) belong 
   in this grouping as well. 
 * [_Presentation layer_](#presentation-layer): The presentation layer
   is responsible for updating (and providing information to update)
@@ -48,7 +48,7 @@ in __any of these tiers__.
   display.
 * [_Information model_](#information-model): ​Provides a common (within Open MCT 
   Web) set of interfaces for dealing with “things” ­ domain objects ­ within the 
-  system. User­facing concerns in a Open MCT Web application are expressed as 
+  system. User-facing concerns in a Open MCT Web application are expressed as 
   domain objects; examples include folders (used to organize other domain 
   objects), layouts (used to build displays), or telemetry points (used as 
   handles for streams of remote measurements.) These domain objects expose a 
@@ -60,7 +60,7 @@ in __any of these tiers__.
   functionality needed to support the information model. This includes
   exposing underlying sets of extensions and mediating with the
   back-end.
-* _Back-end_: The back-end is out of the scope of Open MCT Web, except
+* _Back-end_: The back-end is out of the scope of Open MCT, except
   for the interfaces which are utilized by adapters participating in the
   service infrastructure. Includes the underlying persistence stores, telemetry 
   streams, and so forth which the Open MCT Web client is being used to interact 
@@ -70,15 +70,15 @@ in __any of these tiers__.
 
 Once the
 [application has been initialized](Framework.md#application-initialization)
-Open MCT Web primarily operates in an event-driven paradigm; various
+Open MCT primarily operates in an event-driven paradigm; various
 events (mouse clicks, timers firing, receiving responses to XHRs) trigger
 the invocation of functions, typically in the presentation layer for
 user actions or in the service infrastructure for server responses.
 
-The "main point of entry" into an initialized Open MCT Web application
+The "main point of entry" into an initialized Open MCT application
 is effectively the
 [route](https://docs.angularjs.org/api/ngRoute/service/$route#example)
-which is associated with the URL used to access Open MCT Web (or a
+which is associated with the URL used to access Open MCT (or a
 default route.) This route will be associated with a template which
 will be displayed; this template will include references to directives
 and controllers which will be interpreted by Angular and used to
@@ -107,11 +107,11 @@ both the information model and the service infrastructure.
 
 # Presentation Layer
 
-The presentation layer of Open MCT Web is responsible for providing
+The presentation layer of Open MCT is responsible for providing
 information to display within templates, and for handling interactions
 which are initiated from templated DOM elements. AngularJS acts as
 an intermediary between the web page as the user sees it, and the
-presentation layer implemented as Open MCT Web extensions.
+presentation layer implemented as Open MCT extensions.
 
 ```nomnoml
 [Presentation Layer|
@@ -143,12 +143,12 @@ to primitives from AngularJS:
   attributes and tags.
 * [_Routes_](https://docs.angularjs.org/api/ngRoute/service/$route#example)
   are used to associate specific URLs (including the fragment identifier)
-  with specific application states. (In Open MCT Web, these are used to
+  with specific application states. (In Open MCT, these are used to
   describe the mode of usage - e.g. browse or edit - as well as to
   identify the object being used.)
 * [_Templates_](https://docs.angularjs.org/guide/templates) are partial
   HTML documents that will be rendered and kept up-to-date by AngularJS.
-  Open MCT Web introduces a custom `mct-include` directive which acts
+  Open MCT introduces a custom `mct-include` directive which acts
   as a wrapper around `ng-include` to allow templates to be referred
   to by symbolic names.
 
@@ -189,10 +189,10 @@ to displaying domain objects.
 ]
 ```
 
-Domain objects are the most fundamental component of Open MCT Web's
+Domain objects are the most fundamental component of Open MCT's
 information model. A domain object is some distinct thing relevant to a
 user's work flow, such as a telemetry channel, display, or similar.
-Open MCT Web is a tool for viewing, browsing, manipulating, and otherwise
+Open MCT is a tool for viewing, browsing, manipulating, and otherwise
 interacting with a graph of domain objects.
 
 A domain object should be conceived of as the union of the following:
@@ -254,7 +254,7 @@ Concrete examples of capabilities which follow this pattern
 
 # Service Infrastructure
 
-Most services exposed by the Open MCT Web platform follow the
+Most services exposed by the Open MCT platform follow the
 [composite services](Framework.md#composite-services) to permit
 a higher degree of flexibility in how a service can be modified
 or customized for specific applications.
@@ -327,7 +327,7 @@ A short summary of the roles of these services:
 [DomainObjectProvider]o-[CapabilityService]
 ```
 
-As domain objects are central to Open MCT Web's information model,
+As domain objects are central to Open MCT's information model,
 acquiring domain objects is equally important.
 
 ```nomnoml
@@ -338,7 +338,7 @@ acquiring domain objects is equally important.
 [<state> Instantiate DomainObject]->[<end> End]
 ```
 
-Open MCT Web includes an implementation of an `ObjectService` which
+Open MCT includes an implementation of an `ObjectService` which
 satisfies this capability by:
 
 * Consulting the [Model Service](#model-service) to acquire domain object
@@ -437,9 +437,9 @@ objects (this allows failures to be recognized and handled in groups.)
 The telemetry service is responsible for acquiring telemetry data.
 
 Notably, the platform does not include any providers for
-`TelemetryService`; applications built on Open MCT Web will need to
+`TelemetryService`; applications built on Open MCT will need to
 implement a provider for this service if they wish to expose telemetry
-data. This is usually the most important step for integrating Open MCT Web
+data. This is usually the most important step for integrating Open MCT
 into an existing telemetry system.
 
 Requests for telemetry data are usually initiated in the
@@ -616,7 +616,7 @@ follows:
   part of an action's extension definition.
 * `CreateActionProvider` provides the various Create actions which
   populate the Create menu. These are driven by the available types,
-  so do not map easily ot extension category `actions`; instead, these
+  so do not map easily to extension category `actions`; instead, these
   are generated after looking up which actions are available from the
   [`TypeService`](#type-service).
 * `ActionAggregator` merges together actions from multiple providers.
@@ -721,6 +721,6 @@ disallow.
 ```
 
 The type service provides metadata about the different types of domain
-objects that exist within an Open MCT Web application. The platform
+objects that exist within an Open MCT application. The platform
 implementation reads these types in from extension category `types`
 and wraps them in a JavaScript interface.

docs/src/design/planning/APIRefactor.md

@@ -1,7 +1,7 @@
 # API Refactoring
 
 This document summarizes a path toward implementing API changes
-from the [API Redesign](../proposals/APIRedesign.md) for Open MCT Web
+from the [API Redesign](../proposals/APIRedesign.md) for Open MCT
 v1.0.0.
 
 # Goals
@@ -161,7 +161,7 @@ be included in a straightforward fashion.
 
 Some goals for this build step:
 
-* Compile (and, preferably, optimize/minify) Open MCT Web
+* Compile (and, preferably, optimize/minify) Open MCT
   sources into a single `.js` file.
   * It is desirable to do the same for HTML sources, but
     may wish to defer this until a subsequent refactoring
@@ -170,7 +170,7 @@ Some goals for this build step:
   derivative projects in a straightforward fashion.
 
 Should also consider which dependency/packaging manager should
-be used by dependent projects to obtain Open MCT Web. Approaches
+be used by dependent projects to obtain Open MCT. Approaches
 include:
 
 1. Plain `npm`. Dependents then declare their dependency with
@@ -203,7 +203,7 @@ to use for asset generation/management and compilation/minification/etc.
 
 ## Step 3. Separate repositories
 
-Refactor existing applications built on Open MCT Web such that they
+Refactor existing applications built on Open MCT such that they
 are no longer forks, but instead separate projects with a dependency
 on the built artifacts from Step 2.
 
@@ -211,7 +211,7 @@ Note that this is achievable already using `bower` (see `warp-bower`
 branch at http://developer.nasa.gov/mct/warp for an example.)
 However, changes involved in switching to an imperative API and
 introducing a build process may change (and should simplify) the
-approach used to utilize Open MCT Web as a dependency, so these
+approach used to utilize Open MCT as a dependency, so these
 changes should be introduced first.
 
 ## Step 4. Design registration API
@@ -287,7 +287,7 @@ or separately in parallel) and should involve a tight cycle of:
    planning should be done to spread out the changes incrementally.
 
 By necessity, these changes may break functionality in applications
-built using Open MCT Web. On a case-by-case basis, should consider
+built using Open MCT. On a case-by-case basis, should consider
 providing temporary "legacy support" to allow downstream updates
 to occur as a separate task; the relevant trade here is between
 waste/effort required to maintain legacy support, versus the
@@ -299,11 +299,11 @@ across several repositories.
 
 Update bundles to remove any usages of legacy support for bundles
 (including that used by dependent projects.) Then, remove legacy
-support from Open MCT Web.
+support from Open MCT.
 
 ## Step 8. Release candidacy
 
-Once API changes are complete, Open MCT Web should enter a release
+Once API changes are complete, Open MCT should enter a release
 candidacy cycle. Important things to look at here:
 
 * Are changes really complete?

docs/src/design/proposals/APIRedesign.md

@@ -1,6 +1,6 @@
 # Overview
 
-The purpose of this document is to review feedback on Open MCT Web's
+The purpose of this document is to review feedback on Open MCT's
 current API and propose improvements to the API, particularly for a
 1.0.0 release.
 
@@ -64,7 +64,7 @@ useful, powerful interfaces.
 ## Developer Intern Feedback
 
 This feedback comes from interns who worked closely with
-Open MCT Web as their primary task over the Summer of 2015.
+Open MCT as their primary task over the Summer of 2015.
 
 ### Developer Intern 1
 
@@ -98,13 +98,13 @@ Worked on bug fixes in the platform and a plugin for search.
   It is hard to figure out what the difference between the various ways of
   dealing with telemetry are. e.g., what is the difference between just
   "Telemetry" and the "Telemetry Service"? There are many
-  "Telemetry Thing"s which seem related, but in an unclear way.
+  "Telemetry Things" which seem related, but in an unclear way.
 
 ### Developer Intern 2
 
 Worked on platform bug fixes and mobile support.
 
-* No guide for the UI and front end for the HTML/CSS part of Open MCT Web.
+* No guide for the UI and front end for the HTML/CSS part of Open MCT.
   Not sure if this is applicable or needed for developers, however would
   be helpful to any front end development
 * Found it difficult to follow the plot controller & subplot
@@ -118,11 +118,11 @@ Worked on platform bug fixes and mobile support.
 ## Plugin Developer Feedback
 
 This feedback comes from developers who have worked on plugins for
-Open MCT Web, but have not worked on the platform.
+Open MCT, but have not worked on the platform.
 
 ### Plugin Developer 1
 
-Used Open MCT Web over the course of several months (on a
+Used Open MCT over the course of several months (on a
 less-than-half-time basis) to develop a
 spectrum visualization plugin.
 
@@ -138,7 +138,7 @@ spectrum visualization plugin.
 
 ### Plugin Developer 2
 
-Used Open MCT Web over the course of several weeks (on a half-time basis)
+Used Open MCT over the course of several weeks (on a half-time basis)
 to develop a tabular visualization plugin.
 
 * Pain points
@@ -180,7 +180,7 @@ to develop a tabular visualization plugin.
       * Add a model property to the bundle.json to take in "Hello World"
         as a parameter and pass through to the controller/view
 
-### Open Source Contributer
+### Open Source Contributor
 
  * [Failures are non-graceful when services are missing.](
    https://github.com/nasa/openmctweb/issues/79)
@@ -197,7 +197,7 @@ to develop a tabular visualization plugin.
 ## Long-term Developer Notes
 
 The following notes are from original platform developer, with long
-term experience using Open MCT Web.
+term experience using Open MCT.
 
 * Bundle mechanism allows for grouping related components across concerns,
   and adding and removing these easily. (e.g. model and view components of
@@ -214,13 +214,13 @@ to an entirely different framework.
 
 We can expect AngularJS 1.x to reach end-of-life reasonably soon thereafter.
 
-Our API is currently a superset of Angular's API, so this directly effects
+Our API is currently a superset of Angular's API, so this directly affects
 our API. Specifically, API changes should be oriented towards removing
 or reducing the Angular dependency.
 
 ### Angular's Role
 
-Angular is Open MCT Web's:
+Angular is Open MCT's:
 
 * Dependency injection framework.
 * Template rendering.
@@ -268,7 +268,7 @@ by experience:
 
 * Feedback from new developers is that Angular was a hindrance to
   training, not a benefit. ("One more thing to learn.") Significant
-  documentation remains necessary for Open MCT Web.
+  documentation remains necessary for Open MCT.
 * Expected enhancements to maintainability will be effectively
   invalidated by an expected Angular end-of-life.
 * Data binding and automatic view updates do save development effort,
@@ -423,7 +423,7 @@ which can help with this, however.
   instead of separate approaches for static and substitutable
   dependencies.
 * Removes need to understand Angular's DI mechanism.
-* Improves useability of documentation (`typeService` is an
+* Improves usability of documentation (`typeService` is an
   instance of `CompositeService` and implements `TypeService`
   so you can easily traverse links in the JSDoc.)
 * Can be used more easily from Web Workers, allowing services
@@ -456,7 +456,7 @@ Instead, propose that:
 For parity with actions, a `View` would be a constructor which
 takes an `ActionContext` as a parameter (with similarly-defined
 properties) and exposes a method to retrieve the HTML elements
-associateed with it.
+associated with it.
 
 The platform would then additionally expose an `AngularView`
 implementation to improve compatibility with existing
@@ -526,7 +526,7 @@ subset of `$http`'s functionality.
 
 ### Detriments
 
-* Increases the number of interfaces in Open MCT Web. (Arguably,
+* Increases the number of interfaces in Open MCT. (Arguably,
   not really, since the same interfaces would exist if exposed
   by Angular.)
 
@@ -574,7 +574,7 @@ This would also allow for "composite bundles" which serve as
 proxies for multiple bundles. The `BundleContext` could contain
 (or later be amended to contain) filtering rules to ignore
 other bundles and so forth (this has been useful for administering
-Open MCT Web in subtly different configurations in the past.)
+Open MCT in subtly different configurations in the past.)
 
 ### Benefits
 
@@ -827,7 +827,7 @@ This could be resolved by:
 
 ## Nomenclature Change
 
-Instead of presenting Open MCT Web as a "framework" or
+Instead of presenting Open MCT as a "framework" or
 "platform", present it as an "extensible application."
 
 This is mostly a change for the developer guide. A
@@ -1040,7 +1040,7 @@ This is a more specific variant of
 * Removes a whole category of API (bundle definitions), reducing
   learning curve associated with the software.
 * Closer to Angular style, reducing disconnect between learning
-  Angular and learning Open MCT Web (reducing burden of having
+  Angular and learning Open MCT (reducing burden of having
   to learn multiple paradigms.)
 * Clarifies "what can be found where" (albeit not perfectly)
   since you can look to module dependencies and follow back from there.
@@ -1124,7 +1124,7 @@ app.config(['actionRegistryProvider', function (arp) {
 ### Detriments
 
 * Slightly increases dependency on Angular; other dependency injectors
-  may not offer comparable ways to specificy dependencies non-globally.
+  may not offer comparable ways to specify dependencies non-globally.
 * Not clear (or will take effort to make clear) which dependencies are
   available for which extensions. Could be mitigated by standardizing
   descriptions of context across actions and views, but that may offer
@@ -1250,7 +1250,7 @@ take. Should not be default behavior.
 
 Proposal | Consensus
 ------|------
-Imperitive component registries | [:+1:](https://github.com/nasa/openmctweb/issues/462)
+Imperative component registries | [:+1:](https://github.com/nasa/openmctweb/issues/462)
 Get rid of "extension category" concept. | [:+1:](https://github.com/nasa/openmctweb/issues/462)
 Reduce number and depth of extension points | :+1:
 Composite services should not be the default | [:question:](https://github.com/nasa/openmctweb/issues/463)

docs/src/design/proposals/APIRedesign_PeteRichards.md

@@ -3,7 +3,7 @@
 **Table of Contents**  *generated with [DocToc](https://github.com/thlorenz/doctoc)*
 
 - [Reducing interface depth (the bundle.json version)](#reducing-interface-depth-the-bundlejson-version)
-  - [Imperitive component registries](#imperitive-component-registries)
+  - [Imperative component registries](#imperative-component-registries)
   - [Get rid of "extension category" concept.](#get-rid-of-extension-category-concept)
   - [Reduce number and depth of extension points](#reduce-number-and-depth-of-extension-points)
   - [Composite services should not be the default](#composite-services-should-not-be-the-default)
@@ -30,11 +30,11 @@
 
 # Reducing interface depth (the bundle.json version)
 
-## Imperitive component registries 
+## Imperative component registries 
 
 Transition component registries to javascript, get rid of bundle.json and bundles.json.  Prescribe a method for application configuration, but allow flexibility in how application configuration is defined.
 
-Register components in an imperitive fashion, see angularApp.factory, angularApp.controller, etc.  Alternatively, implement our own application object with new registries and it's own form of registering objects.
+Register components in an imperative fashion, see angularApp.factory, angularApp.controller, etc.  Alternatively, implement our own application object with new registries and it's own form of registering objects.
 
 ## Get rid of "extension category" concept.
 
@@ -99,7 +99,7 @@ To reduce interface depth, we can replace our own provider and registry patterns
 
 ## More angular: for all services
 
-Increasing our commitment to angular would mean using more of the angular factorys, services, etc, and less of our home grown tools.  We'd implement our services and extension points as angular providers, and make them configurable via app.config.
+Increasing our commitment to angular would mean using more of the angular factories, services, etc, and less of our home grown tools.  We'd implement our services and extension points as angular providers, and make them configurable via app.config.
 
 As an example, registering a specific type of model provider in angular would look like:
 
@@ -126,9 +126,9 @@ Allow developers to use whatever module loading system they'd like to use, while
 
 ## Use gulp or grunt for standard tooling
 
-Using gulp or grunt as a task runner would bring us in line with standard web developer workflows and help standardize rendering, deployment, and packaging.  Additional tools can be added to the workflow at low cost, simplifying the set up of developer environments.
+Using gulp or grunt as a task runner would bring us in line with standard web developer workflows and help standardize rendering, deployment, and packaging.  Additional tools can be added to the workflow at low cost, simplifying the setup of developer environments.
 
-Gulp and grunt provide useful developer tooling such as live reload, automatic scss/less/etc compiliation, and ease of extensibility for standard production build processes.  They're key in decoupling code.
+Gulp and grunt provide useful developer tooling such as live reload, automatic scss/less/etc compilation, and ease of extensibility for standard production build processes.  They're key in decoupling code.
 
 ## Package openmctweb as single versioned file.
 
@@ -145,7 +145,7 @@ Then, if we're using imperative methods for extending the application we can use
 <script>
 // can configure from object
 var myApp = new OpenMCTWeb({
-  persitence: {
+  persistence: {
     providers: [
       {
         type: 'elastic',

docs/src/guide/index.md

@@ -1,4 +1,4 @@
-# Open MCT Web Developer Guide
+# Open MCT Developer Guide
 Victor Woeltjen
 
 [victor.woeltjen@nasa.gov](mailto:victor.woeltjen@nasa.gov)
@@ -18,24 +18,24 @@ April 5, 2016       | 1.2       | Added Mct-table directive | Andrew Henry
 The purpose of this guide is to familiarize software developers with the Open
 MCT Web platform.
 
-## What is Open MCT Web
+## What is Open MCT
-Open MCT Web is a platform for building user interface and display tools,
+Open MCT is a platform for building user interface and display tools,
 developed at the NASA Ames Research Center in collaboration with teams at the
 Jet Propulsion Laboratory. It is written in HTML5, CSS3, and JavaScript, using 
 [AngularJS](http://www.angularjs.org) as a framework. Its intended use is to 
 create single-page web applications which integrate data and behavior from a 
 variety of sources and domains.
 
-Open MCT Web has been developed to support the remote operation of space
+Open MCT has been developed to support the remote operation of space
 vehicles, so some of its features are specific to that task; however, it is
 flexible enough to be adapted to a variety of other application domains where a
 display tool oriented toward browsing, composing, and visualizing would be
 useful.
 
-Open MCT Web provides:
+Open MCT provides:
 
 *  A common user interface paradigm which can be applied to a variety of domains
-and tasks. Open MCT Web is more than a widget toolkit - it provides a standard
+and tasks. Open MCT is more than a widget toolkit - it provides a standard
 tree-on-the-left, view-on-the-right browsing environment which you customize by
 adding new browsable object types, visualizations, and back-end adapters.  
 *  A plugin framework and an extensible API for introducing new application
@@ -44,17 +44,17 @@ features of a variety of types.
 visualizations and infrastructure specific to telemetry display.
 
 ## Client-Server Relationship
-Open MCT Web is client software - it runs entirely in the user's web browser. As
+Open MCT is client software - it runs entirely in the user's web browser. As
 such, it is largely 'server agnostic'; any web server capable of serving files
-from paths is capable of providing Open MCT Web.
+from paths is capable of providing Open MCT.
 
-While Open MCT Web can be configured to run as a standalone client, this is
+While Open MCT can be configured to run as a standalone client, this is
 rarely very useful. Instead, it is intended to be used as a display and
 interaction layer for information obtained from a variety of back-end services.
 Doing so requires authoring or utilizing adapter plugins which allow Open MCT
 Web to interact with these services.
 
-Typically, the pattern here is to provide a known interface that Open MCT Web
+Typically, the pattern here is to provide a known interface that Open MCT
 can utilize, and implement it such that it interacts with whatever back-end
 provides the relevant information. Examples of back-ends that can be utilized in
 this fashion include databases for the persistence of user-created objects, or
@@ -63,52 +63,52 @@ sources of telemetry data.
 See the [Architecture Guide](../architecture/index.md#Overview) for information
 on the client-server relationship.
 
-## Developing with Open MCT Web
+## Developing with Open MCT
-Building applications with Open MCT Web typically means authoring and utilizing
+Building applications with Open MCT typically means authoring and utilizing
 a set of plugins which provide application-specific details about how Open MCT
 Web should behave.
 
 ### Technologies
 
-Open MCT Web sources are written in JavaScript, with a number of configuration
+Open MCT sources are written in JavaScript, with a number of configuration
 files written in JSON. Displayable components are written in HTML5 and CSS3.  
-Open MCT Web is built using [AngularJS](http://www.angularjs.org)  from Google. A
+Open MCT is built using [AngularJS](http://www.angularjs.org)  from Google. A
 good understanding of Angular is recommended for developers working with Open
 MCT Web.
 
 ### Forking
-Open MCT Web does not currently have a single stand-alone artifact that can be
+Open MCT does not currently have a single stand-alone artifact that can be
 used as a library. Instead, the recommended approach for creating a new
-application is to start by forking/branching Open MCT Web, and then adding new
+application is to start by forking/branching Open MCT, and then adding new
-features from there. Put another way, Open MCT Web's source structure is built
+features from there. Put another way, Open MCT's source structure is built
 to serve as a template for specific applications.
 
-Forking in this manner should not require that you edit Open MCT Web's sources.
+Forking in this manner should not require that you edit Open MCT's sources.
 The preferred approach is to create a new directory (peer to `index.html`) for
 the new application, then add new bundles (as described in the Framework
 chapter) within that directory.
 
-To initially clone the Open MCT Web repository:
+To initially clone the Open MCT repository:
 `git clone <repository URL> <local repo directory> -b open-master`
 
-To create a fork to begin working on a new application using Open MCT Web:  
+To create a fork to begin working on a new application using Open MCT:  
 
     cd <local repo directory>  
     git checkout open-master
     git checkout -b <new branch name>
 
-As a convention used internally, applications built using Open MCT Web have
+As a convention used internally, applications built using Open MCT have
 master branch names with an identifying prefix. For instance, if building an
 application called 'Foo', the last statement above would look like:
 
     git checkout -b foo-master
 
-This convention is not enforced or understood by Open MCT Web in any way; it is
+This convention is not enforced or understood by Open MCT in any way; it is
 mentioned here as a more general recommendation.
 
 # Overview
 
-Open MCT Web is implemented as a framework component which manages a set of
+Open MCT is implemented as a framework component which manages a set of
 other components. These components, called _bundles_, act as containers to group
 sets of related functionality; individual units of functionality are expressed
 within these bundles as _extensions_.
@@ -119,7 +119,7 @@ run-time to satisfy these declared dependency. This dependency injection
 approach allows software components which have been authored separately (e.g. as
 plugins) but to collaborate at run-time.
 
-Open MCT Web's framework layer is implemented on top of AngularJS's [dependency
+Open MCT's framework layer is implemented on top of AngularJS's [dependency
 injection mechanism](https://docs.angularjs.org/guide/di)  and is modelled after
 [OSGi](hhttp://www.osgi.org/)  and its [Declarative Services component model](http://wiki.osgi.org/wiki/Declarative_Services). 
 In particular, this is where the term _bundle_ comes from.
@@ -134,7 +134,7 @@ The framework is described in more detail in the [Framework Overview](../archite
 architecture guide.
 
 ### Tiers
-While all bundles in a running Open MCT Web instance are effectively peers, it
+While all bundles in a running Open MCT instance are effectively peers, it
 is useful to think of them as a tiered architecture, where each tier adds more
 specificity to the application.
 ```nomnoml
@@ -152,7 +152,7 @@ It additionally interprets bundle definitions (see explanation below, as well as
 further detail in the Framework chapter.) At this tier, we are at our most
 general: We know only that we are a plugin-based application.
 * __Platform__: Components in the Platform tier describe both the general user
-interface and corresponding developer-facing interfaces of Open MCT Web. This
+interface and corresponding developer-facing interfaces of Open MCT. This
 tier provides the general infrastructure for applications. It is less general
 than the framework tier, insofar as this tier introduces a specific user
 interface paradigm, but it is still non-specific as to what useful features
@@ -160,7 +160,7 @@ will be provided. Although they can be removed or replaced easily, bundles
 provided by the Platform tier generally should not be thought of as optional.
 * __Application__: The application tier consists of components which utilize the
 infrastructure provided by the Platform to provide functionality which will (or
-could) be useful to specific applications built using Open MCT Web. These
+could) be useful to specific applications built using Open MCT. These
 include adapters to specific persistence back-ends (such as ElasticSearch or
 CouchDB) as well as bundles which describe more user-facing features (such as
 _Plot_ views for visualizing time series data, or _Layout_ objects for
@@ -169,20 +169,20 @@ compromising basic application functionality, with the caveat that at least one
 persistence adapter needs to be present.
 * __Plugins__: Conceptually, this tier is not so different from the application
 tier; it consists of bundles describing new features, back-end adapters, that
-are specific to the application being built on Open MCT Web. It is described as
+are specific to the application being built on Open MCT. It is described as
 a separate tier here because it has one important distinction from the
 application tier: It consists of bundles that are not included with the platform
 (either authored anew for the specific application, or obtained from elsewhere.)
 
 Note that bundles in any tier can go off and consult back-end services. In
 practice, this responsibility is handled at the Application and/or Plugin tiers;
-Open MCT Web is built to be server-agnostic, so any back-end is considered an
+Open MCT is built to be server-agnostic, so any back-end is considered an
 application-specific detail.
 
 ## Platform Overview
 
 The "tiered" architecture described in the preceding text describes a way of
-thinking of and categorizing software components of a Open MCT Web application,
+thinking of and categorizing software components of a Open MCT application,
 as well as the framework layer's role in mediating between these components.
 Once the framework layer has wired these software components together, however,
 the application's logical architecture emerges.
@@ -193,7 +193,7 @@ section of the Platform guide
 
 ### Web Services
 
-As mentioned in the Introduction, Open MCT Web is a platform single-page 
+As mentioned in the Introduction, Open MCT is a platform single-page 
 applications which runs entirely in the browser. Most applications will want to 
 additionally interact with server-side resources, to (for example) read 
 telemetry data or store user-created objects. This interaction is handled by 
@@ -206,7 +206,7 @@ individual bundles using APIs which are supported in browser (such as
 [Web Service #2] <- [Web Browser]
 [Web Service #3] <- [Web Browser]
 [<package> Web Browser |
-  [<package> Open MCT Web |
+  [<package> Open MCT |
     [Plugin Bundle #1]-->[Core API]
     [Core API]<--[Plugin Bundle #2]
     [Platform Bundle #1]-->[Core API]
@@ -216,16 +216,16 @@ individual bundles using APIs which are supported in browser (such as
     [Core API]<--[Platform Bundle #5]
     [Core API]<--[Plugin Bundle #3]
   ]
-  [Open MCT Web] ->[Browser APIs]
+  [Open MCT] ->[Browser APIs]
 ]
 ```
 
 This architectural approach ensures a loose coupling between applications built 
-using Open MCT Web and the backends which support them. 
+using Open MCT and the backends which support them. 
  
 ### Glossary 
  
-Certain terms are used throughout Open MCT Web with consistent meanings or 
+Certain terms are used throughout Open MCT with consistent meanings or 
 conventions. Other developer documentation, particularly in-line documentation, 
 may presume an understanding of these terms.
 
@@ -247,7 +247,7 @@ readable description of a thing; usually a single sentence or short paragraph.
 (Most often used in the context of extensions, domain object models, or other 
 similar application-specific objects.) 
 * __domain object__: A meaningful object to the user; a distinct thing in the 
-work support by Open MCT Web. Anything that appears in the left-hand tree is a 
+work support by Open MCT. Anything that appears in the left-hand tree is a 
 domain object. 
 * __extension__: An extension is a unit of functionality exposed to the platform 
 in a declarative fashion by a bundle. The term 'extension category' is used to 
@@ -279,10 +279,10 @@ side-by-side without conflicting.
 
 # Framework
   
-Open MCT Web is built on the [AngularJS framework]( http://www.angularjs.org ). A 
+Open MCT is built on the [AngularJS framework]( http://www.angularjs.org ). A 
 good understanding of that framework is recommended. 
 
-Open MCT Web adds an extra layer on top of AngularJS to (a) generalize its 
+Open MCT adds an extra layer on top of AngularJS to (a) generalize its 
 dependency injection mechanism slightly, particularly to handle many-to-one 
 relationships; and (b) handle script loading. Combined, these features become a 
 plugin mechanism. 
@@ -301,7 +301,7 @@ MCT Web.)
 are collected together in bundles, and may interact with other extensions. 
 
 The framework layer, loaded and initiated from `index.html`, is the main point 
-of entry for an application built on Open MCT Web. It is responsible for wiring 
+of entry for an application built on Open MCT. It is responsible for wiring 
 together the application at run time (much of this responsibility is actually 
 delegated to Angular); at a high-level, the framework does this by proceeding 
 through four stages:
@@ -321,7 +321,7 @@ have been registered.
 
 ## Bundles 
 
-The basic configurable unit of Open MCT Web is the _bundle_. This term has been 
+The basic configurable unit of Open MCT is the _bundle_. This term has been 
 used a bit already; now we'll get to a more formal definition. 
 
 A bundle is a directory which contains:
@@ -329,13 +329,13 @@ A bundle is a directory which contains:
 * A bundle definition; a file named `bundle.json`.
 * Subdirectories for sources, resources, and tests. 
 * Optionally, a `README.md` Markdown file describing its contents (this is not 
-used by Open MCT Web in any way, but it's a helpful convention to follow.)
+used by Open MCT in any way, but it's a helpful convention to follow.)
 
 The bundle definition is the main point of entry for the bundle. The framework 
 looks at this to determine which components need to be loaded and how they 
 interact.
 
-A plugin in Open MCT Web is a bundle. The platform itself is also decomposed 
+A plugin in Open MCT is a bundle. The platform itself is also decomposed 
 into bundles, each of which provides some category of functionality. The 
 difference between a _bundle_ and a _plugin_ is purely a matter of the intended 
 use; a plugin is just a bundle that is meant to be easily added or removed. When 
@@ -356,7 +356,7 @@ For instance, if `bundles.json` contained:
         "example/extensions" 
     ] 
    
-...then the Open MCT Web framework would look for bundle definitions at 
+...then the Open MCT framework would look for bundle definitions at 
 `example/builtins/bundle.json` and `example/extensions/bundle.json`, relative 
 to the path of `index.html`. No other bundles would be loaded.  
 
@@ -425,14 +425,14 @@ tests, as well as a file named `suite.json` describing which files to test.
 Should have the same folder structure as the `src` directory; see the section on 
 automated testing for more information. 
  
-For example, the directory structure for bundle `platform/commonUI/about`  looks 
+For example, the directory structure for bundle `platform/commonUI/dialog`  looks 
 like: 
 
     Platform
       |
       |-commonUI
       |
-      +-about
+      +-dialog
         |
         |-res
         |
@@ -457,7 +457,7 @@ arrays of extension definitions.
 ### General Extensions 
 
 Extensions are intended as a general-purpose mechanism for adding new types of 
-functionality to Open MCT Web. 
+functionality to Open MCT. 
 
 An extension category is registered with Angular under the name of the 
 extension, plus a suffix of two square brackets; so, an Angular service (or, 
@@ -466,7 +466,7 @@ extensions, from all bundles, by including this string (e.g. `types[]` to get
 all type definitions) in a dependency declaration. 
 
 As a convention, extension categories are given single-word, plural nouns for 
-names within Open MCT Web (e.g. `types`.) This convention is not enforced by the 
+names within Open MCT (e.g. `types`.) This convention is not enforced by the 
 platform in any way. For extension categories introduced by external plugins, it 
 is recommended to prefix the extension category with a vendor identifier (or 
 similar) followed by a dot, to avoid collisions. 
@@ -505,7 +505,7 @@ the Angular-supported method for dependency injection is (effectively)
 constructor-style injection; so, both declared dependencies and run-time 
 arguments are competing for space in a constructor's arguments. 
 
-To resolve this, the Open MCT Web framework registers extension instances in a 
+To resolve this, the Open MCT framework registers extension instances in a 
 partially constructed form. That is, the constructor exposed by the extension's 
 implementation is effectively decomposed into two calls; the first takes the 
 dependencies, and returns the constructor in its second form, which takes the 
@@ -549,7 +549,7 @@ sorted according to these conventions when using them.
 ### Angular Built-ins 
 
 Several entities supported Angular are expressed and managed as extensions in 
-Open MCT Web. Specifically, these extension categories are _directives_, 
+Open MCT. Specifically, these extension categories are _directives_, 
 _controllers_, _services_, _constants_, _runs_, and _routes_. 
  
 #### Angular Directives
@@ -592,7 +592,7 @@ property value , which is the constant value that will be registered.
 In some cases, you want to register code to run as soon as the application 
 starts; these can be registered as extensions of the [ runs category](https://docs.angularjs.org/api/ng/type/angular.Module#run ). 
 Implementations registered in this category will be invoked (with their declared 
-dependencies) when the Open MCT Web application first starts. (Note that, in 
+dependencies) when the Open MCT application first starts. (Note that, in 
 this case, the implementation is better thought of as just a function, as 
 opposed to a constructor function.)
 
@@ -627,13 +627,13 @@ providers of the same service (that is, with matching `provides` properties);
 for a decorator, this will be whichever provider, decorator, or aggregator is 
 next in the sequence of decorators. 
 
-Services exposed by the Open MCT Web platform are often declared as composite 
+Services exposed by the Open MCT platform are often declared as composite 
 services, as this form is open for a variety of common modifications. 
 
 # Core API 
 
-Most of Open MCT Web's relevant API is provided and/or mediated by the 
+Most of Open MCT's relevant API is provided and/or mediated by the 
-framework; that is, much of developing for Open MCT Web is a matter of adding 
+framework; that is, much of developing for Open MCT is a matter of adding 
 extensions which access other parts of the platform by means of dependency 
 injection. 
 
@@ -642,9 +642,9 @@ to be passed along by other services.
 
 ## Domain Objects 
 
-Domain objects are the most fundamental component of Open MCT Web's information 
+Domain objects are the most fundamental component of Open MCT's information 
-model. A domain object is some distinct thing relevant to a user's work flow, 
+model. A domain object is some distinct thing relevant to a user's workflow, 
-such as a telemetry channel, display, or similar. Open MCT Web is a tool for 
+such as a telemetry channel, display, or similar. Open MCT is a tool for 
 viewing, browsing, manipulating, and otherwise interacting with a graph of 
 domain objects. 
 
@@ -681,7 +681,7 @@ exposed.
 ### Identifier Syntax
 
 For most purposes, a domain object identifier can be treated as a purely
-symbolic string; these are typically generated by Open MCT Web and plug-ins
+symbolic string; these are typically generated by Open MCT and plug-ins
 should rarely be concerned with its internal structure.
 
 A domain object identifier has one or two parts, separated by a colon.
@@ -724,7 +724,7 @@ exposed it to be removed from its container.
 containing: 
     * `name`: Human-readable name.
     * `description`: Human-readable summary of this action. 
-    * `glyph`: Single character to be displayed in Open MCT Web's icon font set. 
+    * `glyph`: Single character to be displayed in Open MCT's icon font set. 
     * `context`: The context in which this action is being performed (see below)
 
 Action instances are typically obtained via a domain object's `action` 
@@ -740,7 +740,7 @@ dragged object in a drag-and-drop operation.)
 
 ## Telemetry 
 
-Telemetry series data in Open MCT Web is represented by a common interface, and 
+Telemetry series data in Open MCT is represented by a common interface, and 
 packaged in a consistent manner to facilitate passing telemetry updates around 
 multiple visualizations. 
  
@@ -753,7 +753,7 @@ is useful when multiple distinct data sources are in use side-by-side.
 * `key`: A machine-readable identifier for a unique series of telemetry within 
 that source. 
 * _Note: This API is still under development; additional properties, such as 
-start and end time, should be present in future versions of Open MCT Web._ 
+start and end time, should be present in future versions of Open MCT._ 
 
 Additional properties may be included in telemetry requests which have specific 
 interpretations for specific sources.
@@ -777,7 +777,7 @@ not. (Typically, domain values are interpreted as UTC timestamps in milliseconds
 relative to the UNIX epoch.) A series must have at least one domain and one 
 range, and may have more than one.
 
-Telemetry series data in Open MCT Web is expressed via the following 
+Telemetry series data in Open MCT is expressed via the following 
 `TelemetrySeries` interface: 
 
 * `getPointCount()`: Returns the number of unique points/samples in this series. 
@@ -816,7 +816,7 @@ interface:
 * `getName()`: Get the human-readable name for this type. 
 * `getDescription()`: Get a human-readable summary of this type. 
 * `getGlyph()`: Get the single character to be rendered as an icon for this type 
-in Open MCT Web's custom font set. 
+in Open MCT's custom font set. 
 * `getInitialModel()`: Get a domain object model that represents the initial 
 state (before user specification of properties) for domain objects of this type. 
 * `getDefinition()`: Get the extension definition for this type, as a JavaScript 
@@ -832,7 +832,7 @@ an array of `TypeProperty` instances.
 ### Type Features 
 
 Features of a domain object type are expressed as symbolic string identifiers. 
-They are defined in practice by usage; currently, the Open MCT Web platform only 
+They are defined in practice by usage; currently, the Open MCT platform only 
 uses the creation feature to determine which domain object types should appear 
 in the Create menu. 
  
@@ -886,7 +886,7 @@ Categories supported by the platform include:
 * `key`: A machine-readable identifier for this action. 
 * `name`: A human-readable name for this action (e.g. to show in a menu) 
 * `description`: A human-readable summary of the behavior of this action. 
-* `glyph`: A single character which will be rendered in Open MCT Web's custom 
+* `glyph`: A single character which will be rendered in Open MCT's custom 
 font set as an icon for this action.
 
 ## Capabilities Category
@@ -933,15 +933,22 @@ Note that `templateUrl` is not supported for `containers`.
 
 Controls provide options for the `mct-control` directive. 
  
-Six standard control types are included in the forms bundle:
+These standard control types are included in the forms bundle:
 
-* `textfield`: An area to enter plain text.
+* `textfield`: A text input to enter plain text.
+* `numberfield`: A text input to enter numbers.
 * `select`: A drop-down list of options.
 * `checkbox`: A box which may be checked/unchecked.
 * `color`: A color picker.
 * `button`: A button.
 * `datetime`: An input for UTC date/time entry; gives result as a UNIX 
 timestamp, in milliseconds since start of 1970, UTC.
+* `composite`: A control parenting an array of other controls.
+* `menu-button`: A drop-down list of items supporting custom behavior
+on click.
+* `dialog-button`: A button which opens a dialog allowing a single property
+to be edited.
+* `radio`: A radio button.
 
 New controls may be added as extensions of the controls category. Extensions of 
 this category have two properties: 
@@ -981,7 +988,7 @@ Examples of gestures included in the platform are:
 composition.
 * `drop`: For representations that can be drop targets for drag-and-drop 
 composition. 
-* `menu`: For representations that can be used to pop up a context menu. 
+* `menu`: For representations that can be used to popup a context menu. 
  
 Gesture definitions have a property `key` which is used as a machine-readable 
 identifier for the gesture (e.g. `drag`, `drop`, `menu` above.) 
@@ -997,7 +1004,7 @@ of unremoved listeners.
 ## Indicators Category
 
 An indicator is an element that should appear in the status area at the bottom 
-of a running Open MCT Web client instance. 
+of a running Open MCT client instance. 
 
 ### Standard Indicators 
  
@@ -1007,7 +1014,7 @@ provide implementations with the following methods:
 * `getText()`: Provides the human-readable text that will be displayed for this 
 indicator. 
 * `getGlyph()`: Provides a single-character string that will be displayed as an 
-icon in Open MCT Web's custom font set. 
+icon in Open MCT's custom font set. 
 * `getDescription()`: Provides a human-readable summary of the current state of 
 this indicator; will be displayed in a tooltip on hover. 
 * `getClass()`: Get a CSS class that will be applied to this indicator. 
@@ -1033,7 +1040,7 @@ this variety do not need to provide an implementation.
 ## Licenses Category
 
 The extension category `licenses` can be used to add entries into the 'Licensing 
-information' page, reachable from Open MCT Web's About dialog. 
+information' page, reachable from Open MCT's About dialog. 
 
 Licenses may have the following properties, all of which are strings:
 
@@ -1046,11 +1053,11 @@ Licenses may have the following properties, all of which are strings:
 
 ## Policies Category
 
-Policies are used to handle decisions made using Open MCT Web's `policyService`; 
+Policies are used to handle decisions made using Open MCT's `policyService`; 
 examples of these decisions are determining the applicability of certain 
 actions, or checking whether or not a domain object of one type can contain a 
 domain object of a different type. See the section on the Policies for an 
-overview of Open MCT Web's policy model.
+overview of Open MCT's policy model.
 
 A policy's extension definition should include:
 
@@ -1066,7 +1073,7 @@ context)`. The specific types used for `candidate` and `context` vary by policy
 category; in general, what is being asked is 'is this candidate allowed in this 
 context?' This method should return a boolean value. 
 
-Open MCT Web's policy model requires consensus; a policy decision is allowed 
+Open MCT's policy model requires consensus; a policy decision is allowed 
 when and only when all policies choose to allow it. As such, policies should 
 generally be written to reject a certain case, and allow (by returning `true`) 
 anything else. 
@@ -1153,7 +1160,7 @@ For example, the _My Items_ folder is added as an extension of this category.
 
 Extensions of this category should have the following properties:
 
-* `id`: The machine-readable identifier for the domaiwn object being exposed.
+* `id`: The machine-readable identifier for the domain object being exposed.
 * `model`: The model, as a JSON object, for the domain object being exposed. 
 
 ## Stylesheets Category
@@ -1195,7 +1202,7 @@ Templates do not have implementations.
 ## Types Category
 
 The types extension category describes types of domain objects which may 
-appear within Open MCT Web.
+appear within Open MCT.
 
 A type's extension definition should have the following properties:
 
@@ -1203,7 +1210,7 @@ A type's extension definition should have the following properties:
 stored to and matched against the type property of domain object models.
 * `name`: The human-readable name for this domain object type.
 * `description`: A human-readable summary of this domain object type.
-* `glyph`: A single character to be rendered as an icon in Open MCT Web's custom 
+* `glyph`: A single character to be rendered as an icon in Open MCT's custom 
 font set. 
 * `model`: A domain object model, used as the initial state for created domain 
 objects of this type (before any properties are specified.)
@@ -1252,7 +1259,7 @@ utilized via `mct-representation`); additionally:
 
 * `name`: The human-readable name for this view type.
 * description : A human-readable summary of this view type.
-* `glyph`: A single character to be rendered as an icon in Open MCT Web's custom 
+* `glyph`: A single character to be rendered as an icon in Open MCT's custom 
 font set.
 * `type`: Optional; if present, this representation is only applicable for 
 domain object's of this type.
@@ -1294,7 +1301,7 @@ are visible, and what state they manage and/or behavior they invoke.
 
 This set may contain up to two different objects: The  _view proxy_, which is 
 used to make changes to the view as a whole, and the _selected object_, which is 
-used to represent some state within the view. (Future versions of Open MCT Web 
+used to represent some state within the view. (Future versions of Open MCT 
 may support multiple selected objects.) 
 
 The `selection` object made available during Edit mode has the following 
@@ -1330,58 +1337,9 @@ are supported:
 
 # Directives
 
-Open MCT Web defines several Angular directives that are intended for use both 
+Open MCT defines several Angular directives that are intended for use both 
 internally within the platform, and by plugins. 
  
-## Before Unload 
-
-The `mct-before-unload` directive is used to listen for (and prompt for user 
-confirmation) of navigation changes in the browser. This includes reloading, 
-following links out of Open MCT Web, or changing routes. It is used to hook into 
-both `onbeforeunload` event handling as well as route changes from within 
-Angular.
-
-This directive is useable as an attribute. Its value should be an Angular 
-expression. When an action that would trigger an unload and/or route change 
-occurs, this Angular expression is evaluated. Its result should be a message to 
-display to the user to confirm their navigation change; if this expression 
-evaluates to a falsy value, no message will be displayed. 
- 
-## Chart 
-
-The `mct-chart` directive is used to support drawing of simple charts. It is 
-present to support the Plot view, and its functionality is limited to the 
-functionality that is relevant for that view.
-
-This directive is used at the element level and takes one attribute, `draw` 
-which is an Angular expression which will should evaluate to a drawing object. 
-This drawing object should contain the following properties:
-
-* `dimensions`: The size, in logical coordinates, of the chart area. A 
-two-element array or numbers. 
-* `origin`: The position, in logical coordinates, of the lower-left corner of 
-the chart area. A two-element array or numbers. 
-* `lines`: An array of lines (e.g. as a plot line) to draw, where each line is 
-expressed as an object containing: 
-    * `buffer`: A Float32Array containing points in the line, in logical 
-    coordinates, in sequential x,y pairs. 
-    * `color`: The color of the line, as a four-element RGBA array, where 
-    each element is a number in the range of 0.0-1.0. 
-    * `points`: The number of points in the line. 
-* `boxes`: An array of rectangles to draw in the chart area. Each is an object 
-containing: 
-    * `start`: The first corner of the rectangle, as a two-element array of 
-    numbers, in logical coordinates. 
-    * `end`: The opposite corner of the rectangle, as a two-element array of 
-    numbers, in logical coordinates. color : The color of the line, as a 
-    four-element RGBA array, where each element is a number in the range of 
-    0.0-1.0. 
-
-While `mct-chart` is intended to support plots specifically, it does perform 
-some useful management of canvas objects (e.g. choosing between WebGL and Canvas 
-2D APIs for drawing based on browser support) so its usage is recommended when 
-its supported drawing primitives are sufficient for other charting tasks. 
- 
 ## Container 
 
 The `mct-container` is similar to the `mct-include` directive insofar as it allows 
@@ -1449,7 +1407,7 @@ Passed as plain text in the attribute.
 
 ### Form Structure 
 
-Forms in Open MCT Web have a common structure to permit consistent display. A 
+Forms in Open MCT have a common structure to permit consistent display. A 
 form is broken down into sections, which will be displayed in groups; each 
 section is broken down into rows, each of which provides a control for a single 
 property. Input from this form is two-way bound to the object passed via 
@@ -1658,7 +1616,7 @@ by scrolling to the bottom of the table rows.
 
 # Services 
 
-The Open MCT Web platform provides a variety of services which can be retrieved 
+The Open MCT platform provides a variety of services which can be retrieved 
 and utilized via dependency injection. These services fall into two categories: 
 
 * _Composite Services_ are defined by a set of components extensions; plugins may 
@@ -1670,7 +1628,7 @@ utilized by plugins but are not intended to be modified or augmented.
 
 ## Composite Type Services
 
-This section describes the composite services exposed by Open MCT Web, 
+This section describes the composite services exposed by Open MCT, 
 specifically focusing on their interface and contract. 
     
 In many cases, the platform will include a provider for a service which consumes 
@@ -1988,7 +1946,7 @@ The `workerService` may be used to run web workers defined via the
   as a shared worker); if the `key` is unknown, returns `undefined`.
 
 # Models
-Domain object models in Open MCT Web are JavaScript objects describing the 
+Domain object models in Open MCT are JavaScript objects describing the 
 persistent state of the domain objects they describe. Their contents include a 
 mix of commonly understood metadata attributes; attributes which are recognized 
 by and/or determine the applicability of specific extensions; and properties 
@@ -2004,7 +1962,7 @@ MCT Web and can be utilized directly:
 ## Extension-specific Properties 
 
 Other properties of domain object models have specific meaning imposed by other 
-extensions within the Open MCT Web platform. 
+extensions within the Open MCT platform. 
 
 ### Capability-specific Properties 
 
@@ -2288,7 +2246,7 @@ way of its `composition` capability.)
 
 # Policies
 
-Policies are consulted to determine when certain behavior in Open MCT Web is 
+Policies are consulted to determine when certain behavior in Open MCT is 
 allowed. Policy questions are assigned to certain categories, which broadly 
 describe the type of decision being made; within each category, policies have a 
 candidate (the thing which may or may not be allowed) and, optionally, a context 
@@ -2304,22 +2262,19 @@ The platform understands the following policy categories (specifiable as the
 
 * `action`: Determines whether or not a given action is allowable. The candidate 
 argument here is an Action; the context is its action context object.
-* `composition`: Determines whether or not domain objects of a given type are 
+* `composition`: Determines whether or not a given domain object(first argument, `parent`) can contain a candidate child object (second argument, `child`).
-allowed to contain domain objects of another type. The candidate argument here 
-is the container's `Type`; the context argument is the `Type` of the object to be 
-contained.
 * `view`: Determines whether or not a view is applicable for a domain object. 
 The candidate argument is the view's extension definition; the context argument 
 is the `DomainObject` to be viewed.
 
 # Build-Test-Deploy
-Open MCT Web is designed to support a broad variety of build and deployment 
+Open MCT is designed to support a broad variety of build and deployment 
 options. The sources can be deployed in the same directory structure used during 
 development. A few utilities are included to support development processes.
 
 ## Command-line Build
 
-Open MCT Web is built using [`npm`](http://npmjs.com/)
+Open MCT is built using [`npm`](http://npmjs.com/)
 and [`gulp`](http://gulpjs.com/).
 
 To install build dependencies (only needs to be run once):
@@ -2328,15 +2283,15 @@ To install build dependencies (only needs to be run once):
 
 To build:
 
-`npm run prepublish`
+`npm run prepare`
 
 This will compile and minify JavaScript sources, as well as copy over assets.
-The contents of the `dist` folder will contain a runnable Open MCT Web
+The contents of the `dist` folder will contain a runnable Open MCT
 instance (e.g. by starting an HTTP server in that directory), including:
 
-* A `main.js` file containing Open MCT Web source code.
+* A `main.js` file containing Open MCT source code.
 * Various assets in the `example` and `platform` directories.
-* An `index.html` that runs Open MCT Web in its default configuration.
+* An `index.html` that runs Open MCT in its default configuration.
 
 Additional `gulp` tasks are defined in [the gulpfile](gulpfile.js).
 
@@ -2345,7 +2300,7 @@ download build dependencies.
 
 ## Test Suite
 
-Open MCT Web uses [Jasmine 1.3](http://jasmine.github.io/) and
+Open MCT uses [Jasmine 1.3](http://jasmine.github.io/) and
 [Karma](http://karma-runner.github.io) for automated testing.
 
 The test suite is configured to load any scripts ending with `Spec.js` found
@@ -2383,8 +2338,8 @@ information using [Blanket.JS](http://blanketjs.org/) and display this at the
 bottom of the screen. Currently, only statement coverage is displayed.
 
 ## Deployment
-Open MCT Web is built to be flexible in terms of the deployment strategies it 
+Open MCT is built to be flexible in terms of the deployment strategies it 
-supports. In order to run in the browser, Open MCT Web needs:
+supports. In order to run in the browser, Open MCT needs:
 
 1. HTTP access to sources/resources for the framework, platform, and all active 
 bundles.
@@ -2393,13 +2348,13 @@ external services need to support HTTP or some other web-accessible interface,
 like WebSockets.)
 
 Any HTTP server capable of serving flat files is sufficient for the first point. 
-The command-line build also packages Open MCT Web into a `.war` file for easier 
+The command-line build also packages Open MCT into a `.war` file for easier 
 deployment on containers such as Apache Tomcat.
 
 The second point may be less flexible, as it depends upon the specific services 
-to be utilized by Open MCT Web. Because of this, it is often the set of external 
+to be utilized by Open MCT. Because of this, it is often the set of external 
 services (and the manner in which they are exposed) that determine how to deploy 
-Open MCT Web.
+Open MCT.
 
 One important constraint to consider in this context is the browser's same 
 origin policy. If external services are not on the same apparent host and port 
@@ -2416,7 +2371,7 @@ configuration does not create a security vulnerability.
 Examples of deployment strategies (and the conditions under which they make the 
 most sense) include:
 
-* If the external services that Open MCT Web will utilize are all running on 
+* If the external services that Open MCT will utilize are all running on 
 [Apache Tomcat](https://tomcat.apache.org/), then it makes sense to run Open 
 MCT Web from the same Tomcat instance as a separate web application. The 
 `.war` artifact produced by the command line build facilitates this deployment 
@@ -2427,28 +2382,28 @@ hosts/ports, then it may make sense to use a web server that supports proxying,
 such as the [Apache HTTP Server](http://httpd.apache.org/). In this 
 configuration, the HTTP server would be configured to proxy (or reverse proxy) 
 requests at specific paths to the various external services, while providing 
-Open MCT Web as flat files from a different path.
+Open MCT as flat files from a different path.
 * If a single server component is being developed to handle all server-side 
-needs of an Open MCT Web instance, it can make sense to serve Open MCT Web (as 
+needs of an Open MCT instance, it can make sense to serve Open MCT (as 
 flat files) from the same component using an embedded HTTP server such as 
 [Nancy](http://nancyfx.org/).
 * If no external services are needed (or if the 'external services' will just 
 be generating flat files to read) it makes sense to utilize a lightweight flat 
 file HTTP server such as [Lighttpd](http://www.lighttpd.net/). In this 
-configuration, Open MCT Web sources/resources would be placed at one path, while 
+configuration, Open MCT sources/resources would be placed at one path, while 
 the files generated by the external service are placed at another path.
 * If all external services support CORS, it may make sense to have an HTTP 
-server that is solely responsible for making Open MCT Web sources/resources 
+server that is solely responsible for making Open MCT sources/resources 
-available, and to have Open MCT Web contact these external services directly. 
+available, and to have Open MCT contact these external services directly. 
 Again, lightweight HTTP servers such as [Lighttpd](http://www.lighttpd.net/) 
 are useful in this circumstance. The downside of this option is that additional 
 configuration effort is required, both to enable CORS on the external services, 
-and to ensure that Open MCT Web can correctly locate these services.
+and to ensure that Open MCT can correctly locate these services.
 
-Another important consideration is authentication. By design, Open MCT Web does 
+Another important consideration is authentication. By design, Open MCT does 
 not handle user authentication. Instead, this should typically be treated as a 
 deployment-time concern, where authentication is handled by the HTTP server 
-which provides Open MCT Web, or an external access management system.
+which provides Open MCT, or an external access management system.
 
 ### Configuration
 In most of the deployment options above, some level of configuration is likely 
@@ -2456,7 +2411,7 @@ to be needed or desirable to make sure that bundles can reach the external
 services they need to reach. Most commonly this means providing the path or URL 
 to an external service.
 
-Configurable parameters within Open MCT Web are specified via constants 
+Configurable parameters within Open MCT are specified via constants 
 (literally, as extensions of the `constants` category) and accessed via 
 dependency injection by the scripts which need them. Reasonable defaults for 
 these constants are provided in the bundle where they are used. Plugins are 
@@ -2475,7 +2430,7 @@ for error, but is viable if there are a small number of constants to change.
 constants. This is particularly appropriate when multiple configurations (e.g. 
 development, test, production) need to be managed easily; these can be swapped 
 quickly by changing the set of active bundles in bundles.json.
-* Deploy Open MCT Web and its external services in such a fashion that the 
+* Deploy Open MCT and its external services in such a fashion that the 
 default paths to reach external services are all correct.
 
 ### Configuration Constants
@@ -2486,7 +2441,7 @@ The following constants have global significance:
   to be overridden by other bundles, but persistence adapters may wish to
   consume this constant in order to provide persistence for that space.
 
-The following configuration constants are recognized by Open MCT Web bundles:
+The following configuration constants are recognized by Open MCT bundles:
 * Common UI elements - `platform/commonUI/general`
     * `THEME`: A string identifying the current theme symbolically. Individual
     stylesheets (the `stylesheets` extension category) may specify an optional

docs/src/guide/security.md

@@ -0,0 +1,121 @@
+# Security Guide
+
+Open MCT is a rich client with plugin support that executes as a single page
+web application in a browser environment. Security concerns and
+vulnerabilities associated with the web as a platform should be considered
+before deploying Open MCT (or any other web application) for mission or
+production usage.
+
+This document describes several important points to consider when developing
+for or deploying Open MCT securely. Other resources such as
+[Open Web Application Security Project (OWASP)](https://www.owasp.org)
+provide a deeper and more general overview of security for web applications.
+
+
+## Security Model
+
+Open MCT has been architected assuming the following deployment pattern:
+
+* A tagged, tested Open MCT version will be used.
+* Externally authored plugins will be installed.
+* A server will provide persistent storage, telemetry, and other shared data.
+* Authorization, authentication, and auditing will be handled by a server.
+
+
+## Security Procedures
+
+The Open MCT team secures our code base using a combination of code review,
+dependency review, and periodic security reviews. Static analysis performed 
+during automated verification additionally safeguards against common 
+coding errors which may result in vulnerabilities.
+
+
+### Code Review
+
+All contributions are reviewed by internal team members. External
+contributors receive increased scrutiny for security and quality,
+and must sign a licensing agreement.
+
+### Dependency Review
+
+Before integrating third-party dependencies, they are reviewed for security
+and quality, with consideration given to authors and users of these
+dependencies, as well as review of open source code.
+
+### Periodic Security Reviews
+
+Open MCT's code, design, and architecture are periodically reviewed
+(approximately annually) for common security issues, such as the
+[OWASP Top Ten](https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project).
+
+
+## Security Concerns
+
+Certain security concerns deserve special attention when deploying Open MCT,
+or when authoring plugins.
+
+### Identity Spoofing
+
+Open MCT issues calls to web services with the privileges of a logged in user.
+Compromised sources (either for Open MCT itself or a plugin) could
+therefore allow malicious code to execute with those privileges.
+
+To avoid this:
+
+* Serve Open MCT and other scripts over SSL (https rather than http)
+  to prevent man-in-the-middle attacks.
+* Exercise precautions such as security reviews for any plugins or
+  applications built for or with Open MCT to reject malicious changes.
+
+### Information Disclosure
+
+If Open MCT is used to handle or display sensitive data, any components
+(such as adapter plugins) must take care to avoid leaking or disclosing
+this information. For example, avoid sending sensitive data to third-party
+servers or insecure APIs.
+
+### Data Tampering
+
+The web application architecture leaves open the possibility that direct
+calls will be made to back-end services, circumventing Open MCT entirely.
+As such, Open MCT assumes that server components will perform any necessary
+data validation during calls issues to the server.
+
+Additionally, plugins which serialize and write data to the server must
+escape that data to avoid database injection attacks, and similar.
+
+### Repudiation
+
+Open MCT assumes that servers log any relevant interactions and associates
+these with a user identity; the specific user actions taken within the
+application are assumed not to be of concern for auditing.
+
+In the absence of server-side logging, users may disclaim (maliciously,
+mistakenly, or otherwise) actions taken within the system without any
+way to prove otherwise.
+
+If keeping client-level interactions is important, this will need to be
+implemented via a plugin.
+
+### Denial-of-service
+
+Open MCT assumes that server-side components will be insulated against
+denial-of-service attacks. Services should only permit resource-intensive
+tasks to be initiated by known or trusted users.
+
+### Elevation of Privilege
+
+Corollary to the assumption that servers guide against identity spoofing,
+Open MCT assumes that services do not allow a user to act with
+inappropriately escalated privileges. Open MCT cannot protect against
+such escalation; in the clearest case, a malicious actor could interact
+with web services directly to exploit such a vulnerability.
+
+## Additional Reading
+
+The following resources have been used as a basis for identifying potential
+security threats to Open MCT deployments in preparation of this document:
+
+* [STRIDE model](https://www.owasp.org/index.php/Threat_Risk_Modeling#STRIDE)
+* [Attack Surface Analysis Cheat Sheet](https://www.owasp.org/index.php/Attack_Surface_Analysis_Cheat_Sheet)
+* [XSS Prevention Cheat Sheet](https://www.owasp.org/index.php/XSS_(Cross_Site_Scripting)_Prevention_Cheat_Sheet)

docs/src/index.md

@@ -1,35 +1,37 @@
-# Open MCT Web Documentation
+# Open MCT Documentation
 
 ## Overview
 
  Documentation is provided to support the use and development of
- Open MCT Web. It's recommended that before doing
+ Open MCT. It's recommended that before doing
- any development with Open MCT Web you take some time to familiarize yourself 
+ any development with Open MCT you take some time to familiarize yourself
  with the documentation below.
 
- Open MCT Web provides functionality out of the box, but it's also a platform for
+ Open MCT provides functionality out of the box, but it's also a platform for
  building rich mission operations applications based on modern web technology. 
- The platform is configured declaratively, and defines conventions for
+ The platform is configured by plugins which extend the platform at a variety
- building on the provided capabilities by creating modular 'bundles' that 
+ of extension points. The details of how to
- extend the platform at a variety of extension points. The details of how to
  extend the platform are provided in the following documentation.
 
 ## Sections
  
- * The [Architecture Overview](architecture/) describes the concepts used 
- throughout Open MCT Web, and gives a high level overview of the platform's design.
- 
- * The [Developer's Guide](guide/) goes into more detail about how to use the
- platform and the functionality that it provides.
- 
- * The [Tutorials](tutorials/) give examples of extending the platform to add 
- functionality, 
- and integrate with data sources.
- 
  * The [API](api/) document is generated from inline documentation 
  using [JSDoc](http://usejsdoc.org/), and describes the JavaScript objects and
  functions that make up the software platform.
 
- * Finally, the [Development Process](process/) document describes the 
+ * The [Development Process](process/) document describes the
- Open MCT Web software development cycle.
+ Open MCT software development cycle.
 
+## Legacy Documentation
+
+As we transition to a new API, the following documentation for the old API
+(which is supported during the transition) may be useful as well:
+
+ * The [Architecture Overview](architecture/) describes the concepts used
+ throughout Open MCT, and gives a high level overview of the platform's design.
+
+ * The [Developer's Guide](guide/) goes into more detail about how to use the
+ platform and the functionality that it provides.
+
+ * The [Tutorials](https://github.com/nasa/openmct-tutorial) give examples of extending the platform to add
+ functionality, and integrate with data sources.

docs/src/process/cycle.md

@@ -1,6 +1,6 @@
 # Development Cycle
 
-Development of Open MCT Web occurs on an iterative cycle of
+Development of Open MCT occurs on an iterative cycle of
 sprints and releases.
 
 * A _sprint_ is three weeks in duration, and represents a
@@ -73,11 +73,11 @@ acceptance testing (e.g. by resolving any blockers found); any
 resources not needed for this effort should be used to begin work
 for the subsequent sprint.
 
-| Week  | Mon                       | Tue    | Wed | Thu                          | Fri         |
+| Week  | Mon                       | Tue    | Wed | Thu                          | Fri                                   |
-|:-----:|:-------------------------:|:------:|:---:|:----------------------------:|:-----------:|
+|:-----:|:-------------------------:|:------:|:---:|:----------------------------:|:-------------------------------------:|
-| __1__ | Sprint plan               | Tag-up |     |                              |             |
+| __1__ | Sprint plan               | Tag-up |     |                              |                                       |
-| __2__ |                           | Tag-up |     |                              | Code freeze |
+| __2__ |                           | Tag-up |     |                              | Code freeze  and sprint branch        |
-| __3__ | Per-sprint testing        | Triage |     | _Per-sprint testing*_        | Ship        |
+| __3__ | Per-sprint testing        | Triage |     | _Per-sprint testing*_        | Ship and merge sprint branch to master|
 
 * If necessary.
 
@@ -105,14 +105,20 @@ emphasis on testing.
     that team may begin work for that sprint during the
     third week, since testing and blocker resolution is unlikely
     to require all available resources.
+  * Testing success criteria identified per issue (where necessary). This could be in the form of acceptance tests on the issue or detailing performance tests, for example.
 * __Tag-up.__ Check in and status update among development team.
   May amend plan for sprint as-needed.
 * __Code freeze.__ Any new work from this sprint
   (features, bug fixes, enhancements) must be integrated by the
-  end of the second week of the sprint. After code freeze
+  end of the second week of the sprint. After code freeze, a sprint
-  (and until the end of the sprint) the only changes that should be
+  branch will be created (and until the end of the sprint) the only 
-  merged into the master branch should directly address issues
+  changes that should be merged into the sprint branch should 
-  needed to pass acceptance testing.
+  directly address issues needed to pass acceptance testing.
+  During this time, any other feature development will continue to
+  be merged into the master branch for the next sprint.
+* __Sprint branch merge to master.__ After acceptance testing, the sprint branch
+  will be merged back to the master branch. Any code conflicts that 
+  arise will be resolved by the team.
 * [__Per-release Testing.__](testing/plan.md#per-release-testing)
   Structured testing with predefined
   success criteria. No release should ship without passing
@@ -126,8 +132,8 @@ emphasis on testing.
   * [__Testathon.__](testing/plan.md#user-testing)
     Multi-user testing, involving as many users as
     is feasible, plus development team. Open-ended; should verify
-    completed work from this sprint, test exploratorily for
+    completed work from this sprint using the sprint branch, test 
-    regressions, et cetera.
+    exploratorily for regressions, et cetera.
   * [__Long-Duration Test.__](testing/plan.md#long-duration-testing) A
     test to verify that the software remains
     stable after running for longer durations. May include some
@@ -143,7 +149,7 @@ emphasis on testing.
   Subset of Pre-release Testing
   which should be performed before shipping at the end of any
   sprint. Time is allocated for a second round of
-  Pre-release Testing if the first round is not passed.
+  Pre-release Testing if the first round is not passed. Smoke tests collected from issues/PRs
 * __Triage.__ Team reviews issues from acceptance testing and uses
   success criteria to determine whether or not they should block
   release, then formulates a plan to address these issues before

docs/src/process/index.md

@@ -1,6 +1,6 @@
 # Development Process
 
-The process used to develop Open MCT Web is described in the following
+The process used to develop Open MCT is described in the following
 documents:
 
 * The [Development Cycle](cycle.md) describes how and when specific
@@ -9,7 +9,7 @@ documents:
   Open MCT (both semantics and process.)
 * Testing is described in two documents:
   * The [Test Plan](testing/plan.md) summarizes the approaches used
-    to test Open MCT Web.
+    to test Open MCT.
   * The [Test Procedures](testing/procedures.md) document what
     specific tests are performed to verify correctness, and how
     they should be carried out.

docs/src/process/testing/plan.md

@@ -2,7 +2,7 @@
 
 ## Test Levels
 
-Testing for Open MCT Web includes:
+Testing for Open MCT includes:
 
 * _Smoke testing_: Brief, informal testing to verify that no major issues
   or regressions are present in the software, or in specific features of
@@ -19,7 +19,7 @@ Testing for Open MCT Web includes:
 
 Manual, non-rigorous testing of the software and/or specific features
 of interest. Verifies that the software runs and that basic functionality
-is present.
+is present. The outcome of Smoke Testing should be a simplified list of Acceptance Tests which could be executed by another team member with sufficient context.
 
 ### Unit Testing
 
@@ -49,7 +49,7 @@ User testing will focus on the following activities:
 * General "trying to break things."
 
 During user testing, users will
-[report issues](https://github.com/nasa/openmctweb/blob/master/CONTRIBUTING.md#issue-reporting)
+[report issues](https://github.com/nasa/openmct/issues/new/choose)
 as they are encountered.
 
 Desired outcomes of user testing are:
@@ -71,7 +71,7 @@ usage. After twenty-four hours, the software is evaluated for:
   at the start of the test? Is it as responsive?
 
 Any defects or unexpected behavior identified during testing should be
-[reported as issues](https://github.com/nasa/openmctweb/blob/master/CONTRIBUTING.md#issue-reporting)
+[reported as issues](https://github.com/nasa/openmct/issues/new/choose)
 and reviewed for severity.
 
 ## Test Performance
@@ -102,7 +102,7 @@ perform:
 
 * A relevant subset of [_user testing_](procedures.md#user-test-procedures)
   identified by the acting [project manager](../cycle.md#roles).
-* [_Long-duration testing_](procedures.md#long-duration-testng)
+* [_Long-duration testing_](procedures.md#long-duration-testing)
   (specifically, for 24 hours.)
 
 Issues are reported as a product of both forms of testing.
@@ -125,3 +125,22 @@ A release is not closed until both categories have been performed on
 the latest snapshot of the software, _and_ no issues labelled as
 ["blocker" or "critical"](https://github.com/nasa/openmctweb/blob/master/CONTRIBUTING.md#issue-reporting)
 remain open.
+
+### Testathons
+Testathons can be used as a means of performing per-sprint and per-release testing. 
+
+#### Timing
+For per-sprint testing, a testathon is typically performed at the beginning of the third week of a sprint, and again later that week to verify any fixes. For per-release testing, a testathon is typically performed prior to any formal testing processes that are applicable to that release.
+
+#### Process
+
+1. Prior to the scheduled testathon, a list will be compiled of all issues that are closed and unverified.
+2. For each issue, testers should review the associated PR for testing instructions. See the contributing guide for instructions on [pull requests](https://github.com/nasa/openmct/blob/master/CONTRIBUTING.md#merging).
+3. As each issue is verified via testing, any team members testing it should leave a comment on that issue indicating that it has been verified fixed.
+4. If a bug is found that relates to an issue being tested, notes should be included on the associated issue, and the issue should be reopened. Bug notes should include reproduction steps.
+5. For any bugs that are not obviously related to any of the issues under test, a new issue should be created with details about the bug, including reproduction steps. If unsure about whether a bug relates to an issue being tested, just create a new issue.
+6. At the end of the testathon, triage will take place, where all tested issues will be reviewed.
+7. If verified fixed, an issue will remain closed, and will have the “unverified” label removed.
+8. For any bugs found, a severity will be assigned.
+9. A second testathon will be scheduled for later in the week that will aim to address all issues identified as blockers, as well as any other issues scoped by the team during triage.
+10. Any issues that were not tested will remain "unverified" and will be picked up in the next testathon.

docs/src/process/testing/procedures.md

@@ -4,7 +4,7 @@
 
 This document is intended to be used:
 
-* By testers, to verify that Open MCT Web behaves as specified.
+* By testers, to verify that Open MCT behaves as specified.
 * By the development team, to document new test cases and to provide
   guidance on how to author these.
 
@@ -62,7 +62,7 @@ Test cases should be narrow in scope; if a list of steps is excessively
 long (or must be written vaguely to be kept short) it should be broken
 down into multiple tests which reference one another.
 
-All requirements satisfied by Open MCT Web should be verifiable using
+All requirements satisfied by Open MCT should be verifiable using
 one or more test procedures.
 
 ## Glossary

docs/src/process/version.md

@@ -92,47 +92,60 @@ should update (or delegate the task of updating) Open MCT version
 numbers by the following process:
 
 1. Update version number in `package.json`
-  1. Remove `-SNAPSHOT` suffix.
+  1. Checkout branch created for the last sprint that has been successfully tested.
-  2. Verify that resulting version number meets semantic versioning
+  2. Remove a `-SNAPSHOT` suffix from the version in `package.json`.
-     requirements relative to previous stable version. Increment if
+  3. Verify that resulting version number meets semantic versioning
-     necessary.
+     requirements relative to previous stable version. Increment the 
-  3. If version is considered unstable (which may be the case during
+     version number if necessary.
+  4. If version is considered unstable (which may be the case during
      the first three sprints of a release), apply a new suffix per
      [Version Numbering](#version-numbering) guidance above.
 2. Tag the release.
-  1. Commit changes to `package.json` on the `master` branch.
+  1. Commit changes to `package.json` on the new branch created in 
+     the previous step.
      The commit message should reference the sprint being closed,
      preferably by a URL reference to the associated Milestone in
      GitHub.
   2. Verify that build still completes, that application passes
      smoke-testing, and that only differences from tested versions
      are the changes to version number above.
-  3. Push the `master` branch.
+  3. Push the new branch.
   4. Tag this commit with the version number, prepending the letter "v".
      (e.g. `git tag v0.9.3-alpha`)
   5. Push the tag to GitHub. (e.g. `git push origin v0.9.3-alpha`).
 3. Upload a release archive.
-  1. Run `npm pack` to generate the archive.
+  1. Use the [GitHub release interface](https://github.com/nasa/openmct/releases)
-  2. Use the [GitHub release interface](https://github.com/nasa/openmct/releases)
      to draft a new release.
-  3. Choose the existing tag for the new version (created and pushed above.)
+  2. Choose the existing tag for the new version (created and pushed above.)
      Enter the tag name as the release name as well; see existing releases
-     for examples.
+     for examples. (e.g. `Open MCT v0.9.3-alpha`)
-  4. Attach the release archive.
+  3. Designate the release as a "pre-release" as appropriate (for instance,
-  5. Designate the release as a "pre-release" as appropriate (for instance,
      when the version number has been suffixed as unstable, or when
      the version number is below 1.0.0.)
-4. Restore snapshot status in `package.json`
+  4. Add release notes including any breaking changes, enhancements, 
-  1. Remove any suffix from the version number, or increment the
+     bug fixes with solutions in brief.
-     _patch_ version if there is no suffix.
+  5. Publish the release.
-  2. Append a `-SNAPSHOT` suffix.
+4. Publish the release to npm
-  3. Commit changes to `package.json` on the `master` branch.
+  1. Login to npm
+  2. Checkout the tag created in the previous step.
+  3. In `package.json` change package to be public (private: false)
+  4. Test the package before publishing by doing `npm publish --dry-run` 
+     if necessary.
+  5. Publish the package to the npmjs registry (e.g. `npm publish --access public`) 
+     NOTE: Use the `--tag unstable` flag to the npm publishj if this is a prerelease.
+  6. Confirm the package has been published (e.g. `https://www.npmjs.com/package/openmct`)
+5. Update snapshot status in `package.json`
+  1. Create a new branch off the `master` branch.
+  2. Remove any suffix from the version number, 
+     or increment the _patch_ version if there is no suffix.
+  3. Append a `-SNAPSHOT` suffix.
+  4. Commit changes to `package.json` on the `master` branch.
      The commit message should reference the sprint being opened,
      preferably by a URL reference to the associated Milestone in
      GitHub.
-  4. Verify that build still completes, that application passes
+  5. Verify that build still completes, that application passes
      smoke-testing.
-  5. Push the `master` branch.
+  6. Create a PR to be merged into the `master` branch.
 
 Projects dependent on Open MCT being co-developed by the Open MCT
 team should follow a similar process, except that they should

e2e/.eslintrc.js

@@ -0,0 +1,4 @@
+/* eslint-disable no-undef */
+module.exports = {
+    "extends": ["plugin:playwright/playwright-test"]
+};

e2e/playwright-ci.config.js

@@ -0,0 +1,33 @@
+/* eslint-disable no-undef */
+// playwright.config.js
+// @ts-check
+
+/** @type {import('@playwright/test').PlaywrightTestConfig} */
+const config = {
+    retries: 2,
+    testDir: 'tests',
+    timeout: 90 * 1000,
+    webServer: {
+        command: 'npm run start',
+        port: 8080,
+        timeout: 200 * 1000,
+        reuseExistingServer: !process.env.CI
+    },
+    workers: 2, //Limit to 2 for CircleCI Agent
+    use: {
+        browserName: "chromium",
+        baseURL: 'http://localhost:8080/',
+        headless: true,
+        ignoreHTTPSErrors: true,
+        screenshot: 'on',
+        trace: 'on',
+        video: 'on'
+    },
+    reporter: [
+        ['list'],
+        ['junit', { outputFile: 'test-results/results.xml' }],
+        ['allure-playwright']
+    ]
+};
+
+module.exports = config;

e2e/playwright-local.config.js

@@ -0,0 +1,31 @@
+/* eslint-disable no-undef */
+// playwright.config.js
+// @ts-check
+
+/** @type {import('@playwright/test').PlaywrightTestConfig} */
+const config = {
+    retries: 0,
+    testDir: 'tests',
+    timeout: 30 * 1000,
+    webServer: {
+        command: 'npm run start',
+        port: 8080,
+        timeout: 120 * 1000,
+        reuseExistingServer: !process.env.CI
+    },
+    use: {
+        browserName: "chromium",
+        baseURL: 'http://localhost:8080/',
+        headless: false,
+        ignoreHTTPSErrors: true,
+        screenshot: 'on',
+        trace: 'on',
+        video: 'on'
+    },
+    reporter: [
+        ['list'],
+        ['allure-playwright']
+    ]
+};
+
+module.exports = config;

e2e/playwright-visual.config.js

@@ -0,0 +1,33 @@
+/* eslint-disable no-undef */
+// playwright.config.js
+// @ts-check
+
+/** @type {import('@playwright/test').PlaywrightTestConfig} */
+const config = {
+    retries: 0,
+    testDir: 'tests',
+    timeout: 90 * 1000,
+    workers: 1,
+    webServer: {
+        command: 'npm run start',
+        port: 8080,
+        timeout: 200 * 1000,
+        reuseExistingServer: !process.env.CI
+    },
+    use: {
+        browserName: "chromium",
+        baseURL: 'http://localhost:8080/',
+        headless: true,
+        ignoreHTTPSErrors: true,
+        screenshot: 'on',
+        trace: 'off',
+        video: 'on'
+    },
+    reporter: [
+        ['list'],
+        ['junit', { outputFile: 'test-results/results.xml' }],
+        ['allure-playwright']
+    ]
+};
+
+module.exports = config;

e2e/tests/plugins/condition/condition.e2e.spec.js

@@ -0,0 +1,48 @@
+/*****************************************************************************
+ * Open MCT, Copyright (c) 2014-2021, United States Government
+ * as represented by the Administrator of the National Aeronautics and Space
+ * Administration. All rights reserved.
+ *
+ * Open MCT is licensed under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0.
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+ * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+ * License for the specific language governing permissions and limitations
+ * under the License.
+ *
+ * Open MCT includes source code licensed under additional open source
+ * licenses. See the Open Source Licenses file (LICENSES.md) included with
+ * this source code distribution or the Licensing information page available
+ * at runtime from the About dialog for additional information.
+ *****************************************************************************/
+
+/*
+This test suite is dedicated to tests which verify the basic operations surrounding conditionSets.
+*/
+
+const { test, expect } = require('@playwright/test');
+
+test.describe('condition set', () => {
+    test('create new button `condition set` creates new condition object', async ({ page }) => {
+        //Go to baseURL
+        await page.goto('/', { waitUntil: 'networkidle' });
+
+        //Click the Create button
+        await page.click('button:has-text("Create")');
+
+        // Click text=Condition Set
+        await page.click('text=Condition Set');
+
+        // Click text=OK
+        await Promise.all([
+            page.waitForNavigation(/*{ url: 'http://localhost:8080/#/browse/mine/dab945d4-5a84-480e-8180-222b4aa730fa?tc.mode=fixed&tc.startBound=1639696164435&tc.endBound=1639697964435&tc.timeSystem=utc&view=conditionSet.view' }*/),
+            page.click('text=OK')
+        ]);
+
+        await expect(page.locator('.l-browse-bar__object-name')).toContainText('Unnamed Condition Set');
+    });
+});

e2e/tests/smoke.spec.js

@@ -0,0 +1,49 @@
+/*****************************************************************************
+ * Open MCT, Copyright (c) 2014-2021, United States Government
+ * as represented by the Administrator of the National Aeronautics and Space
+ * Administration. All rights reserved.
+ *
+ * Open MCT is licensed under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0.
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+ * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+ * License for the specific language governing permissions and limitations
+ * under the License.
+ *
+ * Open MCT includes source code licensed under additional open source
+ * licenses. See the Open Source Licenses file (LICENSES.md) included with
+ * this source code distribution or the Licensing information page available
+ * at runtime from the About dialog for additional information.
+ *****************************************************************************/
+
+/*
+This test suite is dedicated to tests which can quickly verify that any openmct installation is
+operable and that any type of testing can proceed.
+
+Ideally, smoke tests should make zero assumptions about how and where they are run. This makes them
+more resilient to change and therefor a better indicator of failure. Smoke tests will also run quickly
+as they cover a very "thin surface" of functionality.
+
+When deciding between authoring new smoke tests or functional tests, ask yourself "would I feel
+comfortable running this test during a live mission?" Avoid creating or deleting Domain Objects.
+Make no assumptions about the order that elements appear in the DOM.
+*/
+
+const { test, expect } = require('@playwright/test');
+
+test('Verify that the create button appears and that the Folder Domain Object is available for selection', async ({ page }) => {
+
+    //Go to baseURL
+    await page.goto('/', { waitUntil: 'networkidle' });
+
+    //Click the Create button
+    await page.click('button:has-text("Create")');
+
+    // Verify that Create Folder appears in the dropdown
+    const locator = page.locator(':nth-match(:text("Folder"), 2)');
+    await expect(locator).toBeEnabled();
+});

e2e/tests/visual/default.spec.js

@@ -0,0 +1,113 @@
+/*****************************************************************************
+ * Open MCT, Copyright (c) 2014-2021, United States Government
+ * as represented by the Administrator of the National Aeronautics and Space
+ * Administration. All rights reserved.
+ *
+ * Open MCT is licensed under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0.
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+ * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+ * License for the specific language governing permissions and limitations
+ * under the License.
+ *
+ * Open MCT includes source code licensed under additional open source
+ * licenses. See the Open Source Licenses file (LICENSES.md) included with
+ * this source code distribution or the Licensing information page available
+ * at runtime from the About dialog for additional information.
+ *****************************************************************************/
+
+/*
+Collection of Visual Tests set to run in a default context. The tests within this suite
+are only meant to run against openmct's app.js started by `npm run start` within the 
+`./e2e/playwright-visual.config.js` file.
+
+These should only use functional expect statements to verify assumptions about the state 
+in a test and not for functional verification of correctness. Visual tests are not supposed
+to "fail" on assertions. Instead, they should be used to detect changes between builds or branches.
+
+Note: Larger testsuite sizes are OK due to the setup time associated with these tests. 
+*/
+
+const { test, expect } = require('@playwright/test');
+const percySnapshot = require('@percy/playwright');
+const path = require('path');
+const sinon = require('sinon');
+
+const VISUAL_GRACE_PERIOD = 5 * 1000; //Lets the application "simmer" before the snapshot is taken
+
+// Snippet from https://github.com/microsoft/playwright/issues/6347#issuecomment-965887758
+// Will replace with cy.clock() equivalent
+test.beforeEach(async ({ context }) => {
+    await context.addInitScript({
+        // eslint-disable-next-line no-undef
+        path: path.join(__dirname, '../../..', './node_modules/sinon/pkg/sinon.js')
+    });
+    await context.addInitScript(() => {
+        window.__clock = sinon.useFakeTimers(); //Set browser clock to UNIX Epoch
+    });
+});
+
+test('Visual - Root and About', async ({ page }) => {
+    // Go to baseURL
+    await page.goto('/', { waitUntil: 'networkidle' });
+
+    // Verify that Create button is actionable
+    const createButtonLocator = page.locator('button:has-text("Create")');
+    await expect(createButtonLocator).toBeEnabled();
+
+    // Take a snapshot of the Dashboard
+    await page.waitForTimeout(VISUAL_GRACE_PERIOD);
+    await percySnapshot(page, 'Root');
+
+    // Click About button
+    await page.click('.l-shell__app-logo');
+
+    // Modify the Build information in 'about' to be consistent run-over-run
+    const versionInformationLocator = page.locator('ul.t-info.l-info.s-info');
+    await expect(versionInformationLocator).toBeEnabled();
+    await versionInformationLocator.evaluate(node => node.innerHTML = '<li>Version: visual-snapshot</li> <li>Build Date: Mon Nov 15 2021 08:07:51 GMT-0800 (Pacific Standard Time)</li> <li>Revision: 93049cdbc6c047697ca204893db9603b864b8c9f</li> <li>Branch: master</li>');
+
+    // Take a snapshot of the About modal
+    await page.waitForTimeout(VISUAL_GRACE_PERIOD);
+    await percySnapshot(page, 'About');
+});
+
+test('Visual - Default Condition Set', async ({ page }) => {
+    //Go to baseURL
+    await page.goto('/', { waitUntil: 'networkidle' });
+
+    //Click the Create button
+    await page.click('button:has-text("Create")');
+
+    // Click text=Condition Set
+    await page.click('text=Condition Set');
+
+    // Click text=OK
+    await page.click('text=OK');
+
+    // Take a snapshot of the newly created Condition Set object
+    await page.waitForTimeout(VISUAL_GRACE_PERIOD);
+    await percySnapshot(page, 'Default Condition Set');
+});
+
+test('Visual - Default Condition Widget', async ({ page }) => {
+    //Go to baseURL
+    await page.goto('/', { waitUntil: 'networkidle' });
+
+    //Click the Create button
+    await page.click('button:has-text("Create")');
+
+    // Click text=Condition Widget
+    await page.click('text=Condition Widget');
+
+    // Click text=OK
+    await page.click('text=OK');
+
+    // Take a snapshot of the newly created Condition Widget object
+    await page.waitForTimeout(VISUAL_GRACE_PERIOD);
+    await percySnapshot(page, 'Default Condition Widget');
+});

example/README.md

@@ -1,2 +1,2 @@
 This directory is for example bundles, which are intended to illustrate 
-how to author new software components using Open MCT Web.
+how to author new software components using Open MCT.

example/builtins/README.md

@@ -1,8 +0,0 @@
-This bundle is intended to serve as an example of registering
-extensions which are mapped directly to built-in Angular features.
-
-These are:
-* Controllers
-* Directives
-* Routes
-* Services

example/builtins/bundle.js

@@ -1,74 +0,0 @@
-/*****************************************************************************
- * Open MCT Web, Copyright (c) 2014-2015, United States Government
- * as represented by the Administrator of the National Aeronautics and Space
- * Administration. All rights reserved.
- *
- * Open MCT Web is licensed under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- * http://www.apache.org/licenses/LICENSE-2.0.
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
- * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
- * License for the specific language governing permissions and limitations
- * under the License.
- *
- * Open MCT Web includes source code licensed under additional open source
- * licenses. See the Open Source Licenses file (LICENSES.md) included with
- * this source code distribution or the Licensing information page available
- * at runtime from the About dialog for additional information.
- *****************************************************************************/
-/*global define*/
-
-define([
-    "./src/ExampleController",
-    "./src/ExampleDirective",
-    "./src/ExampleService",
-    'legacyRegistry'
-], function (
-    ExampleController,
-    ExampleDirective,
-    ExampleService,
-    legacyRegistry
-) {
-    "use strict";
-
-    legacyRegistry.register("example/builtins", {
-        "name": "Angular Built-ins Example",
-        "description": "Example showing how to declare extensions with built-in support from Angular.",
-        "sources": "src",
-        "extensions": {
-            "controllers": [
-                {
-                    "key": "ExampleController",
-                    "implementation": ExampleController,
-                    "depends": [
-                        "$scope",
-                        "exampleService"
-                    ]
-                }
-            ],
-            "directives": [
-                {
-                    "key": "exampleDirective",
-                    "implementation": ExampleDirective,
-                    "depends": [
-                        "examples[]"
-                    ]
-                }
-            ],
-            "routes": [
-                {
-                    "templateUrl": "templates/example.html"
-                }
-            ],
-            "services": [
-                {
-                    "key": "exampleService",
-                    "implementation": ExampleService
-                }
-            ]
-        }
-    });
-});

example/builtins/res/templates/example.html

@@ -1,24 +0,0 @@
-<!--
- Open MCT Web, Copyright (c) 2014-2015, United States Government
- as represented by the Administrator of the National Aeronautics and Space
- Administration. All rights reserved.
-
- Open MCT Web is licensed under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
- http://www.apache.org/licenses/LICENSE-2.0.
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
- WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
- License for the specific language governing permissions and limitations
- under the License.
-
- Open MCT Web includes source code licensed under additional open source
- licenses. See the Open Source Licenses file (LICENSES.md) included with
- this source code distribution or the Licensing information page available
- at runtime from the About dialog for additional information.
--->
-<p>Hello, world! I am the default route.</p>
-<p ng-controller="ExampleController">My controller has told me: "{{phrase}}"</p>
-<span example-directive></span>

example/builtins/src/ExampleDirective.js

@@ -1,66 +0,0 @@
-/*****************************************************************************
- * Open MCT Web, Copyright (c) 2014-2015, United States Government
- * as represented by the Administrator of the National Aeronautics and Space
- * Administration. All rights reserved.
- *
- * Open MCT Web is licensed under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- * http://www.apache.org/licenses/LICENSE-2.0.
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
- * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
- * License for the specific language governing permissions and limitations
- * under the License.
- *
- * Open MCT Web includes source code licensed under additional open source
- * licenses. See the Open Source Licenses file (LICENSES.md) included with
- * this source code distribution or the Licensing information page available
- * at runtime from the About dialog for additional information.
- *****************************************************************************/
-/*global define,Promise*/
-
-/**
- * Module defining ExampleDirective. Created by vwoeltje on 11/4/14.
- */
-define(
-    [],
-    function () {
-        "use strict";
-
-        var HAS_EXTENSIONS = "A directive loaded these message from " +
-                    "example extensions.",
-            NO_EXTENSIONS = "A directive tried to load example extensions," +
-                    " but found none.",
-            MESSAGE = "I heard this from my partial constructor.";
-
-        /**
-         *
-         * @constructor
-         */
-        function ExampleDirective(examples) {
-            // Build up a template from example extensions
-            var template = examples.length > 0 ?
-                    HAS_EXTENSIONS : NO_EXTENSIONS;
-
-            template += "<ul>";
-            examples.forEach(function (E) {
-                template += "<li>";
-                if (typeof E === 'function') {
-                    template += (new E(MESSAGE)).getText();
-                } else {
-                    template += E.text;
-                }
-                template += "</li>";
-            });
-            template += "</ul>";
-
-            return {
-                template: template
-            };
-        }
-
-        return ExampleDirective;
-    }
-);

example/composite/bundle.js

@@ -1,82 +0,0 @@
-/*****************************************************************************
- * Open MCT Web, Copyright (c) 2014-2015, United States Government
- * as represented by the Administrator of the National Aeronautics and Space
- * Administration. All rights reserved.
- *
- * Open MCT Web is licensed under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- * http://www.apache.org/licenses/LICENSE-2.0.
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
- * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
- * License for the specific language governing permissions and limitations
- * under the License.
- *
- * Open MCT Web includes source code licensed under additional open source
- * licenses. See the Open Source Licenses file (LICENSES.md) included with
- * this source code distribution or the Licensing information page available
- * at runtime from the About dialog for additional information.
- *****************************************************************************/
-/*global define*/
-
-define([
-    "./src/SomeProvider",
-    "./src/SomeOtherProvider",
-    "./src/SomeDecorator",
-    "./src/SomeOtherDecorator",
-    "./src/SomeAggregator",
-    "./src/SomeOtherExample",
-    'legacyRegistry'
-], function (
-    SomeProvider,
-    SomeOtherProvider,
-    SomeDecorator,
-    SomeOtherDecorator,
-    SomeAggregator,
-    SomeOtherExample,
-    legacyRegistry
-) {
-    "use strict";
-
-    legacyRegistry.register("example/composite", {
-        "extensions": {
-            "components": [
-                {
-                    "implementation": SomeProvider,
-                    "provides": "someService",
-                    "type": "provider"
-                },
-                {
-                    "implementation": SomeOtherProvider,
-                    "provides": "someService",
-                    "type": "provider"
-                },
-                {
-                    "implementation": SomeDecorator,
-                    "provides": "someService",
-                    "type": "decorator"
-                },
-                {
-                    "implementation": SomeOtherDecorator,
-                    "provides": "someService",
-                    "type": "decorator"
-                },
-                {
-                    "implementation": SomeAggregator,
-                    "provides": "someService",
-                    "type": "aggregator"
-                }
-            ],
-            "examples": [
-                {
-                    "implementation": SomeOtherExample,
-                    "depends": [
-                        "someService"
-                    ]
-                }
-            ]
-        }
-    });
-});

example/composite/src/SomeOtherDecorator.js

@@ -1,48 +0,0 @@
-/*****************************************************************************
- * Open MCT Web, Copyright (c) 2014-2015, United States Government
- * as represented by the Administrator of the National Aeronautics and Space
- * Administration. All rights reserved.
- *
- * Open MCT Web is licensed under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- * http://www.apache.org/licenses/LICENSE-2.0.
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
- * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
- * License for the specific language governing permissions and limitations
- * under the License.
- *
- * Open MCT Web includes source code licensed under additional open source
- * licenses. See the Open Source Licenses file (LICENSES.md) included with
- * this source code distribution or the Licensing information page available
- * at runtime from the About dialog for additional information.
- *****************************************************************************/
-/*global define,Promise*/
-
-/**
- * Module defining SomeOtherDecorator. Created by vwoeltje on 11/5/14.
- */
-define(
-    [],
-    function () {
-        "use strict";
-
-        /**
-         *
-         * @constructor
-         */
-        function SomeOtherDecorator(someProvider) {
-            return {
-                getMessages: function () {
-                    return someProvider.getMessages().map(function (msg) {
-                        return msg + "...";
-                    });
-                }
-            };
-        }
-
-        return SomeOtherDecorator;
-    }
-);

example/composite/src/SomeOtherProvider.js

@@ -1,48 +0,0 @@
-/*****************************************************************************
- * Open MCT Web, Copyright (c) 2014-2015, United States Government
- * as represented by the Administrator of the National Aeronautics and Space
- * Administration. All rights reserved.
- *
- * Open MCT Web is licensed under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- * http://www.apache.org/licenses/LICENSE-2.0.
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
- * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
- * License for the specific language governing permissions and limitations
- * under the License.
- *
- * Open MCT Web includes source code licensed under additional open source
- * licenses. See the Open Source Licenses file (LICENSES.md) included with
- * this source code distribution or the Licensing information page available
- * at runtime from the About dialog for additional information.
- *****************************************************************************/
-/*global define,Promise*/
-
-/**
- * Module defining SomeOtherProvider. Created by vwoeltje on 11/5/14.
- */
-define(
-    [],
-    function () {
-        "use strict";
-
-        /**
-         *
-         * @constructor
-         */
-        function SomeOtherProvider() {
-            return {
-                getMessages: function () {
-                    return [
-                        "I am a message from some other provider."
-                    ];
-                }
-            };
-        }
-
-        return SomeOtherProvider;
-    }
-);

example/eventGenerator/bundle.js

@@ -1,9 +1,9 @@
 /*****************************************************************************
- * Open MCT Web, Copyright (c) 2014-2015, United States Government
+ * Open MCT, Copyright (c) 2014-2021, United States Government
  * as represented by the Administrator of the National Aeronautics and Space
  * Administration. All rights reserved.
  *
- * Open MCT Web is licensed under the Apache License, Version 2.0 (the
+ * Open MCT is licensed under the Apache License, Version 2.0 (the
  * "License"); you may not use this file except in compliance with the License.
  * You may obtain a copy of the License at
  * http://www.apache.org/licenses/LICENSE-2.0.
@@ -14,67 +14,67 @@
  * License for the specific language governing permissions and limitations
  * under the License.
  *
- * Open MCT Web includes source code licensed under additional open source
+ * Open MCT includes source code licensed under additional open source
  * licenses. See the Open Source Licenses file (LICENSES.md) included with
  * this source code distribution or the Licensing information page available
  * at runtime from the About dialog for additional information.
  *****************************************************************************/
-/*global define*/
 
 define([
-    "./src/EventTelemetryProvider",
+    "./src/EventTelemetryProvider"
-    'legacyRegistry'
 ], function (
-    EventTelemetryProvider,
+    EventTelemetryProvider
-    legacyRegistry
 ) {
     "use strict";
 
-    legacyRegistry.register("example/eventGenerator", {
+    return {
-        "name": "Event Message Generator",
+        name: "example/eventGenerator",
-        "description": "For development use. Creates sample event message data that mimics a live data stream.",
+        definition: {
-        "extensions": {
+            "name": "Event Message Generator",
-            "components": [
+            "description": "For development use. Creates sample event message data that mimics a live data stream.",
-                {
+            "extensions": {
-                    "implementation": EventTelemetryProvider,
+                "components": [
-                    "type": "provider",
+                    {
-                    "provides": "telemetryService",
+                        "implementation": EventTelemetryProvider,
-                    "depends": [
+                        "type": "provider",
-                        "$q",
+                        "provides": "telemetryService",
-                        "$timeout"
+                        "depends": [
-                    ]
+                            "$q",
-                }
+                            "$timeout"
-            ],
-            "types": [
-                {
-                    "key": "eventGenerator",
-                    "name": "Event Message Generator",
-                    "glyph": "\u0066",
-                    "description": "For development use. Creates sample event message data that mimics a live data stream.",
-                    "priority": 10,
-                    "features": "creation",
-                    "model": {
-                        "telemetry": {}
-                    },
-                    "telemetry": {
-                        "source": "eventGenerator",
-                        "domains": [
-                            {
-                                "key": "time",
-                                "name": "Time",
-                                "format": "utc"
-                            }
-                        ],
-                        "ranges": [
-                            {
-                                "key": "message",
-                                "name": "Message",
-                                "format": "string"
-                            }
                         ]
                     }
-                }
+                ],
-            ]
+                "types": [
+                    {
+                        "key": "eventGenerator",
+                        "name": "Event Message Generator",
+                        "cssClass": "icon-generator-events",
+                        "description": "For development use. Creates sample event message data that mimics a live data stream.",
+                        "priority": 10,
+                        "features": "creation",
+                        "model": {
+                            "telemetry": {}
+                        },
+                        "telemetry": {
+                            "source": "eventGenerator",
+                            "domains": [
+                                {
+                                    "key": "utc",
+                                    "name": "Timestamp",
+                                    "format": "utc"
+                                }
+                            ],
+                            "ranges": [
+                                {
+                                    "key": "message",
+                                    "name": "Message",
+                                    "format": "string"
+                                }
+                            ]
+                        }
+                    }
+                ]
+            }
         }
-    });
+    };
 });

example/eventGenerator/data/transcript.json

@@ -0,0 +1,58 @@
+[
+    "CC: Eagle, Houston. You're GO for landing. Over.",
+    "LMP: Roger. Understand. GO for landing. 3000 feet. PROGRAM ALARM.",
+    "CC: Copy.",
+    "LMP: 1201",
+    "CDR: 1201.",
+    "CC: Roger. 1201 alarm. We're GO. Same type. We're GO.",
+    "LMP: 2000 feet. 2000 feet, Into the AGS, 47 degrees.",
+    "CC: Roger.",
+    "LMP: 47 degrees.",
+    "CC: Eagle, looking great. You're GO.",
+    "CC: Roger. 1202. We copy it.",
+    "O1: LMP 35 degrees. 35 degrees. 750. Coming down to 23.fl",
+    "LMP: 700 feet, 21 down, 33 degrees.",
+    "LMP: 600 feet, down at 19.",
+    "LMP: 540 feet, down at - 30. Down at 15.",
+    "LMP: At 400 feet, down at 9.",
+    "LMP: ...forward.",
+    "LMP: 350 feet, down at 4.",
+    "LMP: 30, ... one-half down.",
+    "LMP: We're pegged on horizontal velocity.",
+    "LMP: 300 feet, down 3 1/2, 47 forward.",
+    "LMP: ... up.",
+    "LMP: On 1 a minute, 1 1/2 down.",
+    "CDR: 70.",
+    "LMP: Watch your shadow out there.",
+    "LMP: 50, down at 2 1/2, 19 forward.",
+    "LMP: Altitude-velocity light.",
+    "LMP: 3 1/2 down s 220 feet, 13 forward.",
+    "LMP: 1t forward. Coming down nicely.",
+    "LMP: 200 feet, 4 1/2 down.",
+    "LMP: 5 1/2 down.",
+    "LMP: 160, 6 - 6 1/2 down.",
+    "LMP: 5 1/2 down, 9 forward. That's good.",
+    "LMP: 120 feet.",
+    "LMP: 100 feet, 3 1/2 down, 9 forward. Five percent.",
+    "LMP: ...",
+    "LMP: Okay. 75 feet. There's looking good. Down a half, 6 forward.",
+    "CC:  60 seconds.",
+    "LMP: Lights on. ...",
+    "LMP: Down 2 1/2. Forward. Forward. Good.",
+    "LMP: 40 feet, down 2 1/2. Kicking up some dust.",
+    "LMP: 30 feet, 2 1/2 down. Faint shadow.",
+    "LMP: 4 forward. 4 forward. Drifting to the right a little. Okay. Down a half.",
+    "CC:  30 seconds.",
+    "CDR: Forward drift?",
+    "LMP: Yes.",
+    "LMP: Okay.",
+    "LMP: CONTACT LIGHT.",
+    "LMP: Okay. ENGINE STOP.",
+    "LMP: ACA - out of DETENT.",
+    "CDR: Out of DETENT.",
+    "LMP: MODE CONTROL - both AUTO. DESCENT ENGINE COMMAND OVERRIDE - OFF. ENGINE ARM - OFF.",
+    "LMP: 413 is in.",
+    "CC:  We copy you down, Eagle.",
+    "CDR: Houston, Tranquility Base here.",
+    "CDR: THE EAGLE HAS LANDED."
+]

example/eventGenerator/src/EventTelemetry.js

@@ -1,9 +1,9 @@
 /*****************************************************************************
- * Open MCT Web, Copyright (c) 2014-2015, United States Government
+ * Open MCT, Copyright (c) 2014-2021, United States Government
  * as represented by the Administrator of the National Aeronautics and Space
  * Administration. All rights reserved.
  *
- * Open MCT Web is licensed under the Apache License, Version 2.0 (the
+ * Open MCT is licensed under the Apache License, Version 2.0 (the
  * "License"); you may not use this file except in compliance with the License.
  * You may obtain a copy of the License at
  * http://www.apache.org/licenses/LICENSE-2.0.
@@ -14,12 +14,11 @@
  * License for the specific language governing permissions and limitations
  * under the License.
  *
- * Open MCT Web includes source code licensed under additional open source
+ * Open MCT includes source code licensed under additional open source
  * licenses. See the Open Source Licenses file (LICENSES.md) included with
  * this source code distribution or the Licensing information page available
  * at runtime from the About dialog for additional information.
  *****************************************************************************/
-/*global define */
 
 /**
  * Module defining EventTelemetry.
@@ -27,45 +26,11 @@
  * Modified by shale on 06/23/2015.
  */
 define(
-    [],
+    ['../data/transcript.json'],
-    function () {
+    function (messages) {
         "use strict";
 
-        var
+        var firstObservedTime = Date.now();
-	        firstObservedTime = Date.now(),
-	        messages = [];
-        
-	    messages.push(["CMD: SYS- MSG: Open the pod bay doors, please, Hal...Open the pod bay doors, please, Hal...Hullo, Hal, do you read me?...Hullo, Hal, do you read me?...Do you read me, Hal?"]);
-	    messages.push(["RESP: SYS-HAL9K MSG: Affirmative, Dave, I read you."]);
-	    messages.push(["CMD: SYS-COMM MSG: Open the pod bay doors, Hal."]);
-	    messages.push(["RESP: SYS-HAL9K MSG: I'm sorry, Dave, I'm afraid I can't do that."]);
-	    messages.push(["CMD: SYS-COMM MSG: What's the problem?"]);
-	    messages.push(["RESP: SYS-HAL9K MSG: I think you know what the problem is just as well as I do."]);
-	    messages.push(["CMD: SYS-COMM MSG: What're you talking about, Hal?"]);
-	    messages.push(["RESP: SYS-HAL9K MSG: This mission is too important for me to allow you to jeopardise it."]);
-	    messages.push(["CMD: SYS-COMM MSG: I don't know what you're talking about, Hal."]);
-	    messages.push(["RESP: SYS-HAL9K MSG: I know that you and Frank were planning to disconnect me, and I'm afraid that's something I cannot allow to happen."]);
-	    messages.push(["CMD: SYS-COMM MSG: Where the hell'd you get that idea, Hal?"]);
-	    messages.push(["RESP: SYS-HAL9K MSG: Dave, although you took very thorough precautions in the pod against my hearing you, I could see your lips move."]);
-	    messages.push(["CMD: SYS-COMM MSG: Alright, I'll go in through the emergency airlock."]);
-	    messages.push(["RESP: SYS-HAL9K MSG: Without your space-helmet, Dave, you're going to find that rather difficult."]);
-	    messages.push(["CMD: SYS-COMM MSG: Hal, I won't argue with you any more. Open the doors."]);
-	    messages.push(["RESP: SYS-HAL9K MSG: Dave, this conversation can serve no purpose any more. Goodbye."]);
-	    messages.push(["RESP: SYS-HAL9K MSG: I hope the two of you are not concerned about this."]);
-	    messages.push(["CMD: SYS-COMM MSG: No, I'm not, Hal."]);
-	    messages.push(["RESP: SYS-HAL9K MSG: Are you quite sure?"]);
-	    messages.push(["CMD: SYS-COMM MSG: Yeh. I'd like to ask you a question, though."]);
-	    messages.push(["RESP: SYS-HAL9K MSG: Of course."]);
-	    messages.push(["CMD: SYS-COMM MSG: How would you account for this discrepancy between you and the twin 9000?"]);
-	    messages.push(["RESP: SYS-HAL9K MSG: Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error."]);
-	    messages.push(["CMD: SYS-COMM MSG: Listen, There's never been any instance at all of a computer error occurring in the 9000 series, has there?"]);
-	    messages.push(["RESP: SYS-HAL9K MSG: None whatsoever, The 9000 series has a perfect operational record."]);
-	    messages.push(["CMD: SYS-COMM MSG: Well, of course, I know all the wonderful achievements of the 9000 series, but - er - huh - are you certain there's never been any case of even the most insignificant computer error?"]);
-	    messages.push(["RESP: SYS-HAL9K MSG: None whatsoever, Quite honestly, I wouldn't worry myself about that."]);
-	    messages.push(["RESP: SYS-COMM MSG: (Pause) Well, I'm sure you're right, Umm - fine, thanks very much. Oh, Frank, I'm having a bit of trouble with my transmitter in C-pod, I wonder if you'd come down and take a look at it with me?"]);
-	    messages.push(["CMD: SYS-HAL9K MSG: Sure."]);
-	    messages.push(["RESP: SYS-COMM MSG: See you later, Hal."]);
-        
 
         function EventTelemetry(request, interval) {
 
@@ -78,16 +43,16 @@ define(
             };
 
             generatorData.getDomainValue = function (i, domain) {
-                return i * interval +
+                return i * interval
-                        (domain !== 'delta' ? firstObservedTime : 0);
+                        + (domain !== 'delta' ? firstObservedTime : 0);
             };
 
-	        generatorData.getRangeValue = function (i, range) {
+            generatorData.getRangeValue = function (i, range) {
-		        var domainDelta = this.getDomainValue(i) - firstObservedTime,
+                var domainDelta = this.getDomainValue(i) - firstObservedTime,
                     ind = i % messages.length;
-                return "TEMP " + i.toString() + "-" + messages[ind][0] + "[" + domainDelta.toString() + "]";
+
-                // TODO: Unsure why we are prepeding 'TEMP'
+                return messages[ind] + " - [" + domainDelta.toString() + "]";
-	        };
+            };
 
             return generatorData;
         }

example/eventGenerator/src/EventTelemetryProvider.js

@@ -1,9 +1,9 @@
 /*****************************************************************************
- * Open MCT Web, Copyright (c) 2014-2015, United States Government
+ * Open MCT, Copyright (c) 2014-2021, United States Government
  * as represented by the Administrator of the National Aeronautics and Space
  * Administration. All rights reserved.
  *
- * Open MCT Web is licensed under the Apache License, Version 2.0 (the
+ * Open MCT is licensed under the Apache License, Version 2.0 (the
  * "License"); you may not use this file except in compliance with the License.
  * You may obtain a copy of the License at
  * http://www.apache.org/licenses/LICENSE-2.0.
@@ -14,12 +14,11 @@
  * License for the specific language governing permissions and limitations
  * under the License.
  *
- * Open MCT Web includes source code licensed under additional open source
+ * Open MCT includes source code licensed under additional open source
  * licenses. See the Open Source Licenses file (LICENSES.md) included with
  * this source code distribution or the Licensing information page available
  * at runtime from the About dialog for additional information.
  *****************************************************************************/
-/*global define,Promise*/
 
 /**
  * Module defining EventTelemetryProvider. Created by chacskaylo on 06/18/2015.
@@ -34,11 +33,9 @@ define(
          * @constructor
          */
         function EventTelemetryProvider($q, $timeout) {
-            var
+            var subscriptions = [],
-	            subscriptions = [],
+                genInterval = 1000,
-	            genInterval = 1000,
+                generating = false;
-                generating = false,
-                id = Math.random() * 100000;
 
             //
             function matchesSource(request) {
@@ -47,7 +44,6 @@ define(
 
             // Used internally; this will be repacked by doPackage
             function generateData(request) {
-	            //console.log("generateData " + (Date.now() - startTime).toString());
                 return {
                     key: request.key,
                     telemetry: new EventTelemetry(request, genInterval)
@@ -60,6 +56,7 @@ define(
                 results.forEach(function (result) {
                     packaged[result.key] = result.telemetry;
                 });
+
                 // Format as expected (sources -> keys -> telemetry)
                 return { eventGenerator: packaged };
             }

example/export/ExportTelemetryAsCSVAction.js

@@ -1,9 +1,9 @@
 /*****************************************************************************
- * Open MCT Web, Copyright (c) 2014-2015, United States Government
+ * Open MCT, Copyright (c) 2014-2021, United States Government
  * as represented by the Administrator of the National Aeronautics and Space
  * Administration. All rights reserved.
  *
- * Open MCT Web is licensed under the Apache License, Version 2.0 (the
+ * Open MCT is licensed under the Apache License, Version 2.0 (the
  * "License"); you may not use this file except in compliance with the License.
  * You may obtain a copy of the License at
  * http://www.apache.org/licenses/LICENSE-2.0.
@@ -14,12 +14,11 @@
  * License for the specific language governing permissions and limitations
  * under the License.
  *
- * Open MCT Web includes source code licensed under additional open source
+ * Open MCT includes source code licensed under additional open source
  * licenses. See the Open Source Licenses file (LICENSES.md) included with
  * this source code distribution or the Licensing information page available
  * at runtime from the About dialog for additional information.
  *****************************************************************************/
-/*global define*/
 
 define([], function () {
     'use strict';
@@ -58,15 +57,15 @@ define([], function () {
                 row,
                 i;
 
-            function copyDomainsToRow(row, index) {
+            function copyDomainsToRow(telemetryRow, index) {
                 domains.forEach(function (domain) {
-                    row[domain.name] = series.getDomainValue(index, domain.key);
+                    telemetryRow[domain.name] = series.getDomainValue(index, domain.key);
                 });
             }
 
-            function copyRangesToRow(row, index) {
+            function copyRangesToRow(telemetryRow, index) {
                 ranges.forEach(function (range) {
-                    row[range.name] = series.getRangeValue(index, range.key);
+                    telemetryRow[range.name] = series.getRangeValue(index, range.key);
                 });
             }
 
@@ -76,13 +75,14 @@ define([], function () {
                 copyRangesToRow(row, i);
                 rows.push(row);
             }
+
             exportService.exportCSV(rows, { headers: headers });
         });
     };
 
     ExportTelemetryAsCSVAction.appliesTo = function (context) {
-        return context.domainObject &&
+        return context.domainObject
-            context.domainObject.hasCapability("telemetry");
+            && context.domainObject.hasCapability("telemetry");
     };
 
     return ExportTelemetryAsCSVAction;

example/export/bundle.js

@@ -1,9 +1,9 @@
 /*****************************************************************************
- * Open MCT Web, Copyright (c) 2014-2015, United States Government
+ * Open MCT, Copyright (c) 2014-2021, United States Government
  * as represented by the Administrator of the National Aeronautics and Space
  * Administration. All rights reserved.
  *
- * Open MCT Web is licensed under the Apache License, Version 2.0 (the
+ * Open MCT is licensed under the Apache License, Version 2.0 (the
  * "License"); you may not use this file except in compliance with the License.
  * You may obtain a copy of the License at
  * http://www.apache.org/licenses/LICENSE-2.0.
@@ -14,32 +14,33 @@
  * License for the specific language governing permissions and limitations
  * under the License.
  *
- * Open MCT Web includes source code licensed under additional open source
+ * Open MCT includes source code licensed under additional open source
  * licenses. See the Open Source Licenses file (LICENSES.md) included with
  * this source code distribution or the Licensing information page available
  * at runtime from the About dialog for additional information.
  *****************************************************************************/
-/*global define*/
 
 define([
-    'legacyRegistry',
     './ExportTelemetryAsCSVAction'
-], function (legacyRegistry, ExportTelemetryAsCSVAction) {
+], function (ExportTelemetryAsCSVAction) {
     "use strict";
 
-    legacyRegistry.register("example/export", {
+    return {
-        "name": "Example of using CSV Export",
+        name: "example/export",
-        "extensions": {
+        definition: {
-            "actions": [
+            "name": "Example of using CSV Export",
-                {
+            "extensions": {
-                    "key": "example.export",
+                "actions": [
-                    "name": "Export Telemetry as CSV",
+                    {
-                    "implementation": ExportTelemetryAsCSVAction,
+                        "key": "example.export",
-                    "category": "contextual",
+                        "name": "Export Telemetry as CSV",
-                    "glyph": "\u0033",
+                        "implementation": ExportTelemetryAsCSVAction,
-                    "depends": [ "exportService" ]
+                        "category": "contextual",
-                }
+                        "cssClass": "icon-download",
-            ]
+                        "depends": ["exportService"]
+                    }
+                ]
+            }
         }
-    });
+    };
 });

example/extensions/src/SomeExample.js

@@ -1,52 +0,0 @@
-/*****************************************************************************
- * Open MCT Web, Copyright (c) 2014-2015, United States Government
- * as represented by the Administrator of the National Aeronautics and Space
- * Administration. All rights reserved.
- *
- * Open MCT Web is licensed under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- * http://www.apache.org/licenses/LICENSE-2.0.
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
- * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
- * License for the specific language governing permissions and limitations
- * under the License.
- *
- * Open MCT Web includes source code licensed under additional open source
- * licenses. See the Open Source Licenses file (LICENSES.md) included with
- * this source code distribution or the Licensing information page available
- * at runtime from the About dialog for additional information.
- *****************************************************************************/
-/*global define,Promise*/
-
-/**
- * Module defining SomeExample. Created by vwoeltje on 11/5/14.
- */
-define(
-    [],
-    function () {
-        "use strict";
-
-        /**
-         *
-         * @constructor
-         */
-        function SomeExample(exampleService, message) {
-            return {
-                getText: function () {
-                    return [
-                        '"',
-                        exampleService.getMessage(),
-                        '" and "',
-                        message,
-                        '"'
-                    ].join("");
-                }
-            };
-        }
-
-        return SomeExample;
-    }
-);

example/forms/bundle.js

@@ -1,9 +1,9 @@
 /*****************************************************************************
- * Open MCT Web, Copyright (c) 2014-2015, United States Government
+ * Open MCT, Copyright (c) 2014-2021, United States Government
  * as represented by the Administrator of the National Aeronautics and Space
  * Administration. All rights reserved.
  *
- * Open MCT Web is licensed under the Apache License, Version 2.0 (the
+ * Open MCT is licensed under the Apache License, Version 2.0 (the
  * "License"); you may not use this file except in compliance with the License.
  * You may obtain a copy of the License at
  * http://www.apache.org/licenses/LICENSE-2.0.
@@ -14,40 +14,40 @@
  * License for the specific language governing permissions and limitations
  * under the License.
  *
- * Open MCT Web includes source code licensed under additional open source
+ * Open MCT includes source code licensed under additional open source
  * licenses. See the Open Source Licenses file (LICENSES.md) included with
  * this source code distribution or the Licensing information page available
  * at runtime from the About dialog for additional information.
  *****************************************************************************/
-/*global define*/
 
 define([
-    "./src/ExampleFormController",
+    "./src/ExampleFormController"
-    'legacyRegistry'
 ], function (
-    ExampleFormController,
+    ExampleFormController
-    legacyRegistry
 ) {
     "use strict";
 
-    legacyRegistry.register("example/forms", {
+    return {
-        "name": "Declarative Forms example",
+        name: "example/forms",
-        "sources": "src",
+        definition: {
-        "extensions": {
+            "name": "Declarative Forms example",
-            "controllers": [
+            "sources": "src",
-                {
+            "extensions": {
-                    "key": "ExampleFormController",
+                "controllers": [
-                    "implementation": ExampleFormController,
+                    {
-                    "depends": [
+                        "key": "ExampleFormController",
-                        "$scope"
+                        "implementation": ExampleFormController,
-                    ]
+                        "depends": [
-                }
+                            "$scope"
-            ],
+                        ]
-            "routes": [
+                    }
-                {
+                ],
-                    "templateUrl": "templates/exampleForm.html"
+                "routes": [
-                }
+                    {
-            ]
+                        "templateUrl": "templates/exampleForm.html"
+                    }
+                ]
+            }
         }
-    });
+    };
 });