3 ms·
This is usually handled by tabs today... not sure that has been ported back to libs like turbo vision yet. I don't think so.
by digisign 5y ago
This is usually handled by tabs today... not sure that has been ported back to libs like turbo vision yet. I don't think so.
- zozbot234 5y agoTab bars are not very TUI friendly though, since the typical TUI has too little space to display a list of usable tab names at all times. Instead there's simply a hotkey which pops up a "window list" for the user to switch to. (There are exceptions when space is genuinely abundant and a side list of "views" or "tabs" to switch to can be kept permanently visible, but they are exceptions.) Here the TUI designer profits from being able to assume that the user can navigate using the keyboard, as opposed to implementing "keyboard shortcuts" as a purely additional feature. (The GUI on the other hand can use design 'tweaks' to minimize the wasted space and perhaps distraction that would normally result from showing an always-visible tab list.)
- digisign 5y agoHmm, I don't agree, with terminals post 2000 or so. My GUI text editor is currently showing about 8 tabs out of a dozen, with ◂ ▸ at the ends. This is comparable to the number of cells in my terminal now, ~100, i.e.: ◂│doc_one.txt ╲ doc_two.txt ╲ doc_three.tx… ╲ doc_four.tx… ╲ doc_five.tx… ╲ │▸ This is 78 "characters" wide and has extra spaces. This is enough space for typical needs, and could work even on relatively dumb terms like the linux console, DOS of yesteryear. A vte high-color term with utf8, 120+ cells wide could potentially double capacity, in number of tabs, filename length, or bit of both.