adds StackingOrder module to project, to manage different layers/stackingContexts in the dom

.editorconfig

@@ -0,0 +1,15 @@
+# EditorConfig is awesome: http://EditorConfig.org
+root = true
+
+[*]
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = false
+
+[*.{js,css,html}]
+indent_style = space
+indent_size = 4
+
+[{.*,package.json,.travis.yml}]
+indent_style = space
+indent_size = 2

.eslintignore

@@ -0,0 +1,6 @@
+thirdPartyCode/
+frames/resources/
+frames/pushMe.hyperesources/
+frames/objectDefaultFiles/pep.min.js
+docs/
+.eslintrc.js

.eslintrc.js

@@ -0,0 +1,98 @@
+module.exports = {
+    "env": {
+        "browser": true,
+        "es6": true
+    },
+    "extends": "eslint:recommended",
+    "globals": {
+        "Atomics": "readonly",
+        "SharedArrayBuffer": "readonly",
+        "Stats": "readonly",
+
+        "Block": "writable",
+        "BlockLink": "writable",
+        "CRAFTING_GRID_HEIGHT": "writable",
+        "CRAFTING_GRID_WIDTH": "writable",
+        "DEBUG_DATACRAFTING": "writable",
+        "Frame": "writable",
+        "Logic": "writable",
+        "LogicGUIState": "writable",
+        "Objects": "writable",
+        "SEA3D": "writable",
+        "TEMP_DISABLE_MEMORIES": "writable",
+        "THREE": "writable",
+        "ToolSocket": "writable",
+        "TWEEN": "writable",
+        "WebKitPoint": "writable",
+        "acceptUDPBeats": "writable",
+        "boundListeners": "writable",
+        "cc": "writable",
+        "cout": "writable",
+        "createNameSpace": "writable",
+        "d3": "writable",
+        "editingAnimationsMatrix": "writable",
+        "globalCanvas": "writable",
+        "globalDOMCache": "writable",
+        "globalProgram": "writable",
+        "globalFrameScaleAdjustment": "writable",
+        "globalNodeScaleAdjustment": "writable",
+        "globalStates": "writable",
+        "httpPort": "writable",
+        "defaultHttpPort": "writable",
+        "hull": "writable",
+        "io": "writable",
+        "objects": "writable",
+        "overlayDiv": "writable",
+        "p5": "writable",
+        "pocketBegin": "writable",
+        "pocketDropAnimation": "writable",
+        "pocketFrame": "writable",
+        "pocketItem": "writable",
+        "pocketItemId": "writable",
+        "pocketNode": "writable",
+        "publicDataCache": "writable",
+        "realityEditor": "writable",
+        "realityElements": "writable",
+        "rotateX": "writable",
+        "rotationXMatrix": "writable",
+        "rr": "writable",
+        "shadowObjects": "writable",
+        "targetDownloadStates": "writable",
+        "timeCorrection": "writable",
+        "timeForContentLoaded": "writable",
+        "visibleObjectTapDelay": "writable",
+        "visibleObjectTapInterval": "writable",
+        "webkitConvertPointFromPageToNode": "writable",
+    },
+    "parserOptions": {
+        "ecmaVersion": 2018,
+        "sourceType": "module",
+    },
+    "rules": {
+        "no-prototype-builtins": "off",
+        "no-redeclare": [
+          "error",
+          {"builtinGlobals": false}
+        ],
+        "no-unused-vars": [
+          "error",
+          {
+            "varsIgnorePattern": "^_",
+            "argsIgnorePattern": "^_",
+          },
+        ],
+        "no-inner-declarations": "off",
+    },
+    "overrides": [{
+        "files": [
+          "src/constructors.js",
+          "src/device/utilities.js",
+          "src/objects.js",
+          "src/states.js",
+        ],
+        "parserOptions": {
+            "ecmaVersion": 2018,
+            "sourceType": "script"
+        }
+    }]
+};

.github/dependabot.yml

@@ -0,0 +1,8 @@
+version: 2
+updates:
+- package-ecosystem: npm
+  directory: "/"
+  schedule:
+    interval: daily
+    time: "10:00"
+  open-pull-requests-limit: 10

.github/workflows/nodejs.yml

@@ -0,0 +1,24 @@
+name: Node.js CI
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [16.x]
+
+    steps:
+    - uses: actions/checkout@v2
+    - name: Use Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v1
+      with:
+        node-version: ${{ matrix.node-version }}
+    - run: npm install
+    - run: npm run build --if-present
+    - run: npm test
+      env:
+        CI: true

.gitignore

@@ -1,5 +1,13 @@
 # idea editing tools
 .idea
+.editorconfig
 
 # osx directory files
-.DS_Store
+.DS_Store
+
+# documentation can be regenerated by running "bash generate_docs.sh"
+docs/
+
+node_modules/
+
+*.swp

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at realityLab@ptc.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,42 @@
+## How To Contribute
+
+Thank you for your interest! We love all community contributions. They are
+great ways to suggest new features, call attention to bugs, or see your work
+come to life! There are a couple different ways to contribute:
+
+### Talking in the Forum
+
+The best place to go for all things Spatial Toolbox is our [forum at
+forum.spatialtoolbox.vuforia.com](https://forum.spatialtoolbox.vuforia.com/).
+There you can ask open-ended questions and discuss feature ideas without
+commiting to filing a GitHub issue.
+
+### Bugs and Features
+
+If you do want to make an official tracked report or request, check out the
+Issues list linked to in this repository's GitHub page. It's possible that
+someone has already had the same idea or same problem.
+
+If it's a new bug then please provide as much information as possible. First,
+provide a description of the problem, e.g. "the tools on screen disappear after
+pressing the pocket button." This includes the platforms and versions involved,
+e.g. Spatial Toolbox 1.3.0 on an iPhone 10 talking to a Spatial Edge Server
+running on Node 12 on Ubuntu 18.04. Next, any steps to reproduce the bug would
+be wonderful. For example, "this happened most often when I created three
+tools, restarted the server, then pressed the pocket button in my app."
+
+If it's a new feature just let us know why it's the best and greatest feature
+in the world. Maybe you'll convince a wandering contributor to submit a pull
+request!
+
+### Pull Requests
+
+Submitting pull requests is a great way to contribute! For more information
+about pull requests, check out [GitHub's
+documentation](https://docs.github.com/en/free-pro-team@latest/github/collaborating-with-issues-and-pull-requests/about-pull-requests).
+
+It helps out your pull request if you make sure that your code is easy to read
+and understand. One test we use for this is running eslint, a style checker for
+JavaScript. You can either run [eslint
+locally](https://eslint.org/docs/user-guide/command-line-interface) or check
+out its results on the pull request itself.