New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] How to use as a crossterm backend? #6
Comments
Hey I'm really sorry; I just saw this issue.
I was planning to get patches to This is more or less the API the README is describing.
This is what I was trying to do as well and actually why I made this crate! The short answer is that: In general I think if you have your app only use the The longer answer is that you also have to be careful how you actually run your application (as in, how the thing that's usually called an event loop is set up) and how your app is structured; more on this below. The examples in this repo don't aim to be runnable on desktop and the web, but they are all essentially unchanged from the examples they are based on with the exception of the I actually do have an example that does run on the web and on desktop here. That app is structured to have a library crate that both a desktop binary and a web binary crate depend on. The code is a little rough but I think comparing A couple of other odds and ends:
|
I do still plan to get the patches to It's possible to use this stuff right now, as the project I linked to does, but unfortunately I think if you try to use my forks of If you're interested in using this crate with |
I can't figure out what this means: "You should be able to just use crossterm and pass it a Terminal."
And a more general question: I have an app which uses tui / crossterm. I'd like to be able to run it in the browser, in addition to Linux / macOS / Windows which are already supported. Do you have any suggestions on structure, so that all the xterm.js glue code is separated from the rest? Thanks!
The text was updated successfully, but these errors were encountered: