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

Make using multiple template sets more convenient #26

Closed
s-ol opened this issue Oct 12, 2015 · 3 comments
Closed

Make using multiple template sets more convenient #26

s-ol opened this issue Oct 12, 2015 · 3 comments

Comments

@s-ol
Copy link
Owner

s-ol commented Oct 12, 2015

Ideas:

  • remember last used template instead of defaulting to i3
  • reorganize themes in subdirectory (~/.config/themer/themes) for simpler directory structure (and no reserved names)
@s-ol s-ol changed the title Make different template sets more convenient Make using multiple template sets more convenient Oct 12, 2015
@s-ol s-ol added this to the v2.0 milestone Oct 12, 2015
@Kashyap12
Copy link

Hi @s-ol , I am new to open source, would love to contribute

@s-ol
Copy link
Owner Author

s-ol commented Nov 24, 2016

Hey @Kashyap12. After checking your profile, I assume you came here from the up-for-grabs site or something similar. Here are a few questions for you:

  • do you know what this project is exactly?
  • have you managed to set it up and tried using it?

It is not a problem if you were to answer 'no' to either of the questions. The reason I am asking is that the project is right now in a 'weird' state; it is more or less functional and full-featured, but I am not happy with most of it and want to rewrite the bigger part from scratch. This issue is concerned with one of the core parts of the current structure (this doesn't mean it's hard to implement, though), and would likely be completely scrapped for the upcoming rewrite. If you don't mind that you can of course still submit a PR for this and I will merge it if it fits the current standards.

I am also sorry for not moderating these issues and the up-for-grabs labels more closely, at the moment #40 would probably be a better place to start, I suggest you take a look. It is less involved with boring, core part of the program and more with the actual user side, smaller, and likely to survive the rewrite and make it into v2.0.

If you like the project and are personally using it or would at least be considering to use it personally, have some python experience or at least some comparable scripting language, I would be even more happy to have someone work on a themer 2.0.

@s-ol
Copy link
Owner Author

s-ol commented Apr 10, 2017

Superseded by #51.

@s-ol s-ol closed this as completed Apr 10, 2017
@s-ol s-ol modified the milestones: future, v2.0 Apr 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants