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
Rename DropLep back to Droplet #77
Comments
I'm not sure, if snippet would be a good name... But as you can do much more than simple include a snippet (even if it is supposed be used for simple things) maybe snippet is too irritating? |
Hm, snippet is already in use for another kind of module. But as I don't like those modules - they are included every time, if they're used or not - we could simply remove that type and replace it with our kind of droplets / snippet. Hm. |
Snippets are the former solution and it where really snippets - nothing more. Too, this addon is already in use (and in the heads). In kitFramework im using kitCommands instead of Droplets and they are very powerfull. |
Hmmm... "In the heads" counts for Droplets, too. ;) |
So what is our decision? |
So if no one wants to decide I do. :) I will rename all back to Droplet. |
Done. Please open a new issue if there are any faults in result of this. |
As DropLep is the name the Lepton Devs chose for the Droplets module, we should go back to the original name - or find a unique new one. Any suggestions?
The text was updated successfully, but these errors were encountered: