mirror of
https://github.com/FliegendeWurst/cursive.git
synced 2024-11-12 12:13:08 +00:00
111 lines
2.7 KiB
Rust
111 lines
2.7 KiB
Rust
//! # Cursive
|
|
//!
|
|
//! [Cursive] is a [TUI] library - it lets you easily build rich interfaces
|
|
//! for use in a terminal.
|
|
//!
|
|
//! [Cursive]: https://github.com/gyscos/Cursive
|
|
//! [TUI]: https://en.wikipedia.org/wiki/Text-based_user_interface
|
|
//!
|
|
//! ## Getting started
|
|
//!
|
|
//! * Every application should start with a [`Cursive`](struct.Cursive.html)
|
|
//! object. It is the main entry-point to the library.
|
|
//! * A declarative phase then describes the structure of the UI by adding
|
|
//! views and configuring their behaviours.
|
|
//! * Finally, the event loop is started by calling
|
|
//! [`Cursive::run(&mut self)`](struct.Cursive.html#method.run).
|
|
//!
|
|
//! ## Views
|
|
//!
|
|
//! Views are the main components of a cursive interface.
|
|
//! The [`views`](./views/index.html) module contains many views to use in your
|
|
//! application; if you don't find what you need, you may also implement the
|
|
//! [`View`](view/trait.View.html) trait and build your own.
|
|
//!
|
|
//! ## Callbacks
|
|
//!
|
|
//! Cursive is callback-driven: it reacts to events generated by user input.
|
|
//!
|
|
//! During the declarative phase, callbacks are set to trigger on specific
|
|
//! events. These functions usually take a `&mut Cursive` argument, allowing
|
|
//! them to modify the view tree at will.
|
|
//!
|
|
//! ## Examples
|
|
//!
|
|
//! ```rust
|
|
//! extern crate cursive;
|
|
//!
|
|
//! use cursive::Cursive;
|
|
//! use cursive::views::TextView;
|
|
//!
|
|
//! fn main() {
|
|
//! let mut siv = Cursive::dummy();
|
|
//!
|
|
//! siv.add_layer(TextView::new("Hello World!\nPress q to quit."));
|
|
//!
|
|
//! siv.add_global_callback('q', |s| s.quit());
|
|
//!
|
|
//! siv.run();
|
|
//! }
|
|
//! ```
|
|
//!
|
|
//! ## Debugging
|
|
//!
|
|
//! The `Cursive` root initializes the terminal on creation, and do cleanups
|
|
//! on drop. While it is alive, printing to the terminal will not work
|
|
//! as expected, making debugging a bit harder.
|
|
//!
|
|
//! One solution is to redirect stderr to a file when running the application,
|
|
//! and log to it instead of stdout.
|
|
//!
|
|
//! Or you can use gdb as usual.
|
|
#![deny(missing_docs)]
|
|
|
|
// We use chan_signal to detect SIGWINCH.
|
|
// It's not how windows work, so no need to use that.
|
|
|
|
macro_rules! new_default(
|
|
($c:ty) => {
|
|
impl Default for $c {
|
|
fn default() -> Self {
|
|
Self::new()
|
|
}
|
|
}
|
|
}
|
|
);
|
|
|
|
pub mod traits;
|
|
|
|
pub mod event;
|
|
#[macro_use]
|
|
pub mod view;
|
|
|
|
#[macro_use]
|
|
pub mod utils;
|
|
|
|
pub mod align;
|
|
pub mod direction;
|
|
pub mod logger;
|
|
pub mod menu;
|
|
pub mod rect;
|
|
pub mod theme;
|
|
pub mod vec;
|
|
pub mod views;
|
|
|
|
// This probably doesn't need to be public?
|
|
mod cursive;
|
|
mod printer;
|
|
mod with;
|
|
mod xy;
|
|
|
|
mod div;
|
|
mod utf8;
|
|
|
|
pub mod backend;
|
|
|
|
pub use crate::cursive::{CbFunc, CbSink, Cursive, ScreenId};
|
|
pub use crate::printer::Printer;
|
|
pub use crate::vec::Vec2;
|
|
pub use crate::with::With;
|
|
pub use crate::xy::XY;
|