Open maaslalani opened 2 years ago
I'd love to pick this up and contribute!
How should I move forward?
Hey @KaviiSuri, awesome that you want to contribute. I think to implement this we'll need some sort of Navigation
bubble as mentioned. This should mean that the top level navigation can contain different Screen
s (maybe we can improve this name) and a way to switch between them through their configured keybindings.
I think a lot of the inspiration will come from this video of making nested models (https://www.youtube.com/watch?v=uJ2egAkSkjg) and making a way to stream line this code and make concepts that most people would understand so that it is easier to build multi-view applications.
If you want to give it a go please feel free to! Let me know if you have any further questions or want to ask about clarification about introducing concepts.
Hi, Thanks for the video! I'll go through it and get back with any questions I have! (I'm kinda new to bubbles so I might have a lot of them!)
@maaslalani I've added a draft PR, wanted to get your inputs on how to move forward.
Bubbles should probably help users build multi-view applications such as
glow
, etc... more easily. We can likely do this by implementing routing and navigation through a Bubble similar to how we help define keybindings withkey.Binding
.I'm roughly imagining something like this:
I'd imagine we can also then implement many helper methods and handle updating nested models for most use cases. I think this will make multi-view Bubble Tea applications much easier to implement if we can simply define several
tea.Model
and definekey.Binding
s to switch between them and handle all routing and updates for the users building the apps. This could also allow us to buildStack
based navigation, etc...