-
Notifications
You must be signed in to change notification settings - Fork 0
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
Review the platform abstraction layer #6
Comments
|
Regarding the color and input stuff: probably take a look at lanterna, that's a library offering some nice abstractions around terminals. It somewhat lacked proper Windows support last time I looked, but I could hack it. |
I've already dropped in lanterna while implementing terminal support and did some preliminary research on unborking windows terminals, so I'm way ahead on this. Guess I'll do something with colors while finishing #5. (tldr on terminals in Windows is that they are messed up beyond belief because of historical reasons. lanterna does works ok in a cygwin terminal and has an AWT terminal emulation mode) |
Well, starting from some stupid version of Windows 10 it should work much better. I think we should support that mode. To enable that shit, we should call |
Not exactly, no. The thing is, lanterna does not have any Windows support to speak of. If it runs in a cygwin environment, it sort of works. If one tries to start it in a |
Well, yeah, mainstream lanterna doesn't. But some time ago I was working on a branch where it is. If there is a necessity, then we'll be able to dust it out.
Heh, but I am! |
(Probably linked with #5)
Currently, the platform abstraction layer is nearly-nonexistent. We need to make an isolated place for all of the platform-dependent things (e.g. key codes,
Display
implementation etc.), so that we have a definitive answer to the question "How do I add the new platform".The text was updated successfully, but these errors were encountered: