Inquirer library based on Textual #6178
Replies: 3 comments 1 reply
-
|
Looks great! Would you mind sharing this on the Discord channel show-and-tell? I'm sure it would get a lot of feedback. |
Beta Was this translation helpful? Give feedback.
-
|
oooooh, I've been waiting for this for so long!!!! +1 on what will said about joining discord |
Beta Was this translation helpful? Give feedback.
-
|
In case anyone is interested, I've made some progress on the synchronous high-level API for programs that need a simple TUI with inquiry widgets i.s.o. only inquiry prompts. Example app is here: https://github.com/robvanderleek/inquirer-textual/blob/issue-14-Support_full-screen_app_next_to_prompts/examples/app.py In a nutshell, the synchronous API code runs in a separate thread and communicates with the Textual event loop thread via shared variables/Events. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Similar to Inquirer.js, and existing Inquirer Python ports (such as InquirerPy), I've started work on Inquirer Textual:
Nothing big yet, current status: https://robvanderleek.github.io/inquirer-textual/
Development for the inline widgets so far is nice, I really enjoy the ability to unit-test widgets.
I'm a bit stuck now on the way the library should support users to migrate from inline prompts to a slightly more advanced full-screen TUI. Preferably, I want to keep the API high-level and synchronous (the Textual paradigm is great for larger TUI applications, but a bit daunting for smaller programs IMO.)
Feedback appreciated! 🙂
Beta Was this translation helpful? Give feedback.
All reactions