etro 0.6.0

package/.env

@@ -0,0 +1,2 @@
+GITHUB_TOKEN=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
+NPM_AUTH_TOKEN=9f33f7fb-82a2-4e87-a4ba-3860f13a3b68

package/.github/workflows/nodejs.yml

@@ -0,0 +1,27 @@
+name: Node CI
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [8.x, 10.x, 12.x]
+
+    steps:
+    - uses: actions/checkout@v1
+    - name: Use Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v1
+      with:
+        node-version: ${{ matrix.node-version }}
+    - name: npm install, lint, build, and test
+      run: |
+        npm ci
+        npm run lint
+        npm run build
+        npm test
+      env:
+        CI: true

package/CHANGELOG.md

@@ -0,0 +1,109 @@
+# Changelog
+
+## [0.6.0] - 2019-12-26
+### Added
+- Add [API documentation](https://etrojs.dev/).
+- Support enabling and disabling layers and effects.
+- Implement more movie events (*movie.play*, *movie.record*, *movie.pause*, *movie.change.duration*).
+- Implement [property filters](https://github.com/etro-js/etro/wiki/Property-Filters).
+- Implement property caching.
+- Media layer supports media whose duration changes.
+- Add unimplemented `etro.Font` properties.
+- Add example that uses a live stream (the webcam).
+
+### Changed
+- Add layer `start` and `stop` methods.
+- Add layer and effect `attach` and `detach` methods.
+- Make some properties public (`_getDefaultOptions`, `_publicExcludes`, `layer.Base#_render`, `event._publish`, `layer.Base#_render`, `event._publish`, `layer.Visual#_doRender`).
+- Change `etro.val(property, element, time)` → `etro.val(element, path, time)`.
+- Make event properties specific to event type
+  - *layer.attach|detach*: `source` → `effectTarget`
+  - *effect.attach|detach*: `source` → `effectTarget`
+  - *movie.change.layer.add|remove*: `source` → `layer`
+  - *movie.change.effect.add|remove*: `source` → `effect`
+
+### Fixed
+- Media current time is no longer reset every time it's played.
+- Fix Gaussian blur effect throwing error.
+- Custom textures work for shader effects.
+- Fix undefined behavior with shader effects that output transparency.
+- Use `sourceTextureOptions` in shader effects.
+- Recursive property changes now emit events with `etro.watchPublic`.
+- Public properties set to keyframes are treated as keyframes.
+- Update event names in examples.
+
+## [0.5.0] - 2019-10-09
+### Added
+- Movies and layers auto-refresh.
+
+### Changed
+- Rewrite event system.
+  - Events propogate up.
+  - Event names are organized into groups.
+
+### Fixed
+- Update IIFE global export from `mv` to `etro`.
+- Fix recording audio.
+- Fix recording movies without audio in Chrome.
+- Fix effects for movies.
+
+## [0.4.0] - 2019-08-18
+### Added
+- WebGL fragment shader effects, with which you can re-render a layer or movie with a GLSL fragment shader.
+- New `initialRefresh` movie option that can prevent rendering on init.
+
+### Changed
+- Most visual effects now use GLSL.
+- New `element` argument passed to function properties to see which Etro object the property belongs to.
+
+## [0.3.0] - 2018-12-11
+### Added
+- Function properties.
+  - Dynamic properties that call a function every time they're queried.
+
+### Changed
+- Null or undefined layer dimensions default to the width or height of the movie.
+- Movie "end" event is now called "ended".
+
+### Fixed
+- Bug with layer options
+
+### Removed
+- Volume, speed and muted properties. These will most likely be added as separate audio effects in the future.
+
+## [0.2.0] - 2018-10-14
+### Added
+- Keyframes
+  - Works with any value type in pretty much every built-in component property.
+  - Number and objects, including colors and fonts, can interpolate.
+  - Custom interpolation option.
+- Elliptical mask effect.
+- Many small improvements.
+
+## [0.1.0] - 2018-10-06
+### Added
+- Movies
+  - Timeline
+  - Playing
+  - Exporting
+- Layers
+  - Base layers
+  - Text layers
+  - Image layers
+  - Audio layers
+  - Video layers
+- Effects
+  - Transparency
+  - Brightness
+  - Contrast
+  - Channels
+  - Gaussian blur
+  - Transform
+
+[0.6.0]: https://github.com/etro-js/etro/compare/v0.6...HEAD
+[0.5.0]: https://github.com/etro-js/etro/compare/v0.5...v0.6
+[0.4.0]: https://github.com/etro-js/etro/compare/v0.4...v0.5
+[0.3.0]: https://github.com/etro-js/etro/compare/v0.3...v0.4
+[0.3.0]: https://github.com/etro-js/etro/compare/v0.2...v0.3
+[0.2.0]: https://github.com/etro-js/etro/compare/v0.1...v0.2
+[0.1.0]: https://github.com/etro-js/etro/releases/tag/v0.1

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,77 @@
+# 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 me at **\@etro-js** in the [Slack workspace]. 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
+[slack workspace]: https://join.slack.com/t/etrojs/shared_invite/enQtNzgxODc0ODUyMjU2LTA5MGM5YzIyOGU5NjQxY2E0YmIzYzhhZTU4ODdjNzBiY2M3MzgwZTZiYzU5ZmE2NmYyMjc0ZTE0ZWIxMjBmN2Q
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

package/CONTRIBUTING.md

@@ -0,0 +1,155 @@
+# Contributing
+
+## Introduction
+
+Thank you for considering contributing to Etro! There are many ways you can contribute to Etro, like creating issues for features or bugs, improving the docs or wiki, or writing the actual code for the library. This page covers how to make changes to the repository files (either code or docs).
+
+> Etro has a [Taiga Project](https://tree.taiga.io/project/etro-js-etro/epics) for managing issues and a [Slack workspace](https://join.slack.com/t/etrojs/shared_invite/enQtNzgxODc0ODUyMjU2LTA5MGM5YzIyOGU5NjQxY2E0YmIzYzhhZTU4ODdjNzBiY2M3MzgwZTZiYzU5ZmE2NmYyMjc0ZTE0ZWIxMjBmN2Q) for questions and casual discussion
+
+## Setting up your local environment
+
+#### Step 0: Dependencies
+
+- You will need `git`, `node` and `npm`
+
+#### Step 1: Fork
+
+- Create your own fork of Etro. Then run
+
+  ```
+  $ git clone https://github.com/username/etro.git`
+  $ cd etro
+  $ git remote add upstream https://github.com/etro-js/etro.git
+  $ git fetch upstream
+  $ npm install
+  ```
+
+#### Step 2: Branch
+
+- To help organize your work, create a branch for your topic. Avoid working directly off the `master` branch
+
+  ```
+  $ git checkout -b topic-branch
+  ```
+
+## Making your changes
+
+#### Step 3: Code
+
+- If you are writing code, please follow the style guide [StandardJS](https://standardjs.com/rules.html)
+
+- To start the development server run
+
+  ```
+  $ npm start
+  ```
+
+  Then, you can see your changes by running some [examples](examples).
+
+- When you're ready to submit a piece of work, first run
+
+  ```
+  $ npm run lint
+  $ npm run build
+  $ npm test
+  ```
+
+  to lint the code, generate the [dist](dist) files and run unit tests on them.
+
+- Commit your changes
+  - Please avoid squashing all your commits into one; we try to keep each commit atomic in the `master` branch
+  - Please follow these commit message guidelines:
+    - Optionally, begin each commit message with [an appropriate emoji](https://gitmoji.carloscuesta.me/)
+    - Then, write a concise summary of your changes. If you feel you need to, bullet the main idea of your changes in the description and/or explain why you made the changes.
+    - Write in the imperative tense
+    - The first line should be 50 characters or less. Wrap lines after around 72 characters (for Vim add `filetype indent plugin on` to ~/.vimrc, and its enabled by default in Atom).
+    - *Example:*
+
+      ```
+      :emoji: One-liner
+
+      Optional description
+      ```
+
+## Submitting your changes
+
+#### Step 3: Push
+
+- First, rebase (don't merge) to integrate your work with the main repository
+
+  ```
+  $ git fetch upstream
+  $ git rebase upstream/master
+  ```
+
+- Push your changes to the topic branch in your fork of the repository
+
+  ```
+  $ git push origin topic-branch
+  ```
+
+#### Step 4: Pull request
+
+- Open a pull request from your topic-branch to the main repository
+- In the PR title, include **fixes ###** for bugs and **resolves ###** for feature requests
+- If you changed any core functionality, make sure you explain your motives for those changes
+
+#### Step 5: Feedback
+
+- A large part of the submission process is receiving feedback on how you can improve you pull request. If you need change your pull request,
+
+  ```
+  $ git add path/to/changes
+  $ git commit
+  $ git push origin topic-branch
+  ```
+
+## Code overview
+
+*Note: To specify the ES6 module (file) that a declaration exists in, the following syntax will be used: `module.export`.*
+
+### Module Structure
+
+If you are new to the core elements of etro, you should probably read [the *Overview* wiki page](https://github.com/etro-js/etro.wiki/Overview.md).
+
+Here are the contents of **src**:
+
+| Path | Contents |
+| --- | --- |
+| [**effect.js**](src/effect.js) | all (visual) effect classes |
+| [**event.js**](src/event.js) | the pub/sub mechanics |
+| [**index.js**](src/index.js) | the entry module |
+| [**layer.js**](src/layer.js) | all layer classes |
+| [**movie.js**](src/movie.js) | the `Movie` class |
+| [**util.js**](src/util.js) | general utility |
+
+Note that most of the above files will (hopefully soon) be broken down into multiple files each.
+
+### Etro Objects
+
+The base etro objects are the following:
+* `Movie` - the movie (or entire user project)
+* `layer.Base` - the root type of layer
+* `effect.Base` - the root type of visual effect
+
+### Concepts
+
+#### Pub/sub system
+
+Events emitted by Etro objects use a [pub/sub system](https://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern). To emit an event, use `event.publish(target, type, event)`. For instance,
+
+```js
+event.publish(movie, 'movie.type.of.event', { additionalData: 'foo' })
+```
+
+That will notify all listeners of `movie` for event types `'movie'`, `'movie.type'`, `'movie.type.of'` and `'movie.type.of.event'`. To listen for an event, use `event.subscribe(target, type, listener)`, like
+
+```js
+event.subscribe(movie, 'movie.type', event => {
+  console.log(event.target, event.type, event.additionalData) // should print the movie, 'movie.type.of.event', 'foo'
+}
+```
+
+#### Values vs. Properties
+
+In Etro objects, almost any property can be a [keyframe](https://github.com/etro-js/etro/wiki/Keyframes), [function](https://github.com/etro-js/etro/wiki/Functions), or just a constant value. To access the current value of the property at a given time, use `util.val(property, element, time)`; where `property` is the keyframe set, function or constant value, `element` is the object to which `property` belongs, and `time` is the current time relative to the element.