From 79f3b3353ea3036dd94d0771981647c44a1a14ec Mon Sep 17 00:00:00 2001 From: Sasha Koshka Date: Tue, 17 Jan 2023 17:36:11 -0500 Subject: [PATCH] Cool tomo facts in readme --- README.md | 23 ++++++++++++++++++++--- 1 file changed, 20 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 86d7a4f..c2f20a4 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,25 @@ # ![tomo](assets/banner.png) -Tomo is a GUI toolkit written in pure Go, designed to be minimalist, frugal, and -extendable. It is currently in early development, so some features may not work -as expected. +Please note: Tomo is in early development. Some features may not work properly, +and its API may change without notice. + +Tomo is a GUI toolkit written in pure Go. It is designed with these goals in +mind: + +1. Modularity: the core of Tomo is mostly composed of interfaces—and the +overwhelming majority of its code resides in pluggable modules. If you don't +need it, then dont import it—and you can be assured it won't be there. +2. Extendability: during the design of Tomo's API, use cases such as creating +custom backends, element, and layouts were given just as much importance as +normal application building. Your custom element is a first-class citizen. +3. Independence: Tomo is minimally dependent on code outside of the Go +standard library. Because of this, the file size of a compiled Tomo application +is typically very small. +4. Frugality: Tomo foregoes things like animations and anti-aliasing in order to +use a minimal amount of system resources without even having to touch the GPU. +5. Consistency: Tomo's design is not only consistent with itself, but also with +the Go standard library. If you've worked with Go in the past, Tomo will feel +pleasantly familliar. You can find out more about how to use it by visiting the examples directory, or pull up its documentation by running `godoc` within the repository. You can