LOTW VS rich

I see this directory: https://github.com/linuxontheweb/LOTW/tree/main/root/code/ap...

how do I play any games on your "https://linuxontheweb.github.io/" demo?

So, this is about popups inside of browser windows, is it? And not about popups in Windows/Mac/Linux desktops? Because I couldn't start making up my mind until close to the end of the article.

FWIW, I do make some use of modals in Linux on the Web (source code, admittedly somewhat sloppy: https://github.com/linuxontheweb/LOTW/blob/main/root/code/mo...). In fact, I just tried to make a post about a new app I'm working on (that happens to use them) called "HackerNotify": https://news.ycombinator.com/item?id=32358782

I think I'll take this opportunity to introduce "HackerNotify" (https://lotw.site/net/HackerNotify.app), which is a different kind of interface into the Hacker News backend (via firebase).

You can tell how many total comments a story has by the color of its title. The ranking from low to high is: dark blue -> light blue -> aqua -> green -> yellow -> orange -> red.

It has a keyboard-centric interface. Here is the breakdown:

'Space' toggles an item's open/closed state.

'Tab' is used to move between items in a list. If an item is in the open state, pressing tab will focus the first item in its list. Otherwise, it will focus the next item in the list that the item is a member of. This is really the "go to" key in the app. If ever in doubt, just hit 'tab'.

'Enter' is for opening the link (in a new window) to which a "story" item refers. (You can also click the link to open it.)

'c' is for popping open a comment window to respond to whichever item is in focus.

'n' is for setting a "notice" to periodically poll the backend for new replies to a given item (story or comment). The current polling period is one minute.

'/' is for cycling between the 3 screens of the app (Top stories, Watched stories and Notifications).

'1' is to jump to the "Top stories" screen. (All story titles that start out as "Launch HN:" are filtered out of the listing.)

'2' is to jump to the "Watched stories" screen. "Watched stories" is the screen that will hold the top level story items that contain notification items that are no longer embedded in the DOM of the "Top stories" screen.

'3' is to jump to the "Notifications" screen.

'x' is to delete a given notification. The app currently allows for 5 notifications to be set at any given time.

'r' is used to refresh a given item to sync it with the firebase backend.

'Esc' allows you to "escape out" of embedded items. This key also automatically closes items.

'Ctrl+Esc' allows you to immediately escape out to the top level listing, closing all embedded comments along the way.

Finally, since there may still be a bug or two in the app's logic, 'Alt+l' is the "hard reset" shortcut that forcefully closes and blurs every item on every screen. If you need to invoke this shortcut, just pressing 'Tab' again should get you back on your feet.

The link I provided above allows you to open up a Linux on the Web app in the experimental "app mode". If you want to play around with it in its native environment, though, you will need to need to see the LOTW README: https://github.com/linuxontheweb/LOTW#applications

Now, take a look at the following file in my github repo: https://github.com/linuxontheweb/LOTW/blob/main/www/img/screenshot.png

Yeah, I don't personally mess with anything but Chrome, and I consider supporting browsers that are not Chromium-based to be a fork of the entire project.

Per the Disclaimer in the Github README (https://github.com/linuxontheweb/LOTW/):

---------------

LOTW is developed in the crouton environment, which involves ChromeOS in developer mode. All development and testing is currently done on a Chromebook, using an up-to-date Chrome browser.

The system should basically work in any modern browser and host OS, but there are likely many tiny glitches that degrade the user experience in other browsers and/or operating systems.

---------------

The crucial fact of LOTW is that it is based around the concept of a full-featured, sandboxed file system in your browser. Only Chromium-based browsers natively support that kind of thing via 'webkitRequestFileSystem'.

That being said, there is a shim/polyfill that is supposed to load and take care of that (https://github.com/linuxontheweb/LOTW/blob/main/www/js/fs-sh..., created by Eric Bidelman when he was at Google). Last I knew, Firefox seemed to work with it.

I found it funny that he put out this tweet in which he said, "Some people are no nonsense, but, personally, I like a little nonsense" (), only like a day after I started posting here to try to generate excitement for my site (see my username).

Now, take a look at the following file in my github repo:

That image is prominently displayed on the main README of the repo, and as you can tell, it was committed before Elon made his comment. (Also, there are some forks and stars in the repo now, whereas before I started posting here, there were none, so I know at least some people have been appreciating my work.)

You should be able to plainly see that there is "a little nonsense" in that image! I'm just wondering if you all think that is a coincidence or not...

One reason I started working on "Linux on the Web" is that I wanted to work within a paradigm (web development) that has strong connections with current practices but that also can allow me to iterate in directions that are more related to the nuts and bolts of our shared physical reality.

One thing that nobody ever talks about are the more hardware-centric possibilities of the web platform such as WebUSB, but I would absolutely love to start playing around with it in order to allow for an interface of real world objects with the LOTW system -> https://github.com/linuxontheweb/LOTW

There is an open issue [1] on GitHub to make it more modular and get rid of markdown and syntax highlighting but I have no hope for rich to get more minimal.

[1]: https://github.com/Textualize/rich/issues/2277

I hope he doesn't mind, but the creator of Rich and Textualize is a good guy, and Scottish: https://www.willmcgugan.com/about/

https://www.textualize.io/

https://github.com/Textualize/rich

They keep getting improved error messaging and this is one of my favorite features. But I'd love if we could get some real rich text. Idk if anyone else uses rich, but it has infected all my programs now. Not just to print with colors, but because it makes debugging so much easier. Not just print(f"{var=}") but the handler[0,1]. Color is so important to these types of things and so is formatting. Plus, the progress bars are nice and have almost completely replaced tqdm for me[2]. They're just easier and prettier.

[0] https://rich.readthedocs.io/en/stable/logging.html

[1] Try this example: https://github.com/Textualize/rich/blob/master/examples/exce...

[2] Side note: does anyone know how to get these properly working when using DDP with pytorch? I get flickering when using this and I think it is actually down to a pytorch issue and how they're handling their loggers and flushing the screen. I know pytorch doesn't want to depend on rich, but hey, pip uses rich so why shouldn't everyone?

colors.crumb extends Crumb with basic terminal styling functions and RGB, HEX, ANSI conversion functions. It is in the realm of JavaScript's chalk and Python's rich but slightly more functional 😉.

I am working on a new python project and one of the first things I added was https://github.com/Textualize/rich because of how easy it is to make things look good in the terminal.

I am not rewriting anything but I'd love to have a library like `rich` in Rust: https://github.com/textualize/rich

Add some cool-looking stuff to your output with rich.

You might consider taking inspiration from the rich module. In particular, I like how rich supports inline color theming which seems much more cumbersome in your framework, requiring the use of context managers as well as familiarity with how your framework structures color objects. Other than that though, I'm impressed!

Today I released coBib 4.0, my console bibliography manager written in Python, which now uses rich and textual to provide a cohesive and modern user experience in both its CLI and TUI.