VJ Henke

Just the top of my head I can think of some categories: * Compatability -> For Hardware (like pen drawer g-code, midi devices, kinect or similar) or Software (like syphon...

I am wondering how the labeling would be presented to newcomers. I don't see a decent way of doing it with GitHub. Maybe as a separate page in the [guide](https://guide.openrndr.org)...

On that note, I see a similar problem with [[orx-compositor]](https://github.com/openrndr/orx/tree/master/orx-compositor). There are funtions provided ike `deepDestroy` that would allow cleanup, but the important vars themselfs are kept private. This follows...

I am also willing to write a PR for orx-compositor specifically. I would like a second opionion before authoring it though.

Hi Abe, I was not aware of `ApplicationPreload` and couldn't figure out how to use one's custom subclass of that. The guide page should be adjusted for sure :D Feel...

> In https://github.com/openrndr/openrndr-guide/wiki we had planned a section for reusing code. Maybe both approaches could be listed there, together with others like creating a library, or sharing a source folder...

I was not thinking for the people unfamiliar with Kotlin. As an Android Dev, I am maybe too used to it :D Showing how to use `Preload` upfront is the...