5 ms·
hey, how else can I change the transparency of my shell with css ?
by agumonkey 9y ago
hey, how else can I change the transparency of my shell with css ?
- alehander42 9y agoyou're kidding, but that's really it: people love to hate on electron, but nobody has a better solution. it's about "I can reuse my web-based UI on all desktops, mobile and web", not about css
- agumonkey 9y agoWell web based uis are subpar IMO, especially accounting for resource cost. /me goes back to emacs
- majewsky 9y agoYou can't. You can only change the transparency of the terminal. This comment (though probably by mistake) manages to perfectly illustrate the "reinventing things that we don't even understand" mindset that's going on in most of tech. (Also, there exist terminals written in C++ with Qt, and QtWidgets has had CSS support for custom styling for at least 10 years, probably much longer.)
- btrask 9y agoThis is a great "well actually" that also manages to be technically incorrect. If you change the styling in your terminal emulator, it changes the transparency of your shell (and other terminal programs).
- AstralStorm 9y agoThe main example would probably be Konsole from KDE. Quite a hog in the world of terminals but doors is things well. Compared to running an electron instance, it is slim.
- JetSpiegel 9y agoWith Gnome Terminal, it uses CSS to style the desktop.
- stephenr 9y agoWhy do you need to use CSS specifically? macOS built-in Terminal.app has had transparency (even varying transparency for focused vs background windows) for years. Edit: oh, maybe you were being sarcastic? It's been a long day.
- agumonkey 9y agoyeah, I was. I understand the appeal of having html/css hyperdynamism everywhere. And at the same time I don't want to pay the price to the point that I prefer living in lotech linux land. I value frugal over potential flexibility these days. I told that often, but the other day I booted win9x (on a pentium 3 or less, some MB of ram, maybe 64) and ran an old copy of turbo pascal 7 (dos). That thing was flying. It had 80% of what I wanted (including, hear this, ascii shadowed floating editing windows.. talk about overfancy) and used zero resources. Today to have that kind of interactions you'd need a somehow recent quad core and 4GB+ of ram. All that mostly for a bit of eye candy (css may be of some use to decorate tokens/entities to give additional info, but I rarely see that).
- pantulis 9y agoOh, Turbo Pascal had those Turbovision-powered ASCII shadowed floating editing windows in 1993 or so, and it flied on a 386 CPU... the P3 would be a screamer for that ;)
- agumonkey 9y agoThanks for that input, I was very curious to know about performance on much older hardware. This makes TP's worht even higher. 600kB total .. can you believe that ?
- pantulis 9y agoTurbo Pascal had more tricks, it could compile to memory (at least in version 5, if memory serves well). Mind you, not a RAM disk, it could compile and run a MSDOS .COM file from memory itself. Following the filenames during compilation was difficult, as they passed so fast (20Mhz 386sx with 2MB). The compilers and IDEs from that era were truly pieces of art. I also remember TopSpeed Modula-2 that also included its own task scheduler for real time DOS (using clock interrupts, I guess).