Before the discussion on deken installing libraries for you goes super far, we talked about this curing Chris’ initial deken development and, regarding, auto-magically downloading dependencies:
Pd developer time is currently limited (Chris & IOhannes were basically spitballing at that point), so the focus instead was put more on getting the basics working, especially in binary lib upload, search, & install.
Auto-magic dependency was put into the “nice to have, but possibly a lot of work to get right” pile as opposed to “must have" pile. If it turns out to be trivial, then by all means someone can propose some code and we can try it out (deken has it’s own GitHub repo after all).
There is no easy way around the pd-extended kitchen sink -> pd vanilla barebones + libs transition, [declare] is the preferred way forward in that regard. At least I thought that was agreed upon...
IMO the much bigger issue right now is that we don’t have full coverage of built external deken packages for all the main extended libraries for all platforms yet. If we (I am!) are worried about priority with limited resources, I feel this is much more important right now. We need a big push of people essentially updating these main libs to the pd-lib-builder makefile and then coordinating people on various platforms to build said libs and upload deken packages. The makefile can do that as a makefile target, so it’s relatively easy. After all, how can deken suggest a lib to install when there aren’t that many libs in deken to being with?
One of the great things about deken is that it helps decentralize the kitchen sink. Now, we need everyone to grab a utensil and start scrubbing :)
Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
On Jun 9, 2016, at 4:00 AM, pd-list-request@lists.iem.at wrote:
From: Max <abonnements@revolwear.com mailto:abonnements@revolwear.com> Subject: Re: [PD] deken install user experience Date: June 9, 2016 at 3:00:27 AM MDT To: Roman Haefeli <reduzent@gmail.com mailto:reduzent@gmail.com>, pd-list@lists.iem.at mailto:pd-list@lists.iem.at
On 2016년 06월 09일 17:33, Roman Haefeli wrote:
In my ideal world, I write a Pd project, make sure it properly declares what it needs and then people who want to run my project find a list in the documentation with the required externals (with no further explanation how to do that and where to install). After installing the externals from the list, my pd project runs on their box and is able to successfully load the libraries. We're not there yet, see above.
Or even better: the receipient opens the file, Pd realizes that it depends on not installed libraries, prompts "should Pd install the missing libraries x, y and z?" then she/he clicks yes or abort.
Sorry if I missed this, but what is the point of displaying> incompatible (wrong arch, wrong platform) Deken packages? What would be> harmed if they'd be hidden completely? I fail to see the advantage of> having the possibility of downloading a package of wrong arch/platform.
--like: preparing your patch for offline use on multiple archs, which you--currently don't have access to. Totally, I distribute my patches with all needed externals included, for all platforms, this way the user ONLY have to install pd and its ready to listen. He/she just open the patch and it works, no need to deken or -path or whatever, it just work. I think its Ok that other platforms zips are grayed out.
Mensaje telepatico asistido por maquinas.
Having deken proposing solutions for resolving missing patch > dependencies looks very interesting, it should save a lot of time to > users that want to collaborate on same patches from different machines.
One simple solution will be to have one zip containing all externals (updated monthly?) this will be the most simple and interesting for new users. This will bring back the benefits of “extended”. By benefits I mean that as a student you are exposed to the work of all externals devs, it`s there, you open the browser and open zexy, cyclone, ggee, etc. With Vanilla you don't even know that there is a library of externals called mpreach.
Mensaje telepatico asistido por maquinas.
Le 09/06/2016 à 20:16, Lucas Cordiviola a écrit :
One simple solution will be to have one zip containing all externals (updated monthly?) this will be the most simple and interesting for new users.
I don't know in this case how to avoid conflicts, sometimes I have to remove mrpeach from path for having other externals to work, don't ask me why because I don't know.
I'm not insisting, but problematic/conflicting externals once detected can be excluded from the “All” package. But it's just an idea.
Mensaje telepatico asistido por maquinas.
To: pd-list@lists.iem.at From: colet.patrice@free.fr Date: Thu, 9 Jun 2016 20:58:08 +0200 Subject: Re: [PD] deken install user experience
Le 09/06/2016 à 20:16, Lucas Cordiviola a écrit :
One simple solution will be to have one zip containing all externals (updated monthly?) this will be the most simple and interesting for new users.
I don't know in this case how to avoid conflicts, sometimes I have to remove mrpeach from path for having other externals to work, don't ask me why because I don't know.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
-
Dan Wilcox -
Lucas Cordiviola -
patrice colet