<buttonid="sidebar-toggle"class="icon-button"type="button"title="Toggle Table of Contents"aria-label="Toggle Table of Contents"aria-controls="sidebar">
<inputtype="search"id="searchbar"name="searchbar"placeholder="Search this book ..."aria-controls="searchresults-outer"aria-describedby="searchresults-header">
<p>TOMAS (<strong>To</strong>ny's <strong>Ma</strong>naged Operating <strong>S</strong>ystem) is a modular hobby operating system written in C# using the <ahref="https://github.com/CosmosOS/Cosmos">COSMOS</a> framework. It comes with a respective terminal emulator using for Core testing.</p>
<p>Both the kernel and terminal emulator will eventually support programs and plugins, respectfully. With the former allowing for running of native .NET executables and the latter Lua plugins, while taking advantage of the existing <ahref="./design/interfaces.html">interface</a> architecture.</p>
<li>With the help of ChatGPT, the <code>IProgram</code> interface has been rewritten to handle command line arguments. Being ChatGPT derived, it's still rough around the edges (not sure what to do with <code>IArguments</code> right now), but it's one hell of a jumping start!</li>
<li>Speaking of, the <ahref="https://github.com/tonytins/cstdotnet">CST parser</a> has been rewritten to finally support arguments with the help of ChatGPT too. While I could have always looked at FreeSO's implantation for reference, that code is just awful. It will be ported back upstream ASAP!</li>
<li>Split versioning systems between kernal and terminal
<ul>
<li>Calendar versioning, <code>YY.MINOR.MICRO</code>, for kernal</li>
<li>Semantic versioning for terminal</li>
</ul>
</li>
<li>If the file system is activate, system activity will be logged</li>
<li>Build number based on commit hash</li>
</ul>
<p>Due to the huge time skip and architectural changes, I've (retroactively) switched to calendar versioning with <code>v0.1</code> now known as <code>v20.1</code> as well.</p>
<li>Filesystem (based on the Cosmos Wiki <ahref="https://csos-guide-to-cosmos.fandom.com/wiki/Getting_Started_-_Materials_and_Setting_Up">guide</a>)</li>
<li>Semantic versioning</li>
<li>Replaced BasicApp with AboutApp</li>
<li>Removd TerminalCancelEventArgs and everything related to it</li>
<p>Although a hobby, I have wanted to test the idea of some sort of support policy for my projects. In my experience, it provides a nice fallback. For example, a bug in the unzipping process when I switched APIs in my former Blue Rose launcher and updater forced me to create an LTS out of a version that lacked the change while I searched for the cause of the problem. With the current development speed of COSMOS, a hypothetical LTS would possibly last one year.</p>
<!--
## Standard Edition
The Standard Edition of TOMAS is intended for general use and experimentation. It is provided on an "as is" basis, and no guarantees are made regarding its reliability or suitability for any particular purpose.
## Longhorn Edition
The Longhorn Edition of TOMAS is designed for use in enterprise scenarios. It is intended to adhere to the requirements for cybersecurity and the use of long-term support or enterprise-grade open source software.
<p>Since 19.1, TOMAS uses a modular interface design for writing and executing programs. At the moment, the operating system doesn't yet support loading assemblies that would take advantage of this API, but it is being looked into.</p>
<p><code>IProgram</code> is used to create the actual program while <code>IShell</code> executes the respective program from a dictionary. While still early in development, the approach has allowed for easy migration from one major release of COSMOS to another with little to no modifications of the code itself.</p>