Closed rubyFeedback closed 2 years ago
This issue is stale because it has been open 365 days with no activity. Remove stale label or comment or this will be closed in 30 days.
This issue was closed because it has been stalled for 30 days with no activity.
Yo folks - this is more a loose idea, so just to keep the issue tracker clean, I propose to keep this issue open for not longer than 3 months, perhaps even less. This is mostly a bit of brainstorming, which isn't good for implementing something, but just worshipping interesting ideas! So please feel free to close this issue, but if possible I'd like it if could be open for a few weeks, and others comment on it before it closes (not sure if github issue trackers finally have an auto-close, but that would be quite convenient).
So before I explain the idea, let me explain this a bit.
I think I found conky in ... 2009? I don't remember but it was a LONG time ago.
I tested various config files and setups, aka themes and what not. Because my brain power is quite limited, I tend to opt for simple. :P
But I am always looking at nifty screenshots.
Now - often they come with a config file, so people can just use that config file. But as time passes by, old config files may be lost. And sometimes you only see an image but not the conky file, so you don't know HOW this was built. You can probably re-build it on your own with some knowledge easily, but not everyone has that knowledge or time.
So this led me to the idea here ...
What if we could make all screenshots and conky-config files reproducible?
I don't mean ALL of them, mind you - I mean those that have been publish and are somewhat popular (well, several dozen users world-wide I'd suppose at least, so this excludes the solo-users).
So I kind of think of conky not only as the display manager, but also an "add-on / theme" loader.
For instance, just to continue that idea:
^^^^ this would list all available themes, or if there is too many, categories.
^^^ this would install that theme or name of the config.
One name is the default; but alias names with the same name could be used such as:
This could also be hosted by github perhaps, but optionally could be host somewhere else.
The main idea behind this is to allow people to quickly switch between themes for their config files via the commandline. Yes, they can gather the content for the file via the www, but this is an extra step, and some config files for conky may vanish over the years. So this may help preserve themes, and allow users to adapt it.
Anyway, I'll stop here because I am not entirely certain how useful that idea is, how many other people may think this is a good idea or bad, so ... happy commenting! \o/