@jesse Are there any naming conventions you’d like us to use when creating 3rd party Plugins to differentiate them from “official” Kaleidoscope plugins? For example, in the Java world, Maven uses a plugin naming convention of <pluginName>-maven-plugin for 3rd party plugins and maven-<pluginName>-plugin for official plugins. I wasn’t sure if you might want to do something similar where Kaleidoscope-LEDEffect-Foo is an official plugin and LEDEffect-Foo-Kaleidoscope (or perhaps LEDEffect-Foo-Kaleidoscope-Plugin) is a 3rd party plugin.
Of course I’m not sure if your plans are that some plugins may eventually be “absorbed” into the Kaleidoscope project in which case the need to have to rename them might be problematic.
There is indeed the intent of migrating plugins into (and possibly out of) the core. I haven’t heard discussion of naming conventions, but it’s not a bad idea. The code is very much not my bailiwick, so I’ll leave all further commentary to Jesse and algernon. I know jesse is away this weekend at a convention, so he probably can’t jump in for a couple days at the soonest.
Jesse has been able manage a KickStarter manufacturing project, create and develop a massive Open Source Project, and raise a new born all at the same time. Answering a Forum post while at a convention is child’s play for him
True. Makes me feel like still being Human 1.0, while Jesse is already Human 2.0. Same for Algernon except he just got two Human 3.0, as I recently read in his blog.
