3 ms·
This is very cool, thanks for resubmitting it, I actually checked out the source code this time, as opposed to last time only reading the readme. Having learne
by sephoric 8y ago
This is very cool, thanks for resubmitting it, I actually checked out the source code this time, as opposed to last time only reading the readme.
Having learned all that you needed to in order to write (and rewrite) this, do you have any similar future projects in the works?
- 2211 8y agoI'm working on a guide that will cover the entire process of creating a terminal user interface in bash. I want to create a central location for the information I've gathered so it may be of benefit to others. I also hope that people will contribute their own snippets, methods and ideas. It'd be great to find out if there are better ways of implementing the code. The guide is on GitHub [0] and is a heavy work in progress. Its currently structured in a way I'm not too happy with. I want to change it to a series of 'How to implement x' instead of an ever growing implementation. Other than the TUI guide I have 4 other major projects which I am working on (neofetch, pywal, fff and the Pure Bash Bible). [0] https://github.com/dylanaraps/writing-a-tui-in-bash https://github.com/dylanaraps/writing-a-tui-in-bash
- sephoric 8y agoAlong those lines, I think a heavily commented version of fff would be a great learning tool. The concepts of fff are simple enough that anyone could follow along easily without really having to learn fff first. This idea came partly from the fact that when I tried reading fff's new source code yesterday, while knowing exactly what fff does and understanding the comments completely, I was still pretty lost as to what it was doing and how it worked.