h44z/uibk_703807-Advanced-CXX
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Assignment 1: Clarify the combation of app + framework

Browse Source
This commit is contained in:
Alex Hirsch
2020-11-26 14:17:16 +01:00
parent 40fb2db8a4
commit eb0ea94898
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
assignment1/feedback.md
View File

@@ -211,10 +211,8 @@ Building the engine as a library is certainly a possibility, but I suggest keepi
. .
├── cmake/ ├── cmake/
├── docs/ ├── docs/
├── myapp1/ # Always use dedicated folders here. With this approach applications get bigger quickly. ├── myapp/ # Always use dedicated folders here. With this approach applications get bigger quickly.
│   └── myapp1.cpp │   └── myapp.cpp
├── myapp2/
│   └── myapp2.cpp
├── myframework/ ├── myframework/
│   ├── bar.cpp │   ├── bar.cpp
│   ├── bar.hpp │   ├── bar.hpp
@@ -233,4 +231,6 @@ This is a very open approach that may only fit some projects.
You'd then use `#include "myframework/foo.hpp"` for instance. You'd then use `#include "myframework/foo.hpp"` for instance.
You may of course build more than just one app; yet, the focus lies on the combination of app and framework.
Consider watching [John Romero's talk at 2016 GDC Europe](https://www.youtube.com/watch?v=E2MIpi8pIvY) regarding some paradigms to follow during development. Consider watching [John Romero's talk at 2016 GDC Europe](https://www.youtube.com/watch?v=E2MIpi8pIvY) regarding some paradigms to follow during development.