[Feature request] WASM Frienly

[andreytkachenko]

May be my question is not addressed correctly, just close issue.
I working on WASI based plugin system. And for terminal applications such as helix I think the best approach would be just compile applications like sidetree to WASM and communicate through stdin/stdout. Most of such programs are based on TUI which is based on crossterm, but inside crossterm there are some ioctl calls (to get terminal size, cursor position and other). Is it possible to add some WASM backend which would communicate through stdin/stdout like SSH, or has some backend trait and make generalized version of crossterm?

[TimonPost]

It could be some feature flag that implements different api for wasm for those particular functions. I am not much in favor of an entire backend abstraction as i'd like to keep this library as minimal as possible.

[LinusU]

For wasm32-wasi I think that most things should be provided out-of-the-box, raw mode is probably blocked on WebAssembly/WASI#161 though...

Some imports needs to come from std::os::wasi instead of std::os::unix, e.g. AsRawFd.

[jrvidal]

I've lightly forked crossterm to support a web version of a TUI of mine:[*]

• Repo: https://gitlab.com/_rvidal/pneo
• Demo: https://_rvidal.gitlab.io/pneo/
• Fork: https://gitlab.com/_rvidal/crossterm/-/tree/0.27-pneo

FWIW, the changes that I needed were fairly minimal, just adding a few unimplemented!() "implementations" to get it to compile. The "big" feature that I was missing is a way of getting an EventStream from an arbitrary futures::Stream<Item = Vec<u8>>. I hacked around that by exposing event::sys::unix::parse. Which makes me wonder whether there would be any value into extracting that into a separate crate.

Anyway, sharing just in case it's useful.

[*] Not the first person to do this, see here.