trinitrix/core
trinitrix
/
core
Archived
5
4
Fork 2
Code Issues 8 Pull Requests Packages Projects Releases Wiki Activity
This repository has been archived on 2024-05-26. You can view files and clone it, but cannot push or open issues or pull requests.
core/Cargo.toml

32 lines
996 B
TOML
Raw Normal View History

initial commit
2023-06-14 21:49:20 +00:00
[package]
name = "trinitrix"
version = "0.1.0"
edition = "2021"
feature (UI): implemented a login screen
2023-06-29 10:36:16 +00:00
license = "MIT"
initial commit
2023-06-14 21:49:20 +00:00
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
Feat(treewide): Add a feature based layout and repl subcommand Compiling the whole tui stack, just to debug the lua command line seems counterproductive to me. This allows to just compile the needed parts for a basic lua repl. As of yet the repl is just a mock-up, as the event handling can, as of right now, not easily be separated from the tui. To activate specific features add specify the on the cargo command line like this: ``` cargo run --features "cli tui" ``` or add them to the `default` feature set in the `Cargo.toml`.
2023-07-23 13:53:31 +00:00
[features]
Refactor(treewide): Remove the repl, reuse of e. handling is hard The event handling is deeply ingrained in the ui code, the commands are focused around the ui code, in short splitting of the event handling and command system from the ui is intentionally hard and in my opinion not really worth it right now.
2023-07-24 21:38:16 +00:00
default = ["tui"]
Feat(treewide): Add a feature based layout and repl subcommand Compiling the whole tui stack, just to debug the lua command line seems counterproductive to me. This allows to just compile the needed parts for a basic lua repl. As of yet the repl is just a mock-up, as the event handling can, as of right now, not easily be separated from the tui. To activate specific features add specify the on the cargo command line like this: ``` cargo run --features "cli tui" ``` or add them to the `default` feature set in the `Cargo.toml`.
2023-07-23 13:53:31 +00:00
tui = ["dep:tui", "dep:tui-textarea", "dep:crossterm", "dep:tokio-util", "dep:serde", "dep:indexmap"]
initial commit
2023-06-14 21:49:20 +00:00
[dependencies]
Feat(treewide): Add a feature based layout and repl subcommand Compiling the whole tui stack, just to debug the lua command line seems counterproductive to me. This allows to just compile the needed parts for a basic lua repl. As of yet the repl is just a mock-up, as the event handling can, as of right now, not easily be separated from the tui. To activate specific features add specify the on the cargo command line like this: ``` cargo run --features "cli tui" ``` or add them to the `default` feature set in the `Cargo.toml`.
2023-07-23 13:53:31 +00:00
clap = { version = "4.3.19", features = ["derive"] }
cli-log = "2.0"
feature (accounts): implemented login with username and password
2023-06-15 17:19:24 +00:00
anyhow = "1.0"
Feat(treewide): Add a feature based layout and repl subcommand Compiling the whole tui stack, just to debug the lua command line seems counterproductive to me. This allows to just compile the needed parts for a basic lua repl. As of yet the repl is just a mock-up, as the event handling can, as of right now, not easily be separated from the tui. To activate specific features add specify the on the cargo command line like this: ``` cargo run --features "cli tui" ``` or add them to the `default` feature set in the `Cargo.toml`.
2023-07-23 13:53:31 +00:00
matrix-sdk = "0.6"
Refactor(treewide): Remove the repl, reuse of e. handling is hard The event handling is deeply ingrained in the ui code, the commands are focused around the ui code, in short splitting of the event handling and command system from the ui is intentionally hard and in my opinion not really worth it right now.
2023-07-24 21:38:16 +00:00
tokio = { version = "1.29", features = ["macros", "rt-multi-thread", "io-std"] }
Feat(treewide): Add a feature based layout and repl subcommand Compiling the whole tui stack, just to debug the lua command line seems counterproductive to me. This allows to just compile the needed parts for a basic lua repl. As of yet the repl is just a mock-up, as the event handling can, as of right now, not easily be separated from the tui. To activate specific features add specify the on the cargo command line like this: ``` cargo run --features "cli tui" ``` or add them to the `default` feature set in the `Cargo.toml`.
2023-07-23 13:53:31 +00:00
# lua stuff
lua_macros = { path = "./lua_macros" }
Fix(treewide): Update codebase to new lua_macros api
2023-07-20 19:49:23 +00:00
mlua = { version = "0.8.9", features = ["lua54", "async", "send"] }
Feat(treewide): Add a feature based layout and repl subcommand Compiling the whole tui stack, just to debug the lua command line seems counterproductive to me. This allows to just compile the needed parts for a basic lua repl. As of yet the repl is just a mock-up, as the event handling can, as of right now, not easily be separated from the tui. To activate specific features add specify the on the cargo command line like this: ``` cargo run --features "cli tui" ``` or add them to the `default` feature set in the `Cargo.toml`.
2023-07-23 13:53:31 +00:00
once_cell = "1.18.0"
# tui feature specific parts
tui = {version = "0.19", optional = true}
tui-textarea = { version = "0.2", features = ["crossterm"], optional = true }
crossterm = { version = "0.25", optional = true }
tokio-util = { version = "0.7", optional = true }
serde = { version = "1.0", optional = true }
indexmap = { version = "2.0.0", optional = true }