2025-02-03 18:55:26 +00:00
|
|
|
<!doctype html>
|
|
|
|
|
<html>
|
|
|
|
|
<head>
|
|
|
|
|
<title>Townengine Wiki : About Townengine</title>
|
|
|
|
|
<link rel="stylesheet" href="style.css">
|
|
|
|
|
</head>
|
|
|
|
|
<body>
|
2025-02-04 04:32:25 +00:00
|
|
|
<h1 style="margin-bottom:0in;">T1. About Townengine</h1>
|
2025-02-03 18:55:26 +00:00
|
|
|
<a href="index.html">Go back
|
2025-02-04 04:32:25 +00:00
|
|
|
<p><a name="introduction"></a><strong>T1.1 </strong><strong>Introduction</strong>
|
2025-02-03 18:55:26 +00:00
|
|
|
<blockquote>
|
2025-02-03 19:15:46 +00:00
|
|
|
<p>Townengine, {twn}, is an opinionated game development framework designed around ideas of simplicity, managed state,
|
2025-02-03 21:31:15 +00:00
|
|
|
care for old devices, portability, language agnosticism, use-case orientation, iterability and low latency.
|
2025-02-03 18:55:26 +00:00
|
|
|
<p><b>Simplicity.</b> It makes assumptions that trickle down to your game code. There's no delta between frames, nor resolution change.
|
|
|
|
|
Textures have constant known size, not requiring scaling.
|
|
|
|
|
<p><b>Managed state.</b> Designed around this we can provide hot reloading at any point,
|
|
|
|
|
serialization for save files and debug dumps, as well as synchronization over network, without any user code.
|
|
|
|
|
Every frame apparent engine state is cleared, which removes another variable for you to handle, - when to initialize.
|
2025-02-03 22:13:38 +00:00
|
|
|
There's no need for you to call `LoadImage()` of sorts before using it in render, you just pass filepaths around.
|
|
|
|
|
Input is initialized anew each frame, making rebinds trivial.
|
2025-02-03 18:55:26 +00:00
|
|
|
<p><b>Care for old devices.</b> It's to both to provide it for more people, who otherwise might not be able to make games they want,
|
|
|
|
|
as well as to have restrictions that constitute in desired aesthetic. Graphics capabilities are limited, but
|
|
|
|
|
what is present, - is heavily optimized. It is rather different from performance-driven approach that tries to take
|
|
|
|
|
advantage of the latest hardware and features, sacrificing both the reach and portability.
|
|
|
|
|
<p><b>Portability.</b> Written in C11 with all dependencies being in C, it's possible to compile it to most platforms.
|
|
|
|
|
SDL2 is at the center and you cannot get better than this. Default graphics API is OpenGL 1.5 with extension detection.
|
|
|
|
|
As an example, it builds and runs on Haiku OS with LLVMpipe.
|
|
|
|
|
<p><b>Language agnosticism.</b> API is restricted to not require much glue.
|
|
|
|
|
Language interpreters don't need to be part of the engine itself. Anything with C ABI support can link to it.
|
|
|
|
|
<p><b>Use-case orientation.</b> It doesn't try to be a yet another general purpose engine conquering all and nothing.
|
|
|
|
|
Instead we seek particular use cases and implement the most essential parts.
|
|
|
|
|
<p><b>Iterability.</b> Defaults provided for most of the API, making initial code faster to spring.
|
|
|
|
|
Hot reloading for both assets and code.
|
2025-02-03 21:31:15 +00:00
|
|
|
<p><b>Low latency.</b> Care is given to various incarnations of feared latency. Engine is fast to build, allowing for low commitment patches.
|
|
|
|
|
Startup time is profiled and optimized. Streaming is used as much as possible for asset load.
|
2025-02-03 18:55:26 +00:00
|
|
|
</blockquote>
|
2025-02-04 04:32:25 +00:00
|
|
|
<p><a name="wiki"></a><strong>T1.2 </strong><strong>Wiki</strong>
|
2025-02-03 19:15:46 +00:00
|
|
|
<blockquote>
|
|
|
|
|
<p>Purpose of this wiki is to collect information on various usages of {twn} across the genres, FAQ style.
|
|
|
|
|
You're welcomed to contribute to it. It's written in HTML so basic you can edit it by hand.
|
2025-02-03 22:13:38 +00:00
|
|
|
Just check <a href="template.html">template.html</a>.
|
2025-02-03 19:15:46 +00:00
|
|
|
</blockquote>
|
2025-02-03 18:55:26 +00:00
|
|
|
</body>
|
|
|
|
|
</html>
|
