Can’t even view the app information in the app store as it’s “not available in your region”. Perhaps the website could be clear about what regions it is available in?
I've been using a "command palette" in the same app since the mid 90s, on lots of different operating systems, and I've never really found that it's a lazy way to make commands available. Mostly what I want to use is available from a menu, and/or available from keyboard bindings, but if I wish I can also pull up the command palette and run the command directly -- sometimes that's handy if I personally know what the command is called but I can't remember which menu it might be in, or what the key binding is.
Of course, it's not called a "command palette"; normally Emacs calls it `execute-extended-command`, and more commonly people will refer to it as the minibuffer.
But that's just me doing the angry-old-man-yells-about-ancient-useful-UI thing. ;-)
I get that this can be annoying (as someone who maintains code written using Textual, I very much get it), but while we're still 0.x we are making the most of being able to steer in slightly different directions if a more beneficial approach becomes obvious in some area.
We also try really hard to highlight breaking changes when a new release is made.
And, of course, if anything particular is tricky to work around or get working again anyone is welcome to seek some help in GitHub issues, discussions or even on Discord if that's your thing.
It supports normal Markdown links right now. As an Obsidian user I have been thinking wikilinks would be nice to add too. No firm plans but something I’d like to add.
I did add some vim-friendly bindings for switching the navigation panes on the left, but thinking about it not for the main viewer. Feels like an oversight now, good call. I’ll add that to the todo list.
Are you, perhaps, conflating Britain and the United Kingdom of Great Britain and Northern Ireland? There’s a potential upcoming referendum about the latter, not the former.
We are having fun, for sure. And I suspect we’re making coding for the terminal just a wee bit more accessible for some. With Python and Textual folk can spin up a good looking app pretty quickly (see our tutorial).
Perhaps it’ll lead one or two more people down the path to eventually learning ncurses (or S-Lang, which I tended to use back in the day).
This sort of thing is on the development roadmap. Also, some people have been building their own version of this with Textual already. Few days ago someone was showing off a Textual app they’d built that would play video - using the kitty protocol IIRC.
Aye, that’ll be it then. The docs went live towards the end of October, with the release of 0.2.0 (which was a huge change over 0.1, adding the whole CSS approach). If you do decide to dip back by for a look you should hopefully find the documentation covers a lot now, with a really rich tutorial. Still plenty to add of course, it’s a work in progress, but I think we’re doing good for docs now.
How long ago did you check the documentation? As of October this year the first full set of docs were published, with more to come: https://textual.textualize.io/
Yes, when a Textual app is running it takes over the terminal. But Textual is built on Rich, which doesn't. So you could use Rich to handle your batch display and Textual for when you want things that go fullscreen.