taardal / storytime Goto Github PK

Add ResourceManager class to load assets like shaders, textures and more.

Change as many dependencies as possible to git submodules

Problem
Storytime has to be included as a CMake subdirectory for includes in include/Storytime.h to work.

Preferred solution
A public inlude file so that Storytime can be used as a library by simply adding that file to the include path and linking against it.

• Make objects in engine into refs
  • WONTFIX: Unnecessary and retains complete control over creation/destruction
• Refactor formatting & naming conventions

Currently, the CMake project needs to be reloaded for resources to be added to build-folder. The CMake project is NOT reloaded when running project which is not ideal when f.ex. editing shaders.

Add "editor" project to build the engine workflow using imgui

https://onqtam.com/programming/2019-12-20-pch-unity-cmake-3-16/

actions/starter-workflows#53

• Add statistics to renderer to track number of vertices, indices etc.
• Show statistics on ImGUI window

Implement the humble beginnings of an Entity Componen System.

• Add EnTT library
• Add entity class that manages components (with help from scene)
• Add a scene class that manages entities

Use the docking-version of ImGUI

• Add ImGUI library
• Add ImGUI render callbacks to layers

Add textures to quads and subsequently batch rendering

Description
I suspect the current use of logging tags (ST_TAG), while really nice, is not optimal for performance and should therefore be profiled somehow.

Prerequisites

• Profiling tools

Possible solutions

• Convert tags to members
  • This would probably allow me to remove, or at least stop using, the logging macros
  • Could probably remove the tag macro as well if it was converted into a struct? Or can just use the Tag-function in the initializer?

Add categories to events (using BIT?)

• Load from file
• Add more logging
• Use string_view

Alternatives

• Catch2+FakeIt
• GoogleTest+GoogleMock

• Move main function from sandbox to storytime. Get config from client by having client define external getConfig function like getApplication.
• Copy client assets into engine build folder post build
• Delete existing build-folder before new builds to clean existing assets (or overwrite files during build)