more flexibility for handling startup paths/libs
We have two general ideas for adding some more ease to custom startup paths/libs:
Here's one from @aggraef
I think that all this actually raises a more interesting question, namely how do we cater to individual users needs for a "bottled" personalized setup, and make that as easy and painless as possible? I can relate to that, it affects me as well. We use Purr Data for teaching, and sometimes we just need a customized setup so that we can have the students up to speed with the things we want to do quickly. That's certainly something that we can think about.
Here's a very quick idea from @jwilkes
- Startup paths for libs that were default before Pd-extended got abandoned
- Startup paths for all libs
- Startup paths for no libs
The first option should be default since there is still an enormous number of patches in the wild that depend on those paths being loaded by default.
Edit: originally pasted the wrong thing.