Author: mesyeti <mesyeti@mesyeti.uk>
new pages
wiki/dui.md | 5 +++++ | 0 wiki/good-software.md | 25 +++++++++++++++++++++++++ wiki/pages.md | 10 ++++------
diff --git a/wiki/dui.md b/wiki/dui.md new file mode 100644 index 0000000000000000000000000000000000000000..dab2c79dfb65b5eaed9fd9b705968712e8443518 --- /dev/null +++ b/wiki/dui.md @@ -0,0 +1,5 @@ +# DUI +DUI is a work-in-progress graphics library maintained and worked on my PQCraft. + +## Source +- <https://codeberg.org/non-bloat-collective/DUI> diff --git a/wiki/gl45rq.md b/wiki/gl45rq.md deleted file mode 100644 index fb507ee5d5887988f25b12eb83d0b8098db69677..0000000000000000000000000000000000000000 --- a/wiki/gl45rq.md +++ /dev/null @@ -1,2 +0,0 @@ -# gl45rw -stub diff --git a/wiki/gl45rw.md b/wiki/gl45rw.md new file mode 100644 index 0000000000000000000000000000000000000000..fb507ee5d5887988f25b12eb83d0b8098db69677 --- /dev/null +++ b/wiki/gl45rw.md @@ -0,0 +1,2 @@ +# gl45rw +stub diff --git a/wiki/good-software.md b/wiki/good-software.md new file mode 100644 index 0000000000000000000000000000000000000000..4da8567ebf0527eaea55cec1df48d2de0d0de87f --- /dev/null +++ b/wiki/good-software.md @@ -0,0 +1,25 @@ +# Good Software +This page is about what a good program should look like, and details the expected +standards for a non-bloat program. + +## Speed +A non-bloat program should be fast on computers made after the year 2004. These +computers are perfectly capable at running a lot of common computer software, +as long as it isn't bloated + +## Accessibility +A non-bloat program should be accessible. Not just in the way that the program +is accessible to people, like with disability accommodations, but also in the way +that the program is accessible to computers. + +Programs should be written in either C89 or C99. These are the most portable languages +ever, as C is usually available on whatever CPU architecture you're using. The only +case where another language can be used is for a server program, as long as the +client is perfectly accessible. Using C89 or C99 won't cause issues later on where +you want to support a certain CPU architecture but can't, because your compiler +is holding you back. + +Programs should be designed to be easily ported to other platforms. Do not rely +on non-portable libraries, or they will hold you back in the future. Create backends +for different parts of your software, like windowing or graphics, so you can easily +add new backends to support other hardware. diff --git a/wiki/pages.md b/wiki/pages.md index ba24ce8bb4b656b31398400e29eae6fe4890e805..7e724b455e6639952e8292d2ef4b6210e40bc45e 100644 --- a/wiki/pages.md +++ b/wiki/pages.md @@ -2,13 +2,11 @@ # Pages ## Main - [Home](/index.html) -## Individual projects +## Collective projects +- [DUI - Modular GUI library](/dui.html) + +## Associated projects - [Arkas Engine - Retro game engine](/arkas-engine.html) -- [Trinity Engine - Retro game engine](/trinity.html) - [PlatinumSrc - Retro game engine](/platinumsrc.html) -- [gl45rw Engine - Game engine](/gl45rw.html) - [PSCHS - PQCraft's Simple C HTTP Server](/pschs.html) - [Nitron - Operating system and VM](/nitron.html) - -## Group projects -Coming soon