3 ms·
> Turn almost any Python command line program into a GUI application Why would anybody need this? Xterm is already a GUI application and you can run the origi
by enriquto 5y ago
> Turn almost any Python command line program into a GUI application
Why would anybody need this? Xterm is already a GUI application and you can run the original program inside it. What benefit is there?
What I'd like is the inverse operation: turn an arbitrary GUI application into a command line program. Now, that would be really useful! That would allow a lot of automation that is difficult with GUI stuff. It seems a really, really hard problem though.
- tsegers 5y ago> Why would anybody need this? Because they have no experience using a terminal, entering commands and finding documentation
- huskyr 5y agoBecause 99% of the world's population doesn't know how to operate a terminal?
- mritchie712 5y agoThere are whole sections of the README directly answering your question (e.g. who is this for)
- enriquto 5y agoYes, I read this, and it is essentially an aesthetic, UX issue. But it does not allow you to do things any easier in practice (at least if you are used to the command line). I was just asking it semi-rhetorically to introduce my question about the inverse transformation. A command-line interface to clicking buttons on a headless GUI, by naming their labels, would be an extremely useful tool. Even if only worked for applications written with the major toolkits gtk, qt, electron etc. EDIT: imagine that you could do this: ungooey gimp --menu file:open:lena.png --click eraser --drag "10,10-100,200" --menu file:saveas:lena2.png and it created an image with a white diagonal band erased in white.
- dolmen 5y agoIt looks like you want a CLI-ified AppleScript. https://en.wikipedia.org/wiki/AppleScript https://en.wikipedia.org/wiki/AppleScript
- jcelerier 5y agoYou can do that semi-easily on most linux apps using GTK, Qt with AT-SPI: https://delysid.org/gspi.html https://delysid.org/gspi.html most likely both Windows and macOS would have similar mechanisms for accessing their respective accessibility api
- fsloth 5y ago"Why would anybody need this?" For example to provide quick tools for non-professional users. Single button automation for scripts that need to be run intermittently and are poor candidates for timed execution. I am quite proficient at command line, but still prefer a single button that "does that one thing I need".
- magicalhippo 5y agoAs you can see, it makes the program self-discoverable. Instead of having to go back and forth between the --help output or a man page and the command you're typing, you can just read as you go. This is great for non-trivial tools used occasionally by people who don't live in the terminal (aka most users).