gyscos / gyscos/cursive

Allow special backends to support additional features

Open
#85 0 comments 0 reactions 0 assignees View on GitHub
backends enhancement internals
Dominant language
Rust
Stars
4.8k
Forks
270
Avg merge
5d 19h
Merged PRs (30d)
2

Description

Some exotic backends like BearLibTerminal are in effect full graphical applications, and therefore not constrained by the terminal input system.
This means for those backends, a lot more input can be detected.
I don't want to add a bunch of event keys that are only supported on one backend, but it'd be a waste to hide this feature entirely.
I'm therefore thinking of adding a custom event variant, which would be backend-specific.
It means a part of the backend (the "custom" event enum) would need to be made public. Applications would then have the opportunity to tie themselves to a specific backend and use these custom events.

Still unsure if it's all worth it. I don't want to fragment too much users between backends.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.