Which GUI to use for the proof-of-concept prototype?

ArkThis / AHAlodeck

The place to be for discussing future any-data layouts.

GNU General Public License v3.0

0 stars 0 forks source link

Which GUI to use for the proof-of-concept prototype? #1

Open pjotrek-b opened 1 week ago

pjotrek-b commented 1 week ago

I'm voting for Python as language for several reasons.

I've quite recently taken the time to finally get to know Jupyter. Lab as I figured it's Notebooks successor - and I find it mindblowingly powerful and useful.

Paul suggested to use Flask in Docker. I trust Paul on that, and would suggest to go that way.

ross-spencer commented 5 days ago

+1 Python for its adoption in the archiving community.

Flask is nice but it will be interesting to evaluate the abstraction to understand if it will be easy to swap in and out in future. For APIs I have been using FastAPI a lot, and HTMX is a really nice lightweight way of engaging with APIs through HTML.

pjotrek-b commented 3 days ago

Horray! I've added "save" and "reload" functionality to my super-hacky proof-of-concept Python Qt GUI: https://github.com/pjotrek-b/mercs/

It's called "MERCS" for "Metadata Edit? Right Click: Save."

The code is super-ugly, but it works :grin:

I'll now move something like that basic functionality of MERCS over to Flask.

ross-spencer commented 3 days ago

Might be a shortcut for you getting the project into good shape, but I have a template repo I have been working on with different tooling to make it easier to collab with folk.

https://github.com/ffdev-info/template.py