Skip to content
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

Explore Possibility of using tksheet for main activity window #254

Open
aussig opened this issue Jun 7, 2024 · 1 comment
Open

Explore Possibility of using tksheet for main activity window #254

aussig opened this issue Jun 7, 2024 · 1 comment
Labels
enhancement New feature or request investigating Ongoing investigation performance Speed, responsiveness or general performance
Milestone

Comments

@aussig
Copy link
Owner

aussig commented Jun 7, 2024

Currently we manually create loads of individual UI elements for each system tab in activity windows, which works well but has a significant overhead.

We're already using tksheet to manage Discord webhooks in the preferences, and it might be neater, more flexible, more efficient and give more controls to the user if we switch to using a tksheet for the activity table, but only if this keeps the clarity of display and ease of use.

Experiment.

@aussig aussig added enhancement New feature or request investigating Ongoing investigation performance Speed, responsiveness or general performance labels Jun 7, 2024
@aussig aussig added this to the Backlog milestone Jun 7, 2024
@aussig
Copy link
Owner Author

aussig commented Jun 7, 2024

Downside: tksheet uses tkinter as its base, not ttk. This will mean the future theming rework of EDMC will not automatically apply to this component. Note that we will already have this problem, as it's used in the settings window.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request investigating Ongoing investigation performance Speed, responsiveness or general performance
Projects
None yet
Development

No branches or pull requests

1 participant