Some other simplications

[joshka]

• [ ] Status bar basically has an if statement that does something different for each mode that it's presented in, but the shared common functionality isn't enough to make it worth doing that way. Instead just handle that in the specific widget E.g. take code that is kinda like:

  impl Widget for A { fn render(...) { StatusBar.mode(A).render(...) }
  impl Widget for B { fn render(...) { StatusBar.mode(B).render(...) }
  impl Widget for StatusBar {
  fn render(...) {
  match mode {
    A => render_A_status_bar(),
    B => render_B_status_bar(),
  }
  }
  }

  and simplify it

  impl Widget for A { fn render(...) { render_A_status_bar() }
  impl Widget for B { fn render(...) { render_B_status_bar() }

• [x] Help widget render method has a long iterator chain which calls get command a bunch of times. The command list is constant data. Write it as an constant array and then map that instead of the repeated code.

• [x] consider just having an Event::Crossterm(CrosstermEvent) variant instead of mapping each variant to Event variants.

[joshka]

Help widget render method has a long iterator chain which calls get command a bunch of times. The command list is constant data. Write it as an constant array and then map that instead of the repeated code.

27

[joshka]

consider just having an Event::Crossterm(CrosstermEvent) variant instead of mapping each variant to Event variants.

28