From a usability experience the mechanism is like one would expect from a programming environment where one has to add includes to provide library functionality on top of installing them.
to stay with this analogy: in programming environments we pretty much never include all available libraries but only those we need. there might even be conflicting libraries which we don't want to load at the same time.
maybe loading everything works in "batteries inlcuded" approaches like Pd extended and Purr Data, but in Pd vanilla the user must/can decide whether they want to enable libs selectively via [declare] *or* always load them by adding the path to the Pd search paths and/or loading the lib on startup. it's both a burden and a blessing.
but wouldn't that mean that all the Gem examples should have a [declare -lib Gem] in them?
probably. multi-binary libraries don't have this problem because objects will load automatically, but in the case of single-binary libraries this might be a good idea. I don't see any disadvantage but I better leave this to IOhannes :-)
Christof
Gesendet: Sonntag, 27. Januar 2019 um 15:54 Uhr Von: "Max" abonnements@revolwear.com An: pd-list@lists.iem.at Betreff: Re: [PD] Installing GEM on mac?
On 26.01.19 21:25, IOhannes m zmölnig wrote:
On 1/26/19 7:51 PM, Max wrote:
This seems to have put some stuff into the Pd app bundle. However, when I try to open an example, most objects don't seem to be found, eg 'gemwin… could not create'.
seems like you didn't load Gem.
Deken (the external manager you have used through 'Find externals') should have asked you if you want to add Gem to the search paths. Did you say no to that?
hopefully. you shouldn't allow deken to automatically add search-paths. the entire functionality was an ugly hack for Pd<0.49.
Fair enough, but wouldn't that mean that all the Gem examples should have a [declare -lib Gem] in them?
From a usability experience the mechanism is like one would expect from a programming environment where one has to add includes to provide library functionality on top of installing them. Users coming from Apps like DAWs might think of externals more like plugins and might be confused by the extra step to be able to use them, I think that was the rationale of extended and Purr-Data to load all of them no matter if they are used or not. It's a different paradigm, it just needs to be clearly communicated to the user.
just my 0.2 ct..
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list