https://github.com/bsgbryan/mintuts
The repo for all MinTuts tutorials
https://github.com/bsgbryan/mintuts
cg csharp discussion games hlsl inline-diff-comments mintuts-tutorials procedural procedural-generation procedural-programming procedural-terrain shaderlab tutorial tutorial-code tutorial-sourcecode tutorials unity unity3d
Last synced: 3 months ago
JSON representation
The repo for all MinTuts tutorials
- Host: GitHub
- URL: https://github.com/bsgbryan/mintuts
- Owner: bsgbryan
- License: mit
- Created: 2018-05-18T22:42:49.000Z (about 7 years ago)
- Default Branch: master
- Last Pushed: 2018-07-28T03:34:09.000Z (almost 7 years ago)
- Last Synced: 2025-02-10T03:46:14.970Z (4 months ago)
- Topics: cg, csharp, discussion, games, hlsl, inline-diff-comments, mintuts-tutorials, procedural, procedural-generation, procedural-programming, procedural-terrain, shaderlab, tutorial, tutorial-code, tutorial-sourcecode, tutorials, unity, unity3d
- Language: C++
- Size: 21.5 MB
- Stars: 1
- Watchers: 4
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
MinTuts
=======
Hi - thanks for stopping by! :smiley:
MinTuts are minute long tutorial videos. This is where you can get the code used in MinTuts tutorials.
Structure
=========
This repo follows a few rules
Branches
--------
Each MinTut gets its own branch. In a branch you will find all the commits making up that tutorial.
Comments
--------
MinTuts uses GitHub's inline diff comments instead of code comments. There are a few reasons for this:
1. inline diff comments never grow stale - since the comment is attached to a specific commit, the comment will always be relevant. Code comments are prone to growing stale as code bases evolve.
2. inline diff comments support Markdown - this makes them much easier to read, especially when they're densely packed with structured info.
3. inline diff comments don't get in the way of code - code comments can make reading code difficult, especially if there are a lot of them and/or they are long. Inline diff comments can be as plentiful and long as we want - they will never obscure or get in the way of the code they relate to.
4. inline diff comments encourage questions and discussion - building on point 3, because inline diff comments never get in the way of code we are free to use them as Q&A/discussion forums. Such activity only adds value to the codebase.
**_NOTE_** To view inline diff comments, simply click/tap on the the _commits_ nav item (_nead the top-left of the page_). You could also follow this [link](https://github.com/bsgbryan/MinTuts/commits/master) to view all the commits to the `master` branch. Commits that have a text bubble icon and number immediatly to the left of their clipboard icon have comments. Click/tap on the commit hash (_immediatly to the right of the clipboard icon_) to view that commit and its comments.
Notes
=====
* Unity and git have been setup according to [this](https://robots.thoughtbot.com/how-to-git-with-unity)
* This project was created in, and should only be run in, [Unity](https://store.unity.com/download?ref=personal) 2018.1.0f2 or newer