camply VS Gooey

Adding Textual support to camply [1] was apparently very easy. I didn't to the implementation; I just contribute to the project sometimes: https://juftin.com/camply/command_line_usage/#tui

[1] https://juftin.com/camply/

I've got an open-source project called camply. Here's the spiel:

I've built a free command line tool that helps with this - it's called camply: https://juftin.com/camply.

Here's a personal page built with Jekyll: https://juftin.com. And here's a Sphinx Page: https://juftin.com/camply. Both are actually hosted on GitHub pages for free.

I used this one once, but it only does campsite availability.

I came across a reddit post about a really neat tool somebody created to find openings at campgrounds on the recreation.gov website (after cancellations) and get notified immediately. This does not secure you the reservation, but instead uses the website's (public) API to link you to the booking page, from which you then select those dates that somebody else cancelled. It looks like this.

If you have a working understanding of how to run the below command and then your command line proficiency is likely enough to work with camply and you can feel free to start a discussion on GitHub to ask questions: https://github.com/juftin/camply/discussions

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.