mirror of
https://github.com/Ed94/HandmadeHero.git
synced 2025-07-01 11:21:05 -07:00
Day 12 complete
This commit is contained in:
@ -2,3 +2,11 @@
|
||||
|
||||
Architecture discussion was great. Did some diagramming of it.
|
||||
|
||||
I'm going to use a 3 layer approach to the architecture:
|
||||
|
||||
* Platform
|
||||
* Engine
|
||||
* Game (Handmade)
|
||||
|
||||
It will be style 2 so they each will provide a service to the layer below it and platform will provide an API to both engine and game.
|
||||
|
||||
|
13
docs/Day 012.md
Normal file
13
docs/Day 012.md
Normal file
@ -0,0 +1,13 @@
|
||||
# Day 12
|
||||
|
||||
This day was a mess to follow along.
|
||||
|
||||
> Always write the usage code first if you can, when designing something like an API.
|
||||
|
||||
Casey decided to do some heavy hits the audio (makes sense) due to the use of DirectSound.
|
||||
I'm going to preserve his implmentation as is for the most part since I rather keep things simple so that this project actually gets done.
|
||||
|
||||
> Only introduce added complexity when you need it.
|
||||
|
||||
There are two reasons you allow for a more complex interface, you ***NEED*** the feature. It actually is required for the project to have for the UX to preserve the user-level features. Or, there is a performance bottleneck that you need to address.
|
||||
|
Reference in New Issue
Block a user