[image] Dynamic macro plugin What is the process for pulling things into Arduino-Boards? Ask @craigdissel and @jesse whether they are ok with it, figure out if the plugin will live under the keyboardio organization or remain under Craig’s name, and if and when things are settled, submit a PR. …

I think everybody is right. (Though @algernon , there’s enough plugin traffic that adding a category is pretty easy. I’ve been wanting to split ‘programming’ up a bit anyway. There’s “user sketches”, “kaleidoscope core” and “plugins” and they’re all pretty different.) It’s not wrong to have a place …

thread per plugin sounds perfect! I was imagining an announcement only category, with discussion squelched, and that sounded wrong. :slight_smile:

I would l like to see a plugin category like we have a programming category. I think these things are related but they are not the same thing. It is nice to be able to search a specific category when looking for something and I think that the programming category would have more noise to sift throu…

Jesse created it here: https://community.keyboard.io/c/programming/Discuss-Kaleidoscope-Plugins-one-thread-per-plugin

[image] amos: I would love to see a plugin manager like Plug for vim or even a full blown package manager that people can add plugins and dependencies too. Something like hex, rubygems, or npm. One of my plans is to do this within the context of Chrysalis (and also provide a CLI tool for thos…

[image] Jennigma: It is my intent to have a plugins page on the wiki that has a listing like this Does such a plugin page in the Wiki exist by now? I just read this topic over. The wish for some sort of plugin manager was expressed several times. Wouldn’t it be a good idea to collect the use…

Here is another topic where the naming of plugins is briefly discussed [image] Third Party Plugin Naming Conventions Programming I personally think that everything should be Kaleidoscope-Plugin-Foo, where Foo is a name that describes the plugin’s use case or behavior. LED…

A closely-related question about third-party (or, more specifically non-Arduino-Boards) plugins is where one should put them when building custom firmware. In the libraries directory, along with the official ones? Symlink’d there? As submodules of one’s own firmware sketch? In a separate library dir…

[image] merlin: A closely-related question about third-party (or, more specifically non-Arduino-Boards) plugins is where one should put them when building custom firmware. In the libraries directory, along with the official ones? Symlink’d there? As submodules of one’s own firmware sketch? In a …

[image] jesse: I’d thought that you could also drop them inside lib/ in your sketch directory. (Though now I wonder if that’s libraries/ inside your sketch dir.) If the IDE supports one of those and the commandline build doesn’t, that’s a bug and something we should fix. I’ll experiment whe…

Managing core and contributed Kaleidoscope plugins

Programming

noseglasses (Noseglasses) November 18, 2017, 12:39pm 20

Here is another topic where the naming of plugins is briefly discussed

Topic		Replies	Views
Preparing plugins for 1.0.0: Looking for documentation reviewers Programming	45	4300	November 17, 2017
User plugin database Plugins	17	2197	January 2, 2018
Kaleidoscope-CMake Programming	19	3092	December 9, 2017
New plugin: Digital Rain (The Matrix falling code effect) Plugins	42	6759	August 9, 2020
Feedback requested: simplified software installation Programming	38	3535	November 10, 2017

Managing core and contributed Kaleidoscope plugins

Related topics