Eel VS Gooey

I gave up a long time ago attempting to write GUIs in pure python. I've come back to them periodically to see if the landscape has changed, but I'm always disappointed.

My current go-to python GUI solution is to use the Eel library. It renders GUIs in a web-browser like window with HTMl/CSS/JS.It lets you expose your python functions to JavaScript, so data can be easily transferred back and forth between the python and the JavaScript. And since it's just web-dev, it's pretty easy to make things look and feel good enough. Any other web-dev libraries like bootstrap and jquery can be used. It works pretty well for writing GUIs that put data analysis tools in front of my colleagues.

https://github.com/python-eel/Eel

Eel was used to implement the app and communication with the web interface.

I am calling a function from Python using eel and taking the return value. Python functions are asynchronous with JavaScript by nature. This code is combined with other variables to determine if the form can continue. allFilled() is called everytime the form field changes.

In the past, I've used QT4 and QT Designer. It was okay. It was a small mountain to climb for myself then - but certainly doable. However, there was a lot of generated code that wasn't the most concise thing. Today, I discovered Eel. Since I used QT4 in the past, I've done some web dev. Certainly, not proficient there. But Eel wasn't as big of a hurdle. In fact, it took me a fraction of the time because it is much like creating a basic website. Where there's an abundance of tutorials and tips out there for everything imaginable. Instead of downloading and adding a font, clicking through a bunch of dialogs. I just linked a Google font and updated the CSS. Stuff like that.

If you don't want a web-app, you can still use JS for GUI, using something like python-eel https://github.com/python-eel/Eel

The name conflicts with a similar python module that allows one to turn any Python console program into a GUI with one line.

https://github.com/chriskiehl/Gooey

Hey! Cool project! I have a question: why do you dump out sys.argv to a local file in the CWD? [0] tmp.txt is hardly a unique name… or am I missing something and this never triggers?

[0] https://github.com/chriskiehl/Gooey/blob/be4b11b8f27f500e732...

This might be of interest to you:

> Gooey - Turn (almost) any Python 3 Console Program into a GUI application with one line

https://github.com/chriskiehl/Gooey

I love gooey: https://github.com/chriskiehl/Gooey

It allows me to quickly slap a GUI on an existing script that accepts command-line-arguments. In the end, I get the best of both world: Discoverability from the GUI, automation through the script, and automatic feature parity between the two.

Downside: Control over the GUI layout is basic, and only "standard" GUI features work, but I never felt limited when using it.

similar for local/individual usage:

https://github.com/chriskiehl/Gooey - take a python-CLI, make a TK-windows

and then probably even simple dashboarding like streamlit.

Like Gooey?

As for how I'd handle it, I would probably combine both into one command-line program, with all filepaths using pathlib and letting argparse handle the options. That way you could optionally generate a GUI with gooey with little extra effort, although this would also add a dependency.