kui.nvim
arcan
kui.nvim | arcan | |
---|---|---|
4 | 34 | |
180 | 1,503 | |
- | - | |
4.6 | 7.5 | |
11 months ago | 5 days ago | |
C | C | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kui.nvim
-
Ask HN: Is the line between TUIs and GUIs blurring?
I've heard a lot that a benefit for using terminal software over GUI apps is that they use much less resources. And that's why its better to SSH into servers rather than have them use up resources for a display server, Quartz X11 Wayland etc.. But terminals aren't just outputting raw text, they have text and background colors per character, TUI frameworks have been made for them to essentially have GUI-like elements, like Neovim and Ranger. Things like the [Kitty Graphics Protocol](https://sw.kovidgoyal.net/kitty/graphics-protocol/) seem to blur the lines. While I don't know the technical details (please explain if you can!), it's nice that it can render images in the terminal, but how is it different, especially the technical details and resource demand (CPU GPU RAM etc.) to display servers?! Does it work without a display server running on the client, like a "raw" linux terminal where the desktop environment isn't loaded?
I haven't look at this much either but there's also [kui.nvim](https://github.com/romgrk/kui.nvim), a terminal GUI framework built on-top of Kitty Graphics and it seems to escape the TUI constraint of only being able to visualize things with text characters, being able to draw elements of any length. There's a [comment](https://new.reddit.com/r/neovim/comments/110znd4/comment/j8f6pb6/?utm_source=share&utm_medium=web2x&context=3) on this [Reddit post showcasing kui.nvim](https://new.reddit.com/r/neovim/comments/110znd4/kuinvim_an_experiment_into_a_real_graphical/) discussing the benefits of a terminal are that it's not a GUI. But if you were to use this, then how much would it be different from just using Obsidian with its various plugins along with with [Obisidian-bridge.nvim](https://github.com/oflisback/obsidian-bridge.nvim)?
So what makes a terminal a terminal, different from GUIs and full desktop environments? Is it the low resource usage, is it still low with Kitty Graphics and kui.nvim? Is it the keyboard-centric interaction for higher efficiency? Is it because of the other benefits of commands environments, like unix stdin and stdout piping? If you want full blown GUIs in a terminal environment then how is it much different than using a GUI app with full keyboard navigation and text inputs? How do you feel about rendering full GUI graphics in a terminal?
Personally I like the idea of rendering graphics in a terminal environment is it would be overall better than using GUI apps for the reasons listed above, but I'm feeling reluctant on that.
-
kirby.nvim: design update
Not sure if it's clear enough, but it's based on https://github.com/romgrk/kui.nvim
-
[UI question] Is there any way to make float window style like IDEA or VS Code?
It is technically possible, but you'd need something experimental like this: https://github.com/romgrk/kui.nvim
- kui.nvim - an experiment into a real graphical framework, with kitty & cairo
arcan
-
State of the Terminal
You might be interested in Arcan desktop engine ( https://arcan-fe.com ), which as a tui api for clients. It has been used to build an interesting shell experiment: https://arcan-fe.com/2022/10/15/whipping-up-a-new-shell-lash...
-
Is there a cross-platform graphics library that can run without X or wayland that runs on the BSD's bare-metal?
Something like this ? https://arcan-fe.com/
- X.org Alternatives? MicroXWin, Wayland, Y, DFB, Xynth, Fresco, etc. (2009)
-
kirby.nvim: design update
This requires to remove the terminal emulator plus adjust IPC, like what arcan is doing: https://github.com/letoram/arcan
-
VT330/VT340 Sixel Graphics
kragen, what's the current status of BubbleOS?
Also, I'm curious what you think of Arcan (https://arcan-fe.com)
-
Qt Wayland: support for surviving a compositor crash was merged
afair ChromeOS do implement it, harder to find the commit but also know Arcan mentioned elsewhere in this thread added it quite a while ago https://github.com/letoram/arcan/commit/d547c55565a848946422e24eee324c8ed091ff15
-
not the biggest Xorg fan, but it isn't all sunshine and rainbows in the promised Wayland.
I managed to find this one in my history: Arcan it does has a cool name ngl, I never tried it though
-
Wayland blows ass and mostly functions as a launcher for x.org processes. Nobody needs, wants or asked for Wayland. It's nobody's fault but the assholes at FreeDesktop
Lol not arcan
-
A Guide to the Terminal, Console, and Shell
See https://arcan-fe.com/, in particular Lash: https://arcan-fe.com/2022/10/15/whipping-up-a-new-shell-lash...
-
Is Wayland really the best solution
LOL. Not. Meanwhile, one dude managed to write an entire display server that handles, both, Wayland and X11 apps: https://arcan-fe.com/
What are some alternatives?
kui-demo.nvim - kui.nvim demo
hello-wayland - A hello world Wayland client (mirror)
kirby.nvim - Fuzzy picker for neovim - using kitty graphics protocol
waybox - An openbox clone on Wayland (WIP)
fzy-lua-native - Luajit FFI bindings to FZY
openbsd-wip - OpenBSD work in progress ports
glaucus - A simple and lightweight Linux® distribution based on musl libc and toybox
ydotool - Generic command-line automation tool (no X!)
rdrview - Firefox Reader View as a command line tool
etlegacy - ET: Legacy is an open source project based on the code of Wolfenstein: Enemy Territory which was released in 2010 under the terms of the GPLv3 license.
gluon - a modular framework for creating OpenWrt-based firmwares for wireless mesh nodes
obs-gnome-screencast - GNOME Screen Cast OBS Studio plugin