You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way to be able to get to the bubbletea/charmbracelet/charming code, and see how you built and used it, without having to download Helm? So that we can get a better idea on how to use the code for the terminal user interface, and perhaps, learn from it?
It would save programmers like me so much time for many reasons. You already know that many Golang code projects do not work. Either because of cyclic errors, or incompetence.
Also, downloading such a large program, when one does not need to use Helm or any other dependency, especially when one does not even know if the program works! This too would save alot of time.
The text was updated successfully, but these errors were encountered:
? i'm not sure I understand. This project doesn't use Helm. There are plenty of example docs in the charmbracelet repos if you need simple starter code.
No. I want to see the Bubbletea app as a shell without any need to download any other dependencies. I am sure someone must have determined what the interface would look like before being populated.
Is it possible for us to have access to the shell code, so that we can see how certain aspects of BubbleTea are implemented?
Is there a way to be able to get to the bubbletea/charmbracelet/charming code, and see how you built and used it, without having to download Helm? So that we can get a better idea on how to use the code for the terminal user interface, and perhaps, learn from it?
It would save programmers like me so much time for many reasons. You already know that many Golang code projects do not work. Either because of cyclic errors, or incompetence.
Also, downloading such a large program, when one does not need to use Helm or any other dependency, especially when one does not even know if the program works! This too would save alot of time.
The text was updated successfully, but these errors were encountered: