This repository has been archived by the owner on Dec 8, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #69 from fusionengine-org/dev
V5
- Loading branch information
Showing
101 changed files
with
3,395 additions
and
1,304 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,17 +1,72 @@ | ||
# Contributing | ||
# Contributing rules | ||
We are happy and welcome if you want to contribute to fusion engine. But please consider a few details before continuing: | ||
- Branch: Please when working on your fork, work in the dev branch, because we only will accept commits to the dev branch. It will later be released with the next version of fusion. | ||
- Explain: Please explain why this should be considered and merged. That will make our life easier. | ||
- Test: Please test your code before even opening a new pull request. | ||
- Documentation: Please, if your adding something new, like a feature, please document everything. | ||
- Format: Please, run black for formatting of the code. | ||
1. Branch: Please when working on your fork, work in the dev branch, because we only will accept commits to the dev branch. It will later be released with the next version of fusion. | ||
2. Explain: Please explain why this should be considered and merged. That will make our life easier. | ||
3. Test: Please test your code before even opening a new pull request. | ||
4. Documentation: Please, if your adding something new, like a feature, please document everything. | ||
5. Format: Please, run black for formatting of the code. | ||
|
||
## Not following these rules | ||
If we see a pull request that doesn't follow these rules, we will tell you that, and close the pull request. | ||
We allow you to re-open a new pull request, but we expect you to have your code fixed. | ||
So make sure that you followed [the rules](#contributing-rules) | ||
|
||
## Some technologies we are using | ||
- PDM: We are using pdm for our main interaction with the library. | ||
- pyproject.toml: Pythons way for setting up a project. A replacement for setup.py | ||
- pygame-ce, pygame_gui and pymunk: We are using all three of these libraries to develop fusion engine. | ||
- pygame-ce: Used for windowing and events | ||
- PyOpenGL: Used for rendering everything | ||
- pillow (PIL): Used for loading images for PyOpenGL | ||
- pymunk: Will be used for physics | ||
- black: We are using black to format code | ||
|
||
## How to setup the work environment | ||
If you want to contribute, you got to setup the work environment, so you can develop fusion the right way. First, install PDM using pip: | ||
```bash | ||
pip install --user pdm | ||
``` | ||
PDM will manage everything for us, like virtual enviorments, packages and scripts. | ||
|
||
Then, fork [the repository](https://github.com/fusionengine-org/fusion-engine) to your profile. | ||
|
||
Then, clone your forked github repository: | ||
```bash | ||
git clone https://github.com/_your_username_/fusion-engine.git | ||
cd fusion-engine | ||
``` | ||
Then, change the branch to the dev branch to follow rule #1: | ||
```bash | ||
git checkout dev | ||
``` | ||
|
||
After that we need to run a special PDM command for creating the venv with the dev dependencies: | ||
```bash | ||
pdm install --dev | ||
``` | ||
This will create a .venv, with all dependencies needed and will install a editable version of fusion engine. This will have the same effect as `pip install -e .`. | ||
|
||
To test if it works properly, run one of the example using PDM: | ||
```bash | ||
pdm run example1 | ||
``` | ||
|
||
If you want to test documentation code, run the mkdocs command for starting a local server with the documentation. Run it with: | ||
```bash | ||
pdm run docs | ||
``` | ||
|
||
If you want to run some specific files, then just run: | ||
```bash | ||
pdm run your_file.py | ||
``` | ||
|
||
## Pull Request | ||
If you're ready with your changes, then you must follow a few steps before pull requesting. | ||
First, run black using PDM to format your code: | ||
```bash | ||
pdm run lint | ||
``` | ||
|
||
Then make sure your pull request code works without erroring and you followed the [contribution rules](#contributing-rules) | ||
|
||
After all of this, you can create a pull request and one of our main organisation members will look at it. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,4 @@ | ||
--- | ||
hide: | ||
- navigation | ||
--- | ||
|
||
|
||
## V3 Todo/Changelog | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
# Version 5 Todo/Changelog | ||
|
||
## V5 | ||
- [ ] Docs cleanup | ||
- [ ] New color system | ||
- [ ] Optimised font drawing |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
--- | ||
hide: | ||
- navigation | ||
--- | ||
|
||
|
||
# Getting started with fusion | ||
Welcome to fusion engine. If you're here, that means your interested in fusion. Here is a quick example how to setup fusion engine | ||
|
||
## 💻 Setting up | ||
|
||
To install it run this: | ||
|
||
```bash | ||
pip install fusion-engine | ||
``` | ||
|
||
Then import: | ||
|
||
```python | ||
import fusionengine as fusion | ||
``` | ||
And your done! | ||
|
||
## Next step | ||
After this, you can head into the section tutorials or wiki, to learn more about fusion engine. Have fun! | ||
|
||
- [Tutorials](v5/tutorials/setup.md) | ||
- [Wiki](v5/wiki/window.md) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.