forked from trinitrix/core
17 lines
792 B
Markdown
17 lines
792 B
Markdown
|
# Design Philosophy
|
||
|
|
|
||
|
|
## Customizability
|
||
|
|
Trinitrix aims to be highly customizable.
|
||
|
|
The command API provides a customizazion method, can be used by an initial config script and live by the user.
|
||
|
|
The command API should cover at least 90% of the possible configuration settings.
|
||
|
|
|
||
|
|
## Cross Platform
|
||
|
|
Trinitrix is cross platform.
|
||
|
|
Even if the targeted user group are nerdy linux users.
|
||
|
|
This can be easily achieved by using only cross platform libraries such as `crossterm` or `tui`.
|
||
|
|
|
||
|
|
## Future Proof / Extensible
|
||
|
|
Modules and Interfaces should be designed in a way, that they're not limited to one use case.
|
||
|
|
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.
|