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

[Enhancement] Modular Structure of Theme Definition #43

Open
kevinmatthes opened this issue Jul 17, 2022 · 0 comments
Open

[Enhancement] Modular Structure of Theme Definition #43

kevinmatthes opened this issue Jul 17, 2022 · 0 comments

Comments

@kevinmatthes
Copy link
Contributor

As mentioned in #30 by @mcobzarenco, the colour themes shall be outsourced from the source code in future releases. With this issue, I would like to suggest a procedure on how the themes could be added very easily.

zee has a configuration directory in which the settings are stored. I would like to suggest to add a themes directory within this directory to store the themes in there. The themes themselves could be exported as RON (Rust Object Notation) files that can be added by the user. When the command to change the theme is triggered, a file selection dialogue just as for the file opening can be triggered to show the available themes and select them by name. The theme directory should be scanned for valid themes first when the selection dialogue is triggered.

Longer term, the theme directory should support subdirectories to clone Git repositories into which contain the zee themes. That way, all the current themes could saved in a new repository within this namespace as RON files and then be cloned into the configuration directory, at option.

I am looking forward for your feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant