From eb0ea948986977c5a78b26786307f33d89500903 Mon Sep 17 00:00:00 2001 From: Alex Hirsch Date: Thu, 26 Nov 2020 14:17:16 +0100 Subject: [PATCH] Assignment 1: Clarify the combation of app + framework --- assignment1/feedback.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/assignment1/feedback.md b/assignment1/feedback.md index 563bf51..36ba183 100644 --- a/assignment1/feedback.md +++ b/assignment1/feedback.md @@ -211,10 +211,8 @@ Building the engine as a library is certainly a possibility, but I suggest keepi . ├── cmake/ ├── docs/ -├── myapp1/ # Always use dedicated folders here. With this approach applications get bigger quickly. -│   └── myapp1.cpp -├── myapp2/ -│   └── myapp2.cpp +├── myapp/ # Always use dedicated folders here. With this approach applications get bigger quickly. +│   └── myapp.cpp ├── myframework/ │   ├── bar.cpp │   ├── 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 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.