Why do we need this over something like ratatui.rs? I don't see the use-case in any of this and it is some sort of vapourware that has a private alpha? I don't get it.
Seems like this hype around TUIs makes no sense at all and sounds like a fad. Maybe it is time to move on.
you've done something to the scroll that makes it nearly impossible to move the text and read below
please do not override default scroll behavior
I def wanted to read more, I'm playing around with retro games and agents, using emulators and old terminal games slippedy mind (I also just want to give FF1 a shot first)
I am aware of issues. Note that this is not a "website" in the regular sense of the word. This is actually a TUI app written in rust and compiled to wasm (and other platforms too: https://github.com/ronilan/incredible/releases) as parrt of alpha testing of the Incredible TUI framework.
Creating the screen, reading a markdown file, laying out the text, colouring it, enabling the scroll, managing it, changing the mouse pointer over the scroll bar, responding to the drag on said scroll bar, underlining the links, colouring them when they are hovered, removing colour when they are not, inverting them when they are clicked, loading the next markdown page, changing the browser URL hash, the keyboard shortcuts, Ctrl+e to select all, Ctrl+c to copy, etc. - it's all coming from Incredible TUI framework, not the browser.
I'd make a website with regular website technologies, and then create some view/iframe/page that has the usable TUI in the browser (if that's the concept). Keep pages that are mainly text / docs in that standard tech, these oddities and overrides are better when the user knows it's going to happen, or another way
1. landing page, normal tech so you don't turn people off immediately
2. app/tui page, linked to from landing page letting the user know you did some cool rust/wasm/tui thing, don't necessarily have to call out scroll issues, it will be understood/accepted by way of the weird web tech they have clicked through to
nice, one thing you might also do, in your wasm version, is figure out how to replicate scroll momentum, that's the thing that makes it feel weird, I can flick a page and it will scroll for a while
I guess people love their retrograming experience for UNIX, VMS, MS-DOS and CP/M games.
What kind of TUI library has a private alpha?
Why do we need this over something like ratatui.rs? I don't see the use-case in any of this and it is some sort of vapourware that has a private alpha? I don't get it.
Seems like this hype around TUIs makes no sense at all and sounds like a fad. Maybe it is time to move on.
you've done something to the scroll that makes it nearly impossible to move the text and read below
please do not override default scroll behavior
I def wanted to read more, I'm playing around with retro games and agents, using emulators and old terminal games slippedy mind (I also just want to give FF1 a shot first)
Are you on mobile? What browser?
I am aware of issues. Note that this is not a "website" in the regular sense of the word. This is actually a TUI app written in rust and compiled to wasm (and other platforms too: https://github.com/ronilan/incredible/releases) as parrt of alpha testing of the Incredible TUI framework.
Creating the screen, reading a markdown file, laying out the text, colouring it, enabling the scroll, managing it, changing the mouse pointer over the scroll bar, responding to the drag on said scroll bar, underlining the links, colouring them when they are hovered, removing colour when they are not, inverting them when they are clicked, loading the next markdown page, changing the browser URL hash, the keyboard shortcuts, Ctrl+e to select all, Ctrl+c to copy, etc. - it's all coming from Incredible TUI framework, not the browser.
Feedback on all aspects much appriciated.
I'd make a website with regular website technologies, and then create some view/iframe/page that has the usable TUI in the browser (if that's the concept). Keep pages that are mainly text / docs in that standard tech, these oddities and overrides are better when the user knows it's going to happen, or another way
1. landing page, normal tech so you don't turn people off immediately 2. app/tui page, linked to from landing page letting the user know you did some cool rust/wasm/tui thing, don't necessarily have to call out scroll issues, it will be understood/accepted by way of the weird web tech they have clicked through to
I see it on mobile/desktop | chrome/vivaldi
Done.
https://news.ycombinator.com/item?id=49905574
nice, one thing you might also do, in your wasm version, is figure out how to replicate scroll momentum, that's the thing that makes it feel weird, I can flick a page and it will scroll for a while
thanks. will consider.
[dead]