Components Wishlist (from Bubbles)

[leostera]

Having a nice little library of components to reuse would be amazing, and Bubbles has a nice list that we can just port over:

• cursor
• spinner
• text input
• text area
• table (even virtualized!)
• progress bar: we have something here, not amazing yet but its a good start
• paginator
• list with filtering
• a toggleable help bar
• key bindings component to help declaratively map keys to actions
• checkbox – just a tiny little checkbox :)

[sabine]

Spinner added in #13. 🔥

[lessp]

I began looking at what would be required for text input.

textinput in bubbles makes use of bubbletea itself. This makes one able to simply forward the events to the textinput component. What are your thoughts on doing the same? The alternative would be to simply expose commands from the textinput and map the events yourself. This however, feels like it could become quite cumbersome.

E.g. bubbles does this:

match event with 
| e -> 
  (* do other stuff *)
  let new_text_input = Text_input.update e in
  { model with text_input = new_text_input }

The alternative, if you want leaves to be stand-alone (unless we separate the events), one would have to do this:

match event with 
| KeyDown Left ->
  let new_text_input = Text_input.character_backward model.text_input in
  { model with text_input = new_text_input }
| ...

[leostera]

I think you made the right call with taking the Event.t and making Leaves depend on MintTea 🙏🏼

[metame]

I'm starting on a paginator component :)

[metame]

Forgot to mention this issue in my PR, but Paginator is done for anyone looking at this list.

[davesnx]

I would love to have a "Menu" https://github.com/p-gen/smenu