2024-08-06 08:10:58 +00:00
|
|
|
//! # [Ratatui] `BarChart` example
|
|
|
|
//!
|
|
|
|
//! The latest version of this example is available in the [examples] folder in the repository.
|
|
|
|
//!
|
|
|
|
//! Please note that the examples are designed to be run against the `main` branch of the Github
|
|
|
|
//! repository. This means that you may not be able to compile with the latest release version on
|
|
|
|
//! crates.io, or the one that you have installed locally.
|
|
|
|
//!
|
|
|
|
//! See the [examples readme] for more information on finding examples that match the version of the
|
|
|
|
//! library you are using.
|
|
|
|
//!
|
2024-08-21 18:35:08 +00:00
|
|
|
//! [Ratatui]: https://github.com/ratatui/ratatui
|
|
|
|
//! [examples]: https://github.com/ratatui/ratatui/blob/main/examples
|
|
|
|
//! [examples readme]: https://github.com/ratatui/ratatui/blob/main/examples/README.md
|
2024-08-06 08:10:58 +00:00
|
|
|
|
|
|
|
use std::iter::zip;
|
|
|
|
|
|
|
|
use color_eyre::Result;
|
|
|
|
use ratatui::{
|
feat(terminal): Add ratatui::init() and restore() methods (#1289)
These are simple opinionated methods for creating a terminal that is
useful to use in most apps. The new init method creates a crossterm
backend writing to stdout, enables raw mode, enters the alternate
screen, and sets a panic handler that restores the terminal on panic.
A minimal hello world now looks a bit like:
```rust
use ratatui::{
crossterm::event::{self, Event},
text::Text,
Frame,
};
fn main() {
let mut terminal = ratatui::init();
loop {
terminal
.draw(|frame: &mut Frame| frame.render_widget(Text::raw("Hello World!"), frame.area()))
.expect("Failed to draw");
if matches!(event::read().expect("failed to read event"), Event::Key(_)) {
break;
}
}
ratatui::restore();
}
```
A type alias `DefaultTerminal` is added to represent this terminal
type and to simplify any cases where applications need to pass this
terminal around. It is equivalent to:
`Terminal<CrosstermBackend<Stdout>>`
We also added `ratatui::try_init()` and `try_restore()`, for situations
where you might want to handle initialization errors yourself instead
of letting the panic handler fire and cleanup. Simple Apps should
prefer the `init` and `restore` functions over these functions.
Corresponding functions to allow passing a `TerminalOptions` with
a `Viewport` (e.g. inline, fixed) are also available
(`init_with_options`,
and `try_init_with_options`).
The existing code to create a backend and terminal will remain and
is not deprecated by this approach. This just provides a simple one
line initialization using the common options.
---------
Co-authored-by: Orhun Parmaksız <orhunparmaksiz@gmail.com>
2024-08-22 12:16:35 +00:00
|
|
|
crossterm::event::{self, Event, KeyCode, KeyEventKind},
|
2024-08-11 00:43:13 +00:00
|
|
|
layout::{Constraint, Direction, Layout},
|
|
|
|
style::{Color, Style, Stylize},
|
|
|
|
text::Line,
|
2024-08-06 08:10:58 +00:00
|
|
|
widgets::{Bar, BarChart, BarGroup, Block},
|
feat(terminal): Add ratatui::init() and restore() methods (#1289)
These are simple opinionated methods for creating a terminal that is
useful to use in most apps. The new init method creates a crossterm
backend writing to stdout, enables raw mode, enters the alternate
screen, and sets a panic handler that restores the terminal on panic.
A minimal hello world now looks a bit like:
```rust
use ratatui::{
crossterm::event::{self, Event},
text::Text,
Frame,
};
fn main() {
let mut terminal = ratatui::init();
loop {
terminal
.draw(|frame: &mut Frame| frame.render_widget(Text::raw("Hello World!"), frame.area()))
.expect("Failed to draw");
if matches!(event::read().expect("failed to read event"), Event::Key(_)) {
break;
}
}
ratatui::restore();
}
```
A type alias `DefaultTerminal` is added to represent this terminal
type and to simplify any cases where applications need to pass this
terminal around. It is equivalent to:
`Terminal<CrosstermBackend<Stdout>>`
We also added `ratatui::try_init()` and `try_restore()`, for situations
where you might want to handle initialization errors yourself instead
of letting the panic handler fire and cleanup. Simple Apps should
prefer the `init` and `restore` functions over these functions.
Corresponding functions to allow passing a `TerminalOptions` with
a `Viewport` (e.g. inline, fixed) are also available
(`init_with_options`,
and `try_init_with_options`).
The existing code to create a backend and terminal will remain and
is not deprecated by this approach. This just provides a simple one
line initialization using the common options.
---------
Co-authored-by: Orhun Parmaksız <orhunparmaksiz@gmail.com>
2024-08-22 12:16:35 +00:00
|
|
|
DefaultTerminal, Frame,
|
2024-08-06 08:10:58 +00:00
|
|
|
};
|
|
|
|
|
feat(terminal): Add ratatui::init() and restore() methods (#1289)
These are simple opinionated methods for creating a terminal that is
useful to use in most apps. The new init method creates a crossterm
backend writing to stdout, enables raw mode, enters the alternate
screen, and sets a panic handler that restores the terminal on panic.
A minimal hello world now looks a bit like:
```rust
use ratatui::{
crossterm::event::{self, Event},
text::Text,
Frame,
};
fn main() {
let mut terminal = ratatui::init();
loop {
terminal
.draw(|frame: &mut Frame| frame.render_widget(Text::raw("Hello World!"), frame.area()))
.expect("Failed to draw");
if matches!(event::read().expect("failed to read event"), Event::Key(_)) {
break;
}
}
ratatui::restore();
}
```
A type alias `DefaultTerminal` is added to represent this terminal
type and to simplify any cases where applications need to pass this
terminal around. It is equivalent to:
`Terminal<CrosstermBackend<Stdout>>`
We also added `ratatui::try_init()` and `try_restore()`, for situations
where you might want to handle initialization errors yourself instead
of letting the panic handler fire and cleanup. Simple Apps should
prefer the `init` and `restore` functions over these functions.
Corresponding functions to allow passing a `TerminalOptions` with
a `Viewport` (e.g. inline, fixed) are also available
(`init_with_options`,
and `try_init_with_options`).
The existing code to create a backend and terminal will remain and
is not deprecated by this approach. This just provides a simple one
line initialization using the common options.
---------
Co-authored-by: Orhun Parmaksız <orhunparmaksiz@gmail.com>
2024-08-22 12:16:35 +00:00
|
|
|
fn main() -> Result<()> {
|
|
|
|
color_eyre::install()?;
|
|
|
|
let terminal = ratatui::init();
|
|
|
|
let app_result = App::new().run(terminal);
|
|
|
|
ratatui::restore();
|
|
|
|
app_result
|
|
|
|
}
|
2024-08-06 08:10:58 +00:00
|
|
|
|
|
|
|
const COMPANY_COUNT: usize = 3;
|
|
|
|
const PERIOD_COUNT: usize = 4;
|
|
|
|
|
|
|
|
struct App {
|
|
|
|
should_exit: bool,
|
|
|
|
companies: [Company; COMPANY_COUNT],
|
|
|
|
revenues: [Revenues; PERIOD_COUNT],
|
|
|
|
}
|
|
|
|
|
|
|
|
struct Revenues {
|
|
|
|
period: &'static str,
|
|
|
|
revenues: [u32; COMPANY_COUNT],
|
|
|
|
}
|
|
|
|
|
|
|
|
struct Company {
|
|
|
|
short_name: &'static str,
|
|
|
|
name: &'static str,
|
|
|
|
color: Color,
|
|
|
|
}
|
|
|
|
|
|
|
|
impl App {
|
|
|
|
const fn new() -> Self {
|
|
|
|
Self {
|
|
|
|
should_exit: false,
|
|
|
|
companies: fake_companies(),
|
|
|
|
revenues: fake_revenues(),
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
feat(terminal): Add ratatui::init() and restore() methods (#1289)
These are simple opinionated methods for creating a terminal that is
useful to use in most apps. The new init method creates a crossterm
backend writing to stdout, enables raw mode, enters the alternate
screen, and sets a panic handler that restores the terminal on panic.
A minimal hello world now looks a bit like:
```rust
use ratatui::{
crossterm::event::{self, Event},
text::Text,
Frame,
};
fn main() {
let mut terminal = ratatui::init();
loop {
terminal
.draw(|frame: &mut Frame| frame.render_widget(Text::raw("Hello World!"), frame.area()))
.expect("Failed to draw");
if matches!(event::read().expect("failed to read event"), Event::Key(_)) {
break;
}
}
ratatui::restore();
}
```
A type alias `DefaultTerminal` is added to represent this terminal
type and to simplify any cases where applications need to pass this
terminal around. It is equivalent to:
`Terminal<CrosstermBackend<Stdout>>`
We also added `ratatui::try_init()` and `try_restore()`, for situations
where you might want to handle initialization errors yourself instead
of letting the panic handler fire and cleanup. Simple Apps should
prefer the `init` and `restore` functions over these functions.
Corresponding functions to allow passing a `TerminalOptions` with
a `Viewport` (e.g. inline, fixed) are also available
(`init_with_options`,
and `try_init_with_options`).
The existing code to create a backend and terminal will remain and
is not deprecated by this approach. This just provides a simple one
line initialization using the common options.
---------
Co-authored-by: Orhun Parmaksız <orhunparmaksiz@gmail.com>
2024-08-22 12:16:35 +00:00
|
|
|
fn run(mut self, mut terminal: DefaultTerminal) -> Result<()> {
|
2024-08-06 08:10:58 +00:00
|
|
|
while !self.should_exit {
|
feat(terminal): Add ratatui::init() and restore() methods (#1289)
These are simple opinionated methods for creating a terminal that is
useful to use in most apps. The new init method creates a crossterm
backend writing to stdout, enables raw mode, enters the alternate
screen, and sets a panic handler that restores the terminal on panic.
A minimal hello world now looks a bit like:
```rust
use ratatui::{
crossterm::event::{self, Event},
text::Text,
Frame,
};
fn main() {
let mut terminal = ratatui::init();
loop {
terminal
.draw(|frame: &mut Frame| frame.render_widget(Text::raw("Hello World!"), frame.area()))
.expect("Failed to draw");
if matches!(event::read().expect("failed to read event"), Event::Key(_)) {
break;
}
}
ratatui::restore();
}
```
A type alias `DefaultTerminal` is added to represent this terminal
type and to simplify any cases where applications need to pass this
terminal around. It is equivalent to:
`Terminal<CrosstermBackend<Stdout>>`
We also added `ratatui::try_init()` and `try_restore()`, for situations
where you might want to handle initialization errors yourself instead
of letting the panic handler fire and cleanup. Simple Apps should
prefer the `init` and `restore` functions over these functions.
Corresponding functions to allow passing a `TerminalOptions` with
a `Viewport` (e.g. inline, fixed) are also available
(`init_with_options`,
and `try_init_with_options`).
The existing code to create a backend and terminal will remain and
is not deprecated by this approach. This just provides a simple one
line initialization using the common options.
---------
Co-authored-by: Orhun Parmaksız <orhunparmaksiz@gmail.com>
2024-08-22 12:16:35 +00:00
|
|
|
terminal.draw(|frame| self.draw(frame))?;
|
2024-08-06 08:10:58 +00:00
|
|
|
self.handle_events()?;
|
|
|
|
}
|
|
|
|
Ok(())
|
|
|
|
}
|
|
|
|
|
|
|
|
fn handle_events(&mut self) -> Result<()> {
|
|
|
|
if let Event::Key(key) = event::read()? {
|
feat(terminal): Add ratatui::init() and restore() methods (#1289)
These are simple opinionated methods for creating a terminal that is
useful to use in most apps. The new init method creates a crossterm
backend writing to stdout, enables raw mode, enters the alternate
screen, and sets a panic handler that restores the terminal on panic.
A minimal hello world now looks a bit like:
```rust
use ratatui::{
crossterm::event::{self, Event},
text::Text,
Frame,
};
fn main() {
let mut terminal = ratatui::init();
loop {
terminal
.draw(|frame: &mut Frame| frame.render_widget(Text::raw("Hello World!"), frame.area()))
.expect("Failed to draw");
if matches!(event::read().expect("failed to read event"), Event::Key(_)) {
break;
}
}
ratatui::restore();
}
```
A type alias `DefaultTerminal` is added to represent this terminal
type and to simplify any cases where applications need to pass this
terminal around. It is equivalent to:
`Terminal<CrosstermBackend<Stdout>>`
We also added `ratatui::try_init()` and `try_restore()`, for situations
where you might want to handle initialization errors yourself instead
of letting the panic handler fire and cleanup. Simple Apps should
prefer the `init` and `restore` functions over these functions.
Corresponding functions to allow passing a `TerminalOptions` with
a `Viewport` (e.g. inline, fixed) are also available
(`init_with_options`,
and `try_init_with_options`).
The existing code to create a backend and terminal will remain and
is not deprecated by this approach. This just provides a simple one
line initialization using the common options.
---------
Co-authored-by: Orhun Parmaksız <orhunparmaksiz@gmail.com>
2024-08-22 12:16:35 +00:00
|
|
|
if key.kind == KeyEventKind::Press && key.code == KeyCode::Char('q') {
|
2024-08-06 08:10:58 +00:00
|
|
|
self.should_exit = true;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
Ok(())
|
|
|
|
}
|
|
|
|
|
feat(terminal): Add ratatui::init() and restore() methods (#1289)
These are simple opinionated methods for creating a terminal that is
useful to use in most apps. The new init method creates a crossterm
backend writing to stdout, enables raw mode, enters the alternate
screen, and sets a panic handler that restores the terminal on panic.
A minimal hello world now looks a bit like:
```rust
use ratatui::{
crossterm::event::{self, Event},
text::Text,
Frame,
};
fn main() {
let mut terminal = ratatui::init();
loop {
terminal
.draw(|frame: &mut Frame| frame.render_widget(Text::raw("Hello World!"), frame.area()))
.expect("Failed to draw");
if matches!(event::read().expect("failed to read event"), Event::Key(_)) {
break;
}
}
ratatui::restore();
}
```
A type alias `DefaultTerminal` is added to represent this terminal
type and to simplify any cases where applications need to pass this
terminal around. It is equivalent to:
`Terminal<CrosstermBackend<Stdout>>`
We also added `ratatui::try_init()` and `try_restore()`, for situations
where you might want to handle initialization errors yourself instead
of letting the panic handler fire and cleanup. Simple Apps should
prefer the `init` and `restore` functions over these functions.
Corresponding functions to allow passing a `TerminalOptions` with
a `Viewport` (e.g. inline, fixed) are also available
(`init_with_options`,
and `try_init_with_options`).
The existing code to create a backend and terminal will remain and
is not deprecated by this approach. This just provides a simple one
line initialization using the common options.
---------
Co-authored-by: Orhun Parmaksız <orhunparmaksiz@gmail.com>
2024-08-22 12:16:35 +00:00
|
|
|
fn draw(&self, frame: &mut Frame) {
|
2024-08-06 08:10:58 +00:00
|
|
|
use Constraint::{Fill, Length, Min};
|
feat(terminal): Add ratatui::init() and restore() methods (#1289)
These are simple opinionated methods for creating a terminal that is
useful to use in most apps. The new init method creates a crossterm
backend writing to stdout, enables raw mode, enters the alternate
screen, and sets a panic handler that restores the terminal on panic.
A minimal hello world now looks a bit like:
```rust
use ratatui::{
crossterm::event::{self, Event},
text::Text,
Frame,
};
fn main() {
let mut terminal = ratatui::init();
loop {
terminal
.draw(|frame: &mut Frame| frame.render_widget(Text::raw("Hello World!"), frame.area()))
.expect("Failed to draw");
if matches!(event::read().expect("failed to read event"), Event::Key(_)) {
break;
}
}
ratatui::restore();
}
```
A type alias `DefaultTerminal` is added to represent this terminal
type and to simplify any cases where applications need to pass this
terminal around. It is equivalent to:
`Terminal<CrosstermBackend<Stdout>>`
We also added `ratatui::try_init()` and `try_restore()`, for situations
where you might want to handle initialization errors yourself instead
of letting the panic handler fire and cleanup. Simple Apps should
prefer the `init` and `restore` functions over these functions.
Corresponding functions to allow passing a `TerminalOptions` with
a `Viewport` (e.g. inline, fixed) are also available
(`init_with_options`,
and `try_init_with_options`).
The existing code to create a backend and terminal will remain and
is not deprecated by this approach. This just provides a simple one
line initialization using the common options.
---------
Co-authored-by: Orhun Parmaksız <orhunparmaksiz@gmail.com>
2024-08-22 12:16:35 +00:00
|
|
|
let vertical = Layout::vertical([Length(1), Fill(1), Min(20)]).spacing(1);
|
|
|
|
let [title, top, bottom] = vertical.areas(frame.area());
|
2024-08-06 08:10:58 +00:00
|
|
|
|
|
|
|
frame.render_widget("Grouped Barchart".bold().into_centered_line(), title);
|
|
|
|
frame.render_widget(self.vertical_revenue_barchart(), top);
|
|
|
|
frame.render_widget(self.horizontal_revenue_barchart(), bottom);
|
|
|
|
}
|
|
|
|
|
|
|
|
/// Create a vertical revenue bar chart with the data from the `revenues` field.
|
|
|
|
fn vertical_revenue_barchart(&self) -> BarChart<'_> {
|
|
|
|
let mut barchart = BarChart::default()
|
feat(terminal): Add ratatui::init() and restore() methods (#1289)
These are simple opinionated methods for creating a terminal that is
useful to use in most apps. The new init method creates a crossterm
backend writing to stdout, enables raw mode, enters the alternate
screen, and sets a panic handler that restores the terminal on panic.
A minimal hello world now looks a bit like:
```rust
use ratatui::{
crossterm::event::{self, Event},
text::Text,
Frame,
};
fn main() {
let mut terminal = ratatui::init();
loop {
terminal
.draw(|frame: &mut Frame| frame.render_widget(Text::raw("Hello World!"), frame.area()))
.expect("Failed to draw");
if matches!(event::read().expect("failed to read event"), Event::Key(_)) {
break;
}
}
ratatui::restore();
}
```
A type alias `DefaultTerminal` is added to represent this terminal
type and to simplify any cases where applications need to pass this
terminal around. It is equivalent to:
`Terminal<CrosstermBackend<Stdout>>`
We also added `ratatui::try_init()` and `try_restore()`, for situations
where you might want to handle initialization errors yourself instead
of letting the panic handler fire and cleanup. Simple Apps should
prefer the `init` and `restore` functions over these functions.
Corresponding functions to allow passing a `TerminalOptions` with
a `Viewport` (e.g. inline, fixed) are also available
(`init_with_options`,
and `try_init_with_options`).
The existing code to create a backend and terminal will remain and
is not deprecated by this approach. This just provides a simple one
line initialization using the common options.
---------
Co-authored-by: Orhun Parmaksız <orhunparmaksiz@gmail.com>
2024-08-22 12:16:35 +00:00
|
|
|
.block(Block::new().title(Line::from("Company revenues (Vertical)").centered()))
|
2024-08-06 08:10:58 +00:00
|
|
|
.bar_gap(0)
|
|
|
|
.bar_width(6)
|
|
|
|
.group_gap(2);
|
feat(terminal): Add ratatui::init() and restore() methods (#1289)
These are simple opinionated methods for creating a terminal that is
useful to use in most apps. The new init method creates a crossterm
backend writing to stdout, enables raw mode, enters the alternate
screen, and sets a panic handler that restores the terminal on panic.
A minimal hello world now looks a bit like:
```rust
use ratatui::{
crossterm::event::{self, Event},
text::Text,
Frame,
};
fn main() {
let mut terminal = ratatui::init();
loop {
terminal
.draw(|frame: &mut Frame| frame.render_widget(Text::raw("Hello World!"), frame.area()))
.expect("Failed to draw");
if matches!(event::read().expect("failed to read event"), Event::Key(_)) {
break;
}
}
ratatui::restore();
}
```
A type alias `DefaultTerminal` is added to represent this terminal
type and to simplify any cases where applications need to pass this
terminal around. It is equivalent to:
`Terminal<CrosstermBackend<Stdout>>`
We also added `ratatui::try_init()` and `try_restore()`, for situations
where you might want to handle initialization errors yourself instead
of letting the panic handler fire and cleanup. Simple Apps should
prefer the `init` and `restore` functions over these functions.
Corresponding functions to allow passing a `TerminalOptions` with
a `Viewport` (e.g. inline, fixed) are also available
(`init_with_options`,
and `try_init_with_options`).
The existing code to create a backend and terminal will remain and
is not deprecated by this approach. This just provides a simple one
line initialization using the common options.
---------
Co-authored-by: Orhun Parmaksız <orhunparmaksiz@gmail.com>
2024-08-22 12:16:35 +00:00
|
|
|
|
2024-08-06 08:10:58 +00:00
|
|
|
for group in self
|
|
|
|
.revenues
|
|
|
|
.iter()
|
|
|
|
.map(|revenue| revenue.to_vertical_bar_group(&self.companies))
|
|
|
|
{
|
|
|
|
barchart = barchart.data(group);
|
|
|
|
}
|
|
|
|
barchart
|
|
|
|
}
|
|
|
|
|
|
|
|
/// Create a horizontal revenue bar chart with the data from the `revenues` field.
|
|
|
|
fn horizontal_revenue_barchart(&self) -> BarChart<'_> {
|
|
|
|
let title = Line::from("Company Revenues (Horizontal)").centered();
|
|
|
|
let mut barchart = BarChart::default()
|
|
|
|
.block(Block::new().title(title))
|
|
|
|
.bar_width(1)
|
|
|
|
.group_gap(2)
|
|
|
|
.bar_gap(0)
|
|
|
|
.direction(Direction::Horizontal);
|
|
|
|
for group in self
|
|
|
|
.revenues
|
|
|
|
.iter()
|
|
|
|
.map(|revenue| revenue.to_horizontal_bar_group(&self.companies))
|
|
|
|
{
|
|
|
|
barchart = barchart.data(group);
|
|
|
|
}
|
|
|
|
barchart
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/// Generate fake company data
|
|
|
|
const fn fake_companies() -> [Company; COMPANY_COUNT] {
|
|
|
|
[
|
|
|
|
Company::new("BAKE", "Bake my day", Color::LightRed),
|
|
|
|
Company::new("BITE", "Bits and Bites", Color::Blue),
|
|
|
|
Company::new("TART", "Tart of the Table", Color::White),
|
|
|
|
]
|
|
|
|
}
|
|
|
|
|
|
|
|
/// Some fake revenue data
|
|
|
|
const fn fake_revenues() -> [Revenues; PERIOD_COUNT] {
|
|
|
|
[
|
|
|
|
Revenues::new("Jan", [8500, 6500, 7000]),
|
|
|
|
Revenues::new("Feb", [9000, 7500, 8500]),
|
|
|
|
Revenues::new("Mar", [9500, 4500, 8200]),
|
|
|
|
Revenues::new("Apr", [6300, 4000, 5000]),
|
|
|
|
]
|
|
|
|
}
|
|
|
|
|
|
|
|
impl Revenues {
|
|
|
|
/// Create a new instance of `Revenues`
|
|
|
|
const fn new(period: &'static str, revenues: [u32; COMPANY_COUNT]) -> Self {
|
|
|
|
Self { period, revenues }
|
|
|
|
}
|
|
|
|
|
|
|
|
/// Create a `BarGroup` with vertical bars for each company
|
|
|
|
fn to_vertical_bar_group<'a>(&self, companies: &'a [Company]) -> BarGroup<'a> {
|
|
|
|
let bars: Vec<Bar> = zip(companies, self.revenues)
|
|
|
|
.map(|(company, revenue)| company.vertical_revenue_bar(revenue))
|
|
|
|
.collect();
|
|
|
|
BarGroup::default()
|
|
|
|
.label(Line::from(self.period).centered())
|
|
|
|
.bars(&bars)
|
|
|
|
}
|
|
|
|
|
|
|
|
/// Create a `BarGroup` with horizontal bars for each company
|
|
|
|
fn to_horizontal_bar_group<'a>(&'a self, companies: &'a [Company]) -> BarGroup<'a> {
|
|
|
|
let bars: Vec<Bar> = zip(companies, self.revenues)
|
|
|
|
.map(|(company, revenue)| company.horizontal_revenue_bar(revenue))
|
|
|
|
.collect();
|
|
|
|
BarGroup::default()
|
|
|
|
.label(Line::from(self.period).centered())
|
|
|
|
.bars(&bars)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
impl Company {
|
|
|
|
/// Create a new instance of `Company`
|
|
|
|
const fn new(short_name: &'static str, name: &'static str, color: Color) -> Self {
|
|
|
|
Self {
|
|
|
|
short_name,
|
|
|
|
name,
|
|
|
|
color,
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/// Create a vertical revenue bar for the company
|
|
|
|
///
|
|
|
|
/// The label is the short name of the company, and will be displayed under the bar
|
|
|
|
fn vertical_revenue_bar(&self, revenue: u32) -> Bar {
|
|
|
|
let text_value = format!("{:.1}M", f64::from(revenue) / 1000.);
|
|
|
|
Bar::default()
|
|
|
|
.label(self.short_name.into())
|
|
|
|
.value(u64::from(revenue))
|
|
|
|
.text_value(text_value)
|
|
|
|
.style(self.color)
|
|
|
|
.value_style(Style::new().fg(Color::Black).bg(self.color))
|
|
|
|
}
|
|
|
|
|
|
|
|
/// Create a horizontal revenue bar for the company
|
|
|
|
///
|
|
|
|
/// The label is the long name of the company combined with the revenue and will be displayed
|
|
|
|
/// on the bar
|
|
|
|
fn horizontal_revenue_bar(&self, revenue: u32) -> Bar {
|
|
|
|
let text_value = format!("{} ({:.1} M)", self.name, f64::from(revenue) / 1000.);
|
|
|
|
Bar::default()
|
|
|
|
.value(u64::from(revenue))
|
|
|
|
.text_value(text_value)
|
|
|
|
.style(self.color)
|
|
|
|
.value_style(Style::new().fg(Color::Black).bg(self.color))
|
|
|
|
}
|
|
|
|
}
|