@jeremydouglass thank you so much for elaborating on this. It’s very comprehensive.
-
The /code subfolder idea seems to be very easy and useful way. I’m going to do some test. But thanks for the heads-up about large files. You definitely have got a point there.
-
The idea of a bundle or download of all libraries in
sources.conf(in Contribution Manager) seems easier but also like brute force to me. This could result in very large data to be downloaded and stored on the Pi. Most of the libraries are probably never going to be used by the user. -
The idea of a lookup table sounds very intriguing. I am mostly wondering how and where the script would be run, what language would be best and where the result is going to be stored. I would also like to make sure the information is returned to the community. Creating this might also be useful for the Processing IDE which could then offer auto-install of libraries as well.
There are a few Python scripts in this repo which seem to be touched manually regularly to update the data: https://github.com/processing/processing-docs/tree/master/contrib_generate
Do you think writing another Python script for the lookup table and adding it there would be a good idea? In my mind, it would be run manually by whoever is updating the lists there.
If you’ve got the time and like to help, feel free to work on such a lookup table. Otherwise, I might give it a shot at some stage.
Thanks.