Hello, as a preface, this is my first open source pr. I'm also more or less making a suggestion, I wouldn't use the code I've pushed as it's fairly crude (and it's my first time writing rust), its just to show what I'm suggesting can work. Maybe this should be a feature request rather than a pr?
I'm a big fan of this project. I was interested in being able to configure the source lists instead of having to do so manually in ~/.local/share/flavours/base16/sources.yaml after retrieving the default schemes and templates with flavours update all. I've only poked around the code briefly and slapped together a simple way of achieving this.
The Config struct now has four new fields:
schemes: A string of the link to a repo of a list of schemes of this format
schemes: A string of the link to a repo of a list of templates of this format
extra_schemes: A list of strings, each a link to a base16 colorscheme repo of this format. This is not implemented in this pr. Let's say I wanted to use the default scheme list with additional schemes, I'd add them to this list.
extra_templates: A list of strings, each a link to a base16 template repo of this format. This is not implemented in this pr. Let's say I wanted to use the default template list with additional templates, I'd add them to this list.
I'm not familiar with the base16 scheme and template repos or how frequently prs are accepted. For the purpose of adding new schemes/templates maybe this solution is overkill if new themes/templates are easily added there. But I would like to be able to specify my own scheme/template lists that are used when I run flavours update all.
Again I'm not the most familiar with your design choice and source code. Is this a reasonable suggestion, does it conflict with any of your design choices? Is there a way of achieving this as is? Would you be interested in implementing this feature at all (I of course would be willing to help with this)?
Regardless of if this idea is implemented, I'm going to use this fork once I finish the functionality I mentioned. I'll make a new pr when I feel it is ready.
Hello, as a preface, this is my first open source pr. I'm also more or less making a suggestion, I wouldn't use the code I've pushed as it's fairly crude (and it's my first time writing rust), its just to show what I'm suggesting can work. Maybe this should be a feature request rather than a pr?
I'm a big fan of this project. I was interested in being able to configure the source lists instead of having to do so manually in
~/.local/share/flavours/base16/sources.yaml
after retrieving the default schemes and templates withflavours update all
. I've only poked around the code briefly and slapped together a simple way of achieving this.The
Config
struct now has four new fields:schemes
: A string of the link to a repo of a list of schemes of this formatschemes
: A string of the link to a repo of a list of templates of this formatextra_schemes
: A list of strings, each a link to a base16 colorscheme repo of this format. This is not implemented in this pr. Let's say I wanted to use the default scheme list with additional schemes, I'd add them to this list.extra_templates
: A list of strings, each a link to a base16 template repo of this format. This is not implemented in this pr. Let's say I wanted to use the default template list with additional templates, I'd add them to this list.I'm not familiar with the base16 scheme and template repos or how frequently prs are accepted. For the purpose of adding new schemes/templates maybe this solution is overkill if new themes/templates are easily added there. But I would like to be able to specify my own scheme/template lists that are used when I run
flavours update all
.Again I'm not the most familiar with your design choice and source code. Is this a reasonable suggestion, does it conflict with any of your design choices? Is there a way of achieving this as is? Would you be interested in implementing this feature at all (I of course would be willing to help with this)?