-
Notifications
You must be signed in to change notification settings - Fork 286
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
Update the style of application list #179
Comments
Perhaps move this to a wiki page instead? My rationale is that adding an app to the source code of the library doesn't really seem like it is a meaningful feature. It's something that is about the library, not something that is part of the library. I added https://github.com/tui-rs-revival/ratatui/wiki/Apps (which I copied from APPS.md) It might be nice to have both tui and ratatui apps listed on that page with an indicator of which ones have been migrated. Reorganizing that page is still worth keeping this issue open for though. |
If we split it in different categories should we keep them in different markdown tables ? or maybe have something like I proposed here, I don't know which one is more readable |
I like your categories and subjectively prefer that suggested layout over the tables that we have currently. Any prefs @orhun? |
PR opened here we can work from that |
Yeah, I think we don't need the author. |
It makes sense to separate something which is not directly related to the library but in that case we need to make use of the Wiki more often to make it visible. Maybe after #184 is merged, we can remove that file and add a note in README.md about it is now a part of the Wiki or something. I'm okay with either way and I think having a separate file definitely makes the application list more apparent to the user. Need some comments on this so maybe create a issue/discussion? |
Closing as merged (and the wiki conversation has moved to #185 |
Problem
See fdehau/tui-rs#704
Solution
We can possibly do a similar thing and split the applications into categories.
Alternatives
None.
Additional context
None.
The text was updated successfully, but these errors were encountered: