Skip to content

feat: ✨ add minimal tui for metadata exploration#331

Open
joelostblom wants to merge 4 commits into
mainfrom
term-multi-page-tui-minimal
Open

feat: ✨ add minimal tui for metadata exploration#331
joelostblom wants to merge 4 commits into
mainfrom
term-multi-page-tui-minimal

Conversation

@joelostblom

@joelostblom joelostblom commented May 6, 2026

Copy link
Copy Markdown
Contributor

Description

See motivation in #330. There is also a more fully fledged demo there. Here is a screenshot of what the basic implementation in this PR would look like

image

Close #330, close #327, maybe also close #259?

Needs a thorough review.

Checklist

  • Ran just run-all

@lwjohnst86 lwjohnst86 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Neat idea, but this PR is way too big and the code doesn't match our style at all. Did you use AI for this? 🤔

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This code reminds me of AI generated code... is it? If it isn't, this needs to be heavily refactored to follow our style and clean it up. E.g. there are several nested for loops, a lot of conditionals, a lot of use of list comprehensions, capitalisations when we only use capitalisations for constants, and too deeply nested code.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, this is codex via opencode, same as I mentioned I've been using as a coding assistant for some time. Just to be clear, it's not a one pass "do this and done", there is a lot of iteration but I'll admit that I got a bit too excited about having a prototype up and working that I forgot to adjust the coding style to be functional etc =p That's my bad and I will address that here after we finish the brainstorming about the design in #330 so that I know if we keep --mode approach here or go for a separate subcommand (and potentially other design decisions).

But aside from coding style, does the Textual approach with components, CSS, etc make sense and is that a dependency you can see us take on in flower? I don't have experience with it from previously so I don't know of any gotchas, just that it's built by the same people that made rich and generally popular for making TUIs (in python in particular, I could not find anything else of similar capacity).

I also thought it would be helpful to have this up so that anyone in the team can take it for a spin while we do the brainstorming to experience how things work and not just watch the video I posted.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lwjohnst86 Just a ping in case this comment got lost, no rush though.

@lwjohnst86 lwjohnst86 May 28, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we decide based on the discussion in #330 and maybe make a decision post about which tool to use for TUIs in Python? Unless we refactor this to Rust, which means we'd need to go with a different tooling.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I'll leave this until we arrive at something in #330 and maybe also take a decision on whether we want to use Rust here or not (maybe after we learn more about it for propagate).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Todo

2 participants