v1.1.0 - QoL Update

Description

I wanted to release StateMachine in this release, but other things got developed. As completed GitHub issues continued to accumulate, I realized there are already plenty of ready changes to make up a release. There are still many open GitHub issues to constitute many more releases, so those will keep coming. StateMachine is soon to arrive, motivated by me wanting, badly, to start working on netset, finally.

Changes

• Redesign Time::Invocation as a safe RAII callback function wrapper (#129).
• Add Collider::ByTextureForeground() (#128).
• Add no-game-loop mode (#141).
• Add Camera::RenderDrawPrint() and UI::RenderClearDrawPrint() (#143).
• Change running directory of the "simpleplatform" game example to the Git repository's root (FAQ: "How to run the game examples?").
• Rename CallbacksGroup to CallbackGroup.
• Deprecate Windows port (#149, FAQ: "How to build KTech (with Premake)?").
• Reconfigure Doxygen so working directory is root and output is build/doxygen/ (#139).
• Fix Doxygen GitHub Action not listing namespaces (#140).
• Fix some Doxygen briefs not being processed as briefs.
• Add Doxygen Awesome CSS theme.
• Add KTech logo, icon, brief and version to Doxygen.
• Fix Texture::Print() not printing simple Textures and not being marked const (#146).
• Add Texture::Transform(), which replaces the previous transformation functions like Texture::SetAlpha() (#147).
• Fix Texture::Resize() setting value of simple Textures.
• Write FAQ: "What is the Git workflow here?".
• Update years in copyright notices (#138).

For the full changelog: v1.0.1...v1.1.0.

v1.0.1 - Windows Port Hotfix

Fixes

• Windows port:
  • Invalid use of the chrono library.
  • windows.h macros overlapping library code.

v1.0.0 - First Production Release

After 3 or so years of inconsistent development, I decided it's time to release KTech's first production release: version 1.0.0.

This release includes:

• Doxygen API reference
• Tutorial
• develop Git branch
• Code overhaul (maintainability, readability, modernity, performance)

Following this first release, updates will enter the master branch after being tested for stability in the develop branch, in the form of more releases and incrementing versions.

Apart from stability, this model will help with managing library code in game projects. More specifically, it will enhance usability of Git submodules.

Until now, there was no need for this model. Instead, features were developed in topic branches, and were merged on completion with the master branch immediately. This satisfied the GitHub issues I made, which were the only demand for development.

Now I am intending to restart and open the development of netset (my KTech game), which makes stability and distinct library versions desired traits.

Version 1.1.0 is already planned, which will introduce StateMachine (a user interface utility, see issue #106). I initially wanted to have this feature in this release, but due to a limited time frame, it will see the light of day further on, as stable and refined.