We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We currently use urwid for ikhal and while it works fine, its development seems to have stalled. On the other hand, a new contender for the same space has emerged: textual. Textual promises to be faster and have better maintenance (two full time developers).
We should evaluate what advantages textual has and if the work of porting ikhal to textual is worth it.
The text was updated successfully, but these errors were encountered:
I see it uses rich under the hood, which has always caught my attention.
I think this might be a really interesting fit, and a good opportunity to refactor and improve UI responsiveness a bit.
Sorry, something went wrong.
Textual has matured a lot in the last few months, and I see it as a very good alternative to the harder-to-write urwid :)
I would love to see that in khal!
No branches or pull requests
We currently use urwid for ikhal and while it works fine, its development seems to have stalled. On the other hand, a new contender for the same space has emerged: textual. Textual promises to be faster and have better maintenance (two full time developers).
We should evaluate what advantages textual has and if the work of porting ikhal to textual is worth it.
The text was updated successfully, but these errors were encountered: