First Pass GUI Design (first time contributer)
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 2.1k
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 31
Description
Hello,
I am new to beets and the open source community and was looking to get involved as part of a software engineering course. A few of my group members have posted on the issue tracker with bug issues, but I thought I would go in a different direction. I saw that in the Hacking portion of the wiki you had mentioned interest in a GUI design since beets is currently command line only. I have worked a little bit with GUI at my internship and thought it would be something fun and different to get involved in the design process.
My idea with the GUI implementation is that it would help attract users who might otherwise be put off by the command line aspect. I saw it working with the option to be used as an "introductory" tool, where the various GUI elements would essentially build a typical beets command behind the scenes and execute it. When the user steps through the GUI, there could be an option to display the beets command that they have generated based off their GUI choices in the hopes that, in the future, they can forego the GUI and work exclusively in command line.
As for the actual design, this is a complete shot in the dark, using free (for personal and commercial use) mobile GUI assets that I found online. I figured the best way to get feedback would be to have an example from which changes, approvals and disapproval could be made. Since I am still new to beets and have not had a whole lot of experience, the various views may or may not make sense for the commands they're trying to build. I look forward to receiving your feedback (even if you hate it =P)!
I thought this sort of feature may also make it easier to have different "users", with their own libraries and configurations. Such a thing may already exist, I have not encountered it myself though.






Contributor guide
Assessment
This issue has not been assessed yet.