core Directory Reference

Files
file	asserts.h [code]
	This file contains assertion functions to be used throughout the codebase.
file	clock.h [code]
	This file contains structures and functions for the engine's clock.
file	console.h [code]
	Contains the console system, which disperses all logging to registered consumers as well as handles registered command inputs.
file	engine.h [code]
	This file contains structures and logic pertaining to the overall engine itself. The engine is responsible for managing both the platform layers as well as all systems within the engine.
file	event.h [code]
	This file contains structures and functions specific to the event system. Events are a mechenism that allows the developer to send and recieve data at critical points in the execution of the application in a non- coupled way. For now, this follows a simple pub-sub model of event transmission.
file	frame_data.h [code]
file	identifier.h [code]
	Contains a system for creating numeric identifiers.
file	input.h [code]
	This file contains everything having to do with input on deskop environments from keyboards and mice. Gamepads and touch controls will likely be handled separately at a future date.
file	keymap.h [code]
	This file contains the structures and functions required to implement keymaps and keybindings, used to translate keyboard input events to events and/or call bound functions automatically. Keymaps replace the need for checks of key states in that they will instead invoke callback functions instead. Maps will be added onto a stack, where bindings are replaced along the way. For example, if the base keymap defines the "escape" key as an application quit, then another keymap added on re-defines the key to nothing while adding a new binding for "a", then "a"'s binding will work, and "escape" will do nothing. If "escape" were left undefined in the second keymap, the original mapping is left unchanged. Maps are pushed/popped as expected on a stack.
file	kmemory.h [code]
	This file contains the structures and functions of the memory system. This is responsible for memory interaction with the platform layer, such as allocations/frees and tagging of memory allocations.
file	kmutex.h [code]
file	kstring.h [code]
	This file contains a basic C string handling library.
file	kthread.h [code]
file	kvar.h [code]
	A file that contains the KVar system. KVars are global variables that are dynamically created and set/used within the engine and/or application, and are accessible from anywhere.
file	logger.h [code]
	This file contains structures and logic pertaining to the logging system.
file	metrics.h [code]
file	systems_manager.h [code]
	Contains logic for the management of various engine systems, which are in turn registered with this manager whose lifecycle is then automatically managed thereafter.
file	uuid.h [code]