Should I Add a GUI to My Wine Management App?

I think more code could lead to more trust issues or time spent on validation. It can complicate things for users who want to understand, automate, or write instructions for installation. From a free and open-source software perspective, it might make your code less easily integrated into other projects due to added dependencies. Have you thought about what other features you could build if you decide not to add a GUI? A common middle ground I’ve seen is using YAD (Yet Another Dialog); just bear in mind that it usually necessitates a GUI. You might want to ask yourself if you really want a GUI or just want a chance to enhance your skills—maybe maintain the shell project while creating a separate repository for a GUI that runs the scripts?

I had a look at your project! I’d love to contribute some code. You could implement auto-detection for different distributions instead of relying on a flag. Also, as a tip, try to use shorter flags like -abcde or longer ones like --flagA, --flagB, etc. By the way, how does this project differ from using apt in Debian?

I’m excited to check out your project since I often work with Wine and have faced some challenges. Instead of expanding your current app to include a GUI, why not create a simple wrapper around it? I do that with a lot of my projects using Python and Tkinter. At least this way, the wrapper can be an optional feature without overcomplicating the main project.