2023-07-19 22:40:21 +00:00
|
|
|
# Design Philosophy
|
|
|
|
|
|
|
|
|
|
## Customizability
|
|
|
|
|
Trinitrix aims to be highly customizable.
|
2023-07-19 22:59:47 +00:00
|
|
|
The command API provides a customizazion method, which can be used by an initial config script or live from the intern cli by the user.
|
2023-07-19 22:40:21 +00:00
|
|
|
The command API should cover at least 90% of the possible configuration settings.
|
|
|
|
|
|
|
|
|
|
## Cross Platform
|
|
|
|
|
Trinitrix is cross platform.
|
2023-07-19 22:59:47 +00:00
|
|
|
Even if the targeted users are nerdy linux users xD.
|
2023-07-19 22:40:21 +00:00
|
|
|
This can be easily achieved by using only cross platform libraries such as `crossterm` or `tui`.
|
|
|
|
|
|
|
|
|
|
## Future Proof / Extensible
|
2023-07-19 22:59:47 +00:00
|
|
|
Modules and Interfaces should be designed in a way, that they're not limited to only use case.
|
|
|
|
|
They should be open for every usecase, that makes sense.
|
2023-07-19 22:40:21 +00:00
|
|
|
A good example is the command API, which is a unified way to interact with the application.
|
|
|
|
|
It can used via lua, but use cases like fetching commands using http are theoretically possible too.
|
