This would argue for a greater emphasis on IO / hardware support – in particular, camera support opencv / boofcv would be essential for classes focusing on reactive sketches – Kinect is also popular. As an extensible platform, this starts to look like the question would be what not to included, and why? So now you are looking at 30-50+ libs again rather than 10-15
I think a way to approach this would be to write an openframe-proclibs install script that works with the Processing-Deps repo:
(Edit: its updater script is in a separate repo, processing-deps-updater/update.rb at master · josephtaylor/processing-deps-updater · GitHub)
That repo was created for maven, but it is a big-bunch-of-jars for processing libraries.
- The script installs a default list based on processing-deps
- users can customize the script to add / remove libs not in the default list
- to add a new lib for openframe, contribute it to processing-deps and then add it to the install script.
I think it sounds like a great idea. I have low bandwidth right now, unfortunately, but can chip away at it occasionally. No reason not to get started now, and perhaps others from the forums will join in.
Despite being time-poor, I think this has a lot of potential for digital arts classrooms and public spaces, and really appreciate what you are doing, so I want to help maintain moment.
I’ve invited you to the spreadsheet above – perhaps create another worksheet on it and populate with the processing_deps directory list if that looks useful?