| ... | ... | @@ -165,4 +165,12 @@ For the usage of cluster events in C++, see [Cluster events in C++](Home/Cluster |
|
|
|
The editor module [`RWTHVRToolkitEditor`](https://git-ce.rwth-aachen.de/vr-vis/VR-Group/unreal-development/plugins/rwth-vr-toolkit/-/tree/dev/5.3/Source/RWTHVRToolkitEditor?ref_type=heads) in general contains features to enhace the editor experience, such as visualizers for certain components.
|
|
|
|
Currently, no such features are implemented.
|
|
|
|
|
|
|
|
# [Development](Home/Development) |
|
|
\ No newline at end of file |
|
|
|
# [Development](Home/Development)
|
|
|
|
|
|
|
|
Please read the [Development](Home/Development) section carefully. As a summary:
|
|
|
|
|
|
|
|
- Use your own forks for developing features to not spam branches on this repository, keep it limited to release and dev branches.
|
|
|
|
- Use conventional commit syntax when commiting to improve readability for others: `<type>(scope): description`
|
|
|
|
- Keep commits encapsulated to one change/feature. Don't try to put all your changes into one commit, it makes the history and git blame absolutely unreadable, and git bisect doesn't work as well for debugging.
|
|
|
|
- Commit changes to shared blueprints early and put up PRs regarding them early. The longer they sit, the more nightmareish merging will become.
|
|
|
|
- Document your features both in code and in the Wiki. |
|
|
\ No newline at end of file |
