Slumber a TUI HTTP Client
41–50 of 73 posts
Re: Slumber a TUI HTTP Client
#42Delete key does not exist, Fn-Backspace does not work too.
Re: Slumber a TUI HTTP Client
#43https://github.com/darrenburns/posting is another TUI client.
Re: Slumber a TUI HTTP Client
#44TUI stands for "Text User Interface" not "Terminal User Interface" considering that the point of TUI vs GUI is to distinguish text mode from graphical mode. The word "terminal" isn't really meant to imply text even if quite a few terminal emulators are, indeed, text mode; rather it typically means that the UI is drawn by some other machine than the one you're touching. For example, a very popular Windows Server featu…
On the other hand, there are many elements in the user interface that are not text. In fact, I think it would be quite understandable if one even separated REPLs like bash or octave to be "text user interfaces" while applications that make use of character placement and border special characters "terminal user interfaces", because they use means beyond text stream to communicate with the user. One might even render s…
These characters _are_ text though. They can be copy pasted like text, I can use them in my text editor, you can stick em in a string.
Re: Slumber a TUI HTTP Client
#45The potentially disheartening thing about the ability to create apps like this, they are just low effort are they even worth sharing anymore? I have personal clones of Postman, Teux Deux, Goodreads and a few other utilities. Previously I would clean them up, document, and share out, but now I don't bother with most of it. Just not worth it, when people can make their own customized to their whims.
Re: Slumber a TUI HTTP Client
#46For those who are using Emacs, https://github.com/federicotdn/verb provides similar UX, I have been using it as a postman alternative for quite some time.
Re: Slumber a TUI HTTP Client
#47These small utilities are great, now so quick and easy to create. I made a TUI version and then grew tired of it and ported it to Electron, took less than an hour for each. For those complaining about YAML format, you can create your own in less than an hour using whatever format you want. The potentially disheartening thing about the ability to create apps like this, they are just low effort are they even worth shar…
Re: Slumber a TUI HTTP Client
#48These small utilities are great, now so quick and easy to create. I made a TUI version and then grew tired of it and ported it to Electron, took less than an hour for each. For those complaining about YAML format, you can create your own in less than an hour using whatever format you want. The potentially disheartening thing about the ability to create apps like this, they are just low effort are they even worth shar…
Re: Slumber a TUI HTTP Client
#49Earlier quoted context omitted.
YAML: - - "hello" YAML expanded: - - "hello" JSON (typical formatting): [ [ "hello" ] ] And EDN for good measure: [["hello"]] I know which one I prefer :) Silly example perhaps, but once you have X lists nested in Y lists, it does become a lot easier to see why some prefer a bit more visually hierarchically stronger syntaxes
I still prefer ini files for configuration. Easier to grep and sed.
Re: Slumber a TUI HTTP Client
#50TUI stands for "Text User Interface" not "Terminal User Interface" considering that the point of TUI vs GUI is to distinguish text mode from graphical mode. The word "terminal" isn't really meant to imply text even if quite a few terminal emulators are, indeed, text mode; rather it typically means that the UI is drawn by some other machine than the one you're touching. For example, a very popular Windows Server featu…
TUI also means terminal user interface. But this is wrong: > it typically means that the UI is drawn by some other machine than the one you're touching I guess you're conflating thin-client terminal in the networking sense vs vt100 hardware terminal lineage (where "terminal" comes from here), but it means a text mode interface that runs in the terminal emulator and uses, say, ansi escape sequences. Rather, when you s…
Yes, I didn't really think to separate the two. While my examples of ssh/telnet/rlogin are all of the networking variety, I didn't mean to exclude RS-232 (which the VT100 used). Regardless of whether the wire is for serial or packet data, if you're at a terminal (including any of the thin/dumb/smart varieties), you're not at the box doing the heavy lifting because that's on the other end of a wire representing an important demarcation, a demarcation that doesn't really apply to a local app running a text-mode user interface (or if the mental gymnastics are performed that does introduce such demarcation even within a local app -- think backend vs frontend -- then all local apps are terminals).