Skip to content

Commit 669459f

Browse files
arturvardanyanarturvardanyan
committed
initial commit
0 parents  commit 669459f

File tree

156 files changed

+78276
-0
lines changed

Some content is hidden

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

156 files changed

+78276
-0
lines changed

‎.github/ISSUE_TEMPLATE.md

+41
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
<!--- Provide a general summary of the issue in the Title above -->
2+
3+
## Expected Behavior
4+
5+
<!--- If you're describing a bug, tell us what should happen -->
6+
<!--- If you're suggesting a change/improvement, tell us how it should work -->
7+
8+
## Current Behavior
9+
10+
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
11+
<!--- If suggesting a change/improvement, explain the difference from current behavior -->
12+
13+
## Possible Solution
14+
15+
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
16+
<!--- or ideas how to implement the addition or change -->
17+
18+
## Steps to Reproduce (for bugs)
19+
20+
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
21+
<!--- reproduce this bug. Include code to reproduce, if relevant -->
22+
23+
1. 2. 3. 4.
24+
25+
## Context
26+
27+
<!--- How has this issue affected you? What are you trying to accomplish? -->
28+
<!--- Providing context helps us come up with a solution that is most useful in the real world -->
29+
30+
## Your Environment
31+
32+
<!--- Include as many relevant details about the environment you experienced the bug in -->
33+
34+
- Version used:
35+
- Environment name and version (e.g. Chrome 39, node.js 5.4):
36+
- Operating System and version (desktop or mobile):
37+
- Link to your project:
38+
39+
# Stack trace
40+
41+
<!--- Include stack trace -->

‎.github/PULL_REQUEST_TEMPLATE.md

+43
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
<!--- Provide a general summary of your changes in the Title above -->
2+
3+
## Description
4+
5+
<!--- Describe your changes in detail -->
6+
7+
## Related Issue
8+
9+
<!--- This project only accepts pull requests related to open issues -->
10+
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
11+
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
12+
<!--- Please link to the issue here: -->
13+
14+
## Motivation and Context
15+
16+
<!--- Why is this change required? What problem does it solve? -->
17+
18+
## How Has This Been Tested?
19+
20+
<!--- Please describe in detail how you tested your changes. -->
21+
<!--- Include details of your testing environment, and the tests you ran to -->
22+
<!--- see how your change affects other areas of the code, etc. -->
23+
24+
## Types of changes
25+
26+
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
27+
28+
- [ ] Updated docs / Refactor code / Added a tests case (non-breaking change)
29+
- [ ] Bug fix (non-breaking change which fixes an issue)
30+
- [ ] New feature (non-breaking change which adds functionality)
31+
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
32+
33+
## Checklist:
34+
35+
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
36+
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
37+
38+
- [ ] My code follows the code style of this project.
39+
- [ ] My change requires a change to the documentation.
40+
- [ ] I have updated the documentation accordingly.
41+
- [ ] I have read the **CONTRIBUTING** document.
42+
- [ ] I have added tests to cover my changes.
43+
- [ ] All new and existing tests passed.

‎.gitignore

+21
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# See https://help.github.com/ignore-files/ for more about ignoring files.
2+
3+
# dependencies
4+
/node_modules
5+
6+
# testing
7+
/coverage
8+
9+
# production
10+
/build
11+
12+
# misc
13+
.DS_Store
14+
.env.local
15+
.env.development.local
16+
.env.test.local
17+
.env.production.local
18+
19+
npm-debug.log*
20+
yarn-debug.log*
21+
yarn-error.log*

‎.prettierrc

+4
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
{
2+
"singleQuote": true,
3+
"trailingComma": "all"
4+
}

‎.travis.yml

+24
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
language: node_js
2+
node_js:
3+
- stable
4+
before_install:
5+
- export CHROME_BIN=chromium-browser
6+
- export DISPLAY=:99.0
7+
- sh -e /etc/init.d/xvfb start
8+
- yarn config set registry "https://registry.npmjs.org"
9+
- yarn global add greenkeeper-lockfile@1
10+
- yarn global add codeclimate-test-reporter
11+
before_script:
12+
- greenkeeper-lockfile-update
13+
script:
14+
- npm run build
15+
after_script:
16+
- greenkeeper-lockfile-upload
17+
deploy:
18+
provider: pages
19+
skip-cleanup: true
20+
github-token: $GITHUB_TOKEN
21+
keep-history: true
22+
local_dir: build
23+
on:
24+
tags: true

‎.vscode/settings.json

+10
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
{
2+
"javascript.implicitProjectConfig.experimentalDecorators": true,
3+
"editor.codeActionsOnSave": {
4+
"source.organizeImports": false
5+
},
6+
"editor.formatOnSave": true,
7+
"editor.rulers": [120],
8+
"tslint.autoFixOnSave": true,
9+
"javascript.format.enable": false
10+
}

‎CHANGELOG.md

+7
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
# Phaser3 Particle Editor Changelog:
2+
3+
## Phaser3 Particle Editor 1.0.0-alpha1
4+
5+
### 1.0.0-alpha1 - Planned stable version
6+
7+
- first release

‎CODE_OF_CONDUCT.md

+46
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
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, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
6+
7+
## Our Standards
8+
9+
Examples of behavior that contributes to creating a positive environment include:
10+
11+
- Using welcoming and inclusive language
12+
- Being respectful of differing viewpoints and experiences
13+
- Gracefully accepting constructive criticism
14+
- Focusing on what is best for the community
15+
- Showing empathy towards other community members
16+
17+
Examples of unacceptable behavior by participants include:
18+
19+
- The use of sexualized language or imagery and unwelcome sexual attention or advances
20+
- Trolling, insulting/derogatory comments, and personal or political attacks
21+
- Public or private harassment
22+
- Publishing others' private information, such as a physical or electronic address, without explicit permission
23+
- Other conduct which could reasonably be considered inappropriate in a professional setting
24+
25+
## Our Responsibilities
26+
27+
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.
28+
29+
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.
30+
31+
## Scope
32+
33+
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.
34+
35+
## Enforcement
36+
37+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems 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.
38+
39+
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.
40+
41+
## Attribution
42+
43+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
44+
45+
[homepage]: http://contributor-covenant.org
46+
[version]: http://contributor-covenant.org/version/1/4/

‎CONTRIBUTING.md

+35
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
# Contributing to phaser3-ninepatch-plugin
2+
3+
## Setup
4+
5+
1 - Clone your fork of the repository:
6+
7+
```
8+
$ git clone https://github.com/koreezgames/phaser3-particle-editor.git
9+
```
10+
11+
2 - Install npm dependencies using yarn:
12+
13+
```
14+
$ npm install
15+
```
16+
17+
3 - Run start process
18+
19+
```
20+
$ npm run start
21+
```
22+
23+
## Guidelines
24+
25+
- Please try to [combine multiple commits before
26+
pushing](http://stackoverflow.com/questions/6934752/combining-multiple-commits-before-pushing-in-git).
27+
28+
- Always format your code using `npm run autoformat`.
29+
30+
* Please create an issue before sending a PR if your commit is going to change the
31+
public interface of the package or it includes significant architecture
32+
changes.
33+
34+
* Feel free to ask for help from other members of the Koreez team via the
35+
[github issues](https://github.com/koreezgames/phaser3-particle-editor/issues).

‎LICENSE

+21
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
MIT License
2+
3+
Copyright (c) 2018 Koreez LLC
4+
5+
Permission is hereby granted, free of charge, to any person obtaining a copy
6+
of this software and associated documentation files (the "Software"), to deal
7+
in the Software without restriction, including without limitation the rights
8+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9+
copies of the Software, and to permit persons to whom the Software is
10+
furnished to do so, subject to the following conditions:
11+
12+
The above copyright notice and this permission notice shall be included in all
13+
copies or substantial portions of the Software.
14+
15+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21+
SOFTWARE.

‎README.md

+71
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
# Phaser3 Particle Editor
2+
3+
[![GitHub license](https://img.shields.io/badge/license-MIT-green.svg)](https://github.com/koreezgames/phaser3-particle-editor/blob/master/LICENSE)
4+
[![Build Status](https://secure.travis-ci.org/koreezgames/phaser3-particle-editor.svg?branch=master)](https://travis-ci.org/koreezgames/phaser3-particle-editor)
5+
[![codebeat badge](https://codebeat.co/badges/e3792494-1875-4826-be00-2124148b9287)](https://codebeat.co/projects/github-com-koreezgames-phaser3-particle-editor-master)
6+
[![Greenkeeper badge](https://badges.greenkeeper.io/koreezgames/phaser3-particle-editor.svg)](https://greenkeeper.io/)
7+
[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](https://github.com/koreezgames/phaser3-particle-editor/pulls)
8+
[![styled with prettier](https://img.shields.io/badge/styled_with-prettier-ff69b4.svg)](https://github.com/prettier/prettier)
9+
10+
This tool was designed to interactively create particle emitters using [Phaser](http://phaser.io)
11+
12+
View the editor [here](https://koreezgames.github.io/phaser3-particle-editor/).
13+
14+
![Showcase](https://raw.githubusercontent.com/koreezgames/phaser3-particle-editor/master/showcase.gif)
15+
16+
Key features:
17+
18+
- Blazing fast
19+
- No runtime needed
20+
- Easy to use
21+
22+
## Getting Started
23+
24+
First you want to get your project exported via [editor](https://koreezgames.github.io/phaser3-particle-editor/). You can do it by clicking on the menu button right next to the project name.
25+
26+
Exported project structure:
27+
28+
![Project](https://raw.githubusercontent.com/koreezgames/phaser3-particle-editor/master/project.png)
29+
30+
## Usage
31+
32+
```javascript
33+
var config = {
34+
type: Phaser.WEBGL,
35+
width: 800,
36+
height: 600,
37+
backgroundColor: '#262626',
38+
parent: 'phaser-example',
39+
scene: {
40+
preload: preload,
41+
create: create,
42+
},
43+
};
44+
45+
var game = new Phaser.Game(config);
46+
47+
function preload() {
48+
this.load.atlas('shapes', 'assets/shapes.png', 'assets/shapes.json');
49+
this.load.json('particle-effect', 'assets/particle-effect.json');
50+
}
51+
52+
function create() {
53+
this.add.particles('shapes', this.cache.json.get('particle-effect'));
54+
}
55+
```
56+
57+
## Contributing
58+
59+
The main purpose of this repository is to continue to evolve Phaser, making it easier to use. Development of Editor happens in the open on GitHub, and we are grateful to the community for contributing bugfixes and improvements. Read below to learn how you can take part in improving Editor.
60+
61+
### [Code of Conduct](https://github.com/koreezgames/phaser3-particle-editor/blob/master/CODE_OF_CONDUCT.md)
62+
63+
This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at http://contributor-covenant.org/version/1/4. Please read [the full text](https://github.com/koreezgames/phaser3-particle-editor/blob/master/CODE_OF_CONDUCT.md) so that you can understand what actions will and will not be tolerated.
64+
65+
### [Contributing Guide](https://github.com/koreezgames/phaser3-particle-editor/blob/master/CONTRIBUTING.md)
66+
67+
Read our [contributing guide](https://github.com/koreezgames/phaser3-particle-editor/blob/master/CONTRIBUTING.md) to learn about our development process, how to propose bugfixes and improvements, and how to build and test your changes to Editor.
68+
69+
## License
70+
71+
Editor is [MIT licensed](./LICENSE).

0 commit comments

Comments
 (0)