||11 months ago|
|demo||11 months ago|
|libs||11 months ago|
|src||11 months ago|
|.gitignore||11 months ago|
|.gitmodules||11 months ago|
|LICENSE||12 months ago|
|Makefile||11 months ago|
|README.md||11 months ago|
SurRender is an attempt to create an abstract rendering engine for rendering 2D and 3D scenes in C.
As SurRender itself does not do any window creation and intends to be as open-ended as possible, it could potentially be used for the following ideas:
- A browser engine
- A 2D/3D game engine
- Scientific purposes?
- A tool for creating user interfaces
- A desktop window manager
Many features are currently unfinished. We keep track of all of these unfinished features in the issues tab if you're interested in helping us finish them.
Right now, SurRender is not very useful. 2D functions are partially completed, but 2D scenes and 3D scenes are completely missing. 2D ought to be fairly easy to implement, but 3D will be immensely difficult, and will require lots of help. We plan to allow for the use of multiple 3D rendering techniques, including both software rendering and OpenGL.
If you'd like to contribute, you will need to set up the build environment. To do this...
git clone https://git.lotte.link/naphtha/SurRender.git cd SurRender* ./build-deps.sh
./build-deps.sh to update all dependencies, build them and then automatically build SurRender itself and its test code. The test binary is produced as
In order to use SurRender, you'll need a few dependencies.
- SDL2 (You will need to install the *-dev/*-devel packages for it, as you will need both the library itself and its headers.)
stb_image.hfrom nothings/stb (bundled with SurRender)
- naphtha/radix (bundled with SurRender as a Git submodule)
When contributing to the project, keep these ideas in mind:
- Always think of ways you could improve the performance of your code.
- Try to make it as readable as possible, but not in such a way that it becomes ugly.
- Your code should be easy to use, but not in such a way that performance is crippled.
- Remember that this project is intended to be used by actual humans, for actual projects. Make sure your contributions are generally secure, easy to understand, fast and have a generally positive effect on the project.
Here's a generally useful document outlining how your code should be formatted, although we don't follow all of the points outlined there (for example, we use 4-space indentation, not 8-space. Our code would probably look just fine with 8-space indentation, but 4-space just looks better to me. It's personal preference. Don't start wars over it.)
If your code doesn't quite follow these guidelines but you'd still like to make a pull request, that's fine! We'll take a look at what you've written and help you fix parts of it for you if needed.
We also don't just need help programming - we also need people to test for bugs, assess what could be made easier to use, and so on.
Bugs, feature requests and general issues
Please post any bugs and feature requests under the issues tab. We'll help you when we can, and investigate as many bugs as possible. We're also always looking for feature suggestions and ideas on how things could be changed.