tui-rs/src/widgets/barchart.rs

211 lines
6.2 KiB
Rust
Raw Normal View History

use crate::{
buffer::Buffer,
layout::Rect,
style::Style,
symbols,
widgets::{Block, Widget},
};
2017-10-30 21:28:18 +00:00
use std::cmp::{max, min};
2016-10-22 10:51:41 +00:00
use unicode_width::UnicodeWidthStr;
2016-11-04 18:27:19 +00:00
/// Display multiple bars in a single widgets
///
/// # Examples
///
/// ```
/// # use tui::widgets::{Block, Borders, BarChart};
2016-11-06 20:41:32 +00:00
/// # use tui::style::{Style, Color, Modifier};
2016-11-04 18:27:19 +00:00
/// BarChart::default()
/// .block(Block::default().title("BarChart").borders(Borders::ALL))
2016-11-04 18:27:19 +00:00
/// .bar_width(3)
/// .bar_gap(1)
2016-11-06 20:41:32 +00:00
/// .style(Style::default().fg(Color::Yellow).bg(Color::Red))
/// .value_style(Style::default().fg(Color::Red).modifier(Modifier::BOLD))
2016-11-06 20:41:32 +00:00
/// .label_style(Style::default().fg(Color::White))
2016-11-04 18:27:19 +00:00
/// .data(&[("B0", 0), ("B1", 2), ("B2", 4), ("B3", 3)])
/// .max(4);
/// ```
#[derive(Debug, Clone)]
2016-10-22 10:51:41 +00:00
pub struct BarChart<'a> {
2016-11-04 18:27:19 +00:00
/// Block to wrap the widget in
2016-10-22 10:51:41 +00:00
block: Option<Block<'a>>,
2016-11-04 18:27:19 +00:00
/// The width of each bar
2016-10-22 10:51:41 +00:00
bar_width: u16,
2016-11-04 18:27:19 +00:00
/// The gap between each bar
2016-10-22 10:51:41 +00:00
bar_gap: u16,
/// Set of symbols used to display the data
bar_set: symbols::bar::Set,
2016-11-06 17:49:57 +00:00
/// Style of the values printed at the bottom of each bar
value_style: Style,
/// Style of the labels printed under each bar
label_style: Style,
/// Style for the widget
style: Style,
2016-11-04 18:27:19 +00:00
/// Slice of (label, value) pair to plot on the chart
2016-10-22 10:51:41 +00:00
data: &'a [(&'a str, u64)],
2016-11-04 18:27:19 +00:00
/// Value necessary for a bar to reach the maximum height (if no value is specified,
/// the maximum value in the data is taken as reference)
max: Option<u64>,
/// Values to display on the bar (computed when the data is passed to the widget)
2016-10-22 10:51:41 +00:00
values: Vec<String>,
}
impl<'a> Default for BarChart<'a> {
fn default() -> BarChart<'a> {
BarChart {
block: None,
max: None,
data: &[],
values: Vec::new(),
2016-10-22 10:51:41 +00:00
bar_width: 1,
bar_gap: 1,
bar_set: symbols::bar::NINE_LEVELS,
2016-11-06 17:49:57 +00:00
value_style: Default::default(),
label_style: Default::default(),
style: Default::default(),
2016-10-22 10:51:41 +00:00
}
}
}
impl<'a> BarChart<'a> {
pub fn data(mut self, data: &'a [(&'a str, u64)]) -> BarChart<'a> {
2016-10-22 10:51:41 +00:00
self.data = data;
self.values = Vec::with_capacity(self.data.len());
2016-10-22 17:24:35 +00:00
for &(_, v) in self.data {
2016-10-22 10:51:41 +00:00
self.values.push(format!("{}", v));
}
self
}
pub fn block(mut self, block: Block<'a>) -> BarChart<'a> {
2016-10-22 10:51:41 +00:00
self.block = Some(block);
self
}
pub fn max(mut self, max: u64) -> BarChart<'a> {
2016-10-22 10:51:41 +00:00
self.max = Some(max);
self
}
pub fn bar_width(mut self, width: u16) -> BarChart<'a> {
2016-10-22 10:51:41 +00:00
self.bar_width = width;
self
}
pub fn bar_gap(mut self, gap: u16) -> BarChart<'a> {
2016-10-22 10:51:41 +00:00
self.bar_gap = gap;
self
}
pub fn bar_set(mut self, bar_set: symbols::bar::Set) -> BarChart<'a> {
self.bar_set = bar_set;
self
}
pub fn value_style(mut self, style: Style) -> BarChart<'a> {
2016-11-06 17:49:57 +00:00
self.value_style = style;
2016-10-22 10:51:41 +00:00
self
}
pub fn label_style(mut self, style: Style) -> BarChart<'a> {
2016-11-06 17:49:57 +00:00
self.label_style = style;
2016-10-22 10:51:41 +00:00
self
}
pub fn style(mut self, style: Style) -> BarChart<'a> {
2016-11-06 17:49:57 +00:00
self.style = style;
self
}
2016-10-22 10:51:41 +00:00
}
impl<'a> Widget for BarChart<'a> {
feat: add stateful widgets Most widgets can be drawn directly based on the input parameters. However, some features may require some kind of associated state to be implemented. For example, the `List` widget can highlight the item currently selected. This can be translated in an offset, which is the number of elements to skip in order to have the selected item within the viewport currently allocated to this widget. The widget can therefore only provide the following behavior: whenever the selected item is out of the viewport scroll to a predefined position (make the selected item the last viewable item or the one in the middle). Nonetheless, if the widget has access to the last computed offset then it can implement a natural scrolling experience where the last offset is reused until the selected item is out of the viewport. To allow such behavior within the widgets, this commit introduces the following changes: - Add a `StatefulWidget` trait with an associated `State` type. Widgets that can take advantage of having a "memory" between two draw calls needs to implement this trait. - Add a `render_stateful_widget` method on `Frame` where the associated state is given as a parameter. The chosen approach is thus to let the developers manage their widgets' states themselves as they are already responsible for the lifecycle of the wigets (given that the crate exposes an immediate mode api). The following changes were also introduced: - `Widget::render` has been deleted. Developers should use `Frame::render_widget` instead. - `Widget::background` has been deleted. Developers should use `Buffer::set_background` instead. - `SelectableList` has been deleted. Developers can directly use `List` where `SelectableList` features have been back-ported.
2019-12-15 20:38:18 +00:00
fn render(mut self, area: Rect, buf: &mut Buffer) {
let chart_area = match self.block {
Some(ref mut b) => {
feat: add stateful widgets Most widgets can be drawn directly based on the input parameters. However, some features may require some kind of associated state to be implemented. For example, the `List` widget can highlight the item currently selected. This can be translated in an offset, which is the number of elements to skip in order to have the selected item within the viewport currently allocated to this widget. The widget can therefore only provide the following behavior: whenever the selected item is out of the viewport scroll to a predefined position (make the selected item the last viewable item or the one in the middle). Nonetheless, if the widget has access to the last computed offset then it can implement a natural scrolling experience where the last offset is reused until the selected item is out of the viewport. To allow such behavior within the widgets, this commit introduces the following changes: - Add a `StatefulWidget` trait with an associated `State` type. Widgets that can take advantage of having a "memory" between two draw calls needs to implement this trait. - Add a `render_stateful_widget` method on `Frame` where the associated state is given as a parameter. The chosen approach is thus to let the developers manage their widgets' states themselves as they are already responsible for the lifecycle of the wigets (given that the crate exposes an immediate mode api). The following changes were also introduced: - `Widget::render` has been deleted. Developers should use `Frame::render_widget` instead. - `Widget::background` has been deleted. Developers should use `Buffer::set_background` instead. - `SelectableList` has been deleted. Developers can directly use `List` where `SelectableList` features have been back-ported.
2019-12-15 20:38:18 +00:00
b.render(area, buf);
b.inner(area)
}
2018-08-12 22:27:56 +00:00
None => area,
2016-10-22 10:51:41 +00:00
};
2016-10-31 17:04:10 +00:00
if chart_area.height < 2 {
return;
2016-10-22 10:51:41 +00:00
}
feat: add stateful widgets Most widgets can be drawn directly based on the input parameters. However, some features may require some kind of associated state to be implemented. For example, the `List` widget can highlight the item currently selected. This can be translated in an offset, which is the number of elements to skip in order to have the selected item within the viewport currently allocated to this widget. The widget can therefore only provide the following behavior: whenever the selected item is out of the viewport scroll to a predefined position (make the selected item the last viewable item or the one in the middle). Nonetheless, if the widget has access to the last computed offset then it can implement a natural scrolling experience where the last offset is reused until the selected item is out of the viewport. To allow such behavior within the widgets, this commit introduces the following changes: - Add a `StatefulWidget` trait with an associated `State` type. Widgets that can take advantage of having a "memory" between two draw calls needs to implement this trait. - Add a `render_stateful_widget` method on `Frame` where the associated state is given as a parameter. The chosen approach is thus to let the developers manage their widgets' states themselves as they are already responsible for the lifecycle of the wigets (given that the crate exposes an immediate mode api). The following changes were also introduced: - `Widget::render` has been deleted. Developers should use `Frame::render_widget` instead. - `Widget::background` has been deleted. Developers should use `Buffer::set_background` instead. - `SelectableList` has been deleted. Developers can directly use `List` where `SelectableList` features have been back-ported.
2019-12-15 20:38:18 +00:00
buf.set_background(chart_area, self.style.bg);
let max = self
.max
2017-10-30 21:28:18 +00:00
.unwrap_or_else(|| self.data.iter().fold(0, |acc, &(_, v)| max(v, acc)));
2017-09-11 05:58:37 +00:00
let max_index = min(
(chart_area.width / (self.bar_width + self.bar_gap)) as usize,
self.data.len(),
);
let mut data = self
.data
2016-10-22 10:51:41 +00:00
.iter()
.take(max_index)
2019-06-16 20:21:55 +00:00
.map(|&(l, v)| {
(
l,
v * u64::from(chart_area.height) * 8 / std::cmp::max(max, 1),
)
})
2016-10-22 10:51:41 +00:00
.collect::<Vec<(&str, u64)>>();
for j in (0..chart_area.height - 1).rev() {
for (i, d) in data.iter_mut().enumerate() {
let symbol = match d.1 {
0 => self.bar_set.empty,
1 => self.bar_set.one_eighth,
2 => self.bar_set.one_quarter,
3 => self.bar_set.three_eighths,
4 => self.bar_set.half,
5 => self.bar_set.five_eighths,
6 => self.bar_set.three_quarters,
7 => self.bar_set.seven_eighths,
_ => self.bar_set.full,
2016-10-22 10:51:41 +00:00
};
for x in 0..self.bar_width {
2017-09-11 05:58:37 +00:00
buf.get_mut(
chart_area.left() + i as u16 * (self.bar_width + self.bar_gap) + x,
chart_area.top() + j,
)
.set_symbol(symbol)
2018-09-23 19:00:36 +00:00
.set_style(self.style);
2016-10-22 10:51:41 +00:00
}
if d.1 > 8 {
d.1 -= 8;
} else {
d.1 = 0;
}
}
}
for (i, &(label, value)) in self.data.iter().take(max_index).enumerate() {
if value != 0 {
let value_label = &self.values[i];
let width = value_label.width() as u16;
if width < self.bar_width {
2017-09-11 05:58:37 +00:00
buf.set_string(
chart_area.left()
+ i as u16 * (self.bar_width + self.bar_gap)
2017-10-30 21:28:18 +00:00
+ (self.bar_width - width) / 2,
2017-09-11 05:58:37 +00:00
chart_area.bottom() - 2,
value_label,
self.value_style,
2017-09-11 05:58:37 +00:00
);
2016-10-22 10:51:41 +00:00
}
}
2017-09-11 05:58:37 +00:00
buf.set_stringn(
chart_area.left() + i as u16 * (self.bar_width + self.bar_gap),
chart_area.bottom() - 1,
label,
self.bar_width as usize,
self.label_style,
2017-09-11 05:58:37 +00:00
);
2016-10-22 10:51:41 +00:00
}
}
}