Live data from Hacker News

Vtm: Text-Based Desktop Environment

github.com

61–70 of 98 posts

Re: Vtm: Text-Based Desktop Environment

#61
post #56

Earlier quoted context omitted.

We've done it twice. Many terminals run under electron or equivalent browser interfaces. So we've implemented TUI in the GUI as well!

That’s also applies to literally every terminal emulator written since xterm. Most of the modern terms these days have GPU acceleration too.

No. This isn’t true. Most terminals are native. They don’t run under a browser engine.

Re: Vtm: Text-Based Desktop Environment

#62
post #56

Earlier quoted context omitted.

That’s also applies to literally every terminal emulator written since xterm. Most of the modern terms these days have GPU acceleration too.

No. This isn’t true. Most terminals are native. They don’t run under a browser engine.

A browser engine isn’t a prerequisite for something using a graphical framework nor running on a desktop environment

Re: Vtm: Text-Based Desktop Environment

#63

Earlier quoted context omitted.

I used DESQview for a number of years, and always think about it when see new TUI systems https://en.m.wikipedia.org/wiki/DESQview

I tried to use desqview but it was too slow on my 386 33mhz machine… not sure how much RAM it had back then but I recall it was the bottleneck and swapping to disk caused everything to lag.

I think you are confusing old memories here.

DESQview did not do any memory management of its own, and it did not use graphics. It was entirely local and had no networking. It was famously fast. It was a DOS multitasker so it managed DOS tasks, meaning multiple slots of 640kB. On a 386 with 4MB of RAM you could have 6 full-size DOS VMs with a bit left over.

If you were a power user you could still have say a big 1-2-3 spreadsheet in EMS plus a few DOS VMs.

DESQview delegated memory management to QEMM386, and QEMM386 did not do swapping. It didn't need to.

DESQview/X was a totally different product, with a full GUI, so much bigger and slower -- and it added an optional extension that added full virtual memory with swapping to disk.

I am wondering if you are mixing up DESQview (small, fast, local) with DV/x (big, complicated, networked, had optional VM)?

Or indeed DV/x with something else altogether? OS/2 maybe?

Because if it was swapping, it wasn't DESQview, not in any normal sane config anyway. It might be possible to add DV/x VM to plain old DESQview but I never heard of anyone doing that.

Re: Vtm: Text-Based Desktop Environment

#64
post #6

There was something similar a few years ago which ran over an ssh connection and had a zoomable ui of sorts. I can't find the link -- does this ring a bell anywhere?

It was this very tool. It could be sshed into with

ssh vtm@netxs.online

That domain is dead now

Re: Vtm: Text-Based Desktop Environment

#65
post #6

There was something similar a few years ago which ran over an ssh connection and had a zoomable ui of sorts. I can't find the link -- does this ring a bell anywhere?

It was this very tool. It could be sshed into with ssh vtm@netxs.online That domain is dead now

Hooray, thank you!

When I said "zooming" I was thinking of the white tethers attached to each window which would pull them back into a centre bundle. You can see what I mean here: https://changelog.com/news/a-textbased-desktop-environment-i... at the bottom left, the lines going off to a single point.

actually, by zooming out, I can still see the tethers on the windows. The ssh version was quite mind-blowing back when...

Re: Vtm: Text-Based Desktop Environment

#66
post #59

has anyone tried building it from source?

Building with gcc requires ~4Gb of RAM; clang requires ~8Gb. Due to memory requirements, building vtm for a 32-bit target is only possible using cross-compilation. In addition, cmake downloads Lua sources during the build process.

Re: Vtm: Text-Based Desktop Environment

#67
post #65

Earlier quoted context omitted.

It was this very tool. It could be sshed into with ssh vtm@netxs.online That domain is dead now

Hooray, thank you! When I said "zooming" I was thinking of the white tethers attached to each window which would pull them back into a centre bundle. You can see what I mean here: https://changelog.com/news/a-textbased-desktop-environment-i... at the bottom left, the lines going off to a single point. actually, by zooming out, I can still see the tethers on the windows. The ssh version was quite mind-blowing back whe…

This is the same thing as the public demo back then via 'ssh vtm@netxs.online'. There are no public demo servers running now, but you can still ssh to your running vtm instance with any number of connections. In case of using MS Windows you can even get the output in a standalone GUI window via 'vtm ssh user@unixserver vtm'.

Re: Vtm: Text-Based Desktop Environment

#68
post #11

I know I’m missing the obvious here, but is this a terminal multiplexer (like tmux)? Or a tiling terminal emulator (like iTerm, et al)?

The Youtube video embedded on their Github is titled "Tiling Window Manager with Drag&Drop" and from watching it, that appears to be exactly what this is. I don't know if or why it artificially constrains itself to only opening terminals.

It's scary to do something more complex than a terminal emulator until the architecture is unstable. In case of small changes we will have to rewrite a lot. You can play with a couple of built-in demo apps 'vtm --run text', 'vtm --run calc', 'vtm --run test', 'vtm --run truecolor'. You can also run it directly inside the vtm desktop by typing vtm.desktop.Run({ type='calc' }) in the command line of 'Log Monitor'.

Re: Vtm: Text-Based Desktop Environment

#69
post #3

We've come full circle. We invented a GUI to replace the TUI, then reimplemented the GUI in the TUI. Long live the terminal!

We've done it twice. Many terminals run under electron or equivalent browser interfaces. So we've implemented TUI in the GUI as well!

That sounds like the worst thing ever. So many good native terminals to choose from why ruin it with electron.
Post reply on HN