> > Deken as it is right now, you
> > pretty much have to know the name of the library you want to install,
> > and what it does/what it contains. As a new user, I'd find that pretty
> > daunting.
>
> very good point!
>
> > Thus, I'd propose: a list of keywords for the library (including object
> On 2016-10-31 13:11, Derek Kwan wrote:
> > Thus, I'd propose: a list of keywords for the library (including object
> > class names), version number, category (if applicable), author, and a
> > short description.
>
> oh, you mean something like the "-objects.txt" file that you can upload
>
On 2016-10-31 13:11, Derek Kwan wrote:
> Thus, I'd propose: a list of keywords for the library (including object
> class names), version number, category (if applicable), author, and a
> short description.
oh, you mean something like the "-objects.txt" file that you can upload
alongside your
he need of running Pd)?
> Gesendet: Montag, 31. Oktober 2016 um 13:11 Uhr
> Von: "Derek Kwan" <derek.x.k...@gmail.com>
> An: "Fred Jan Kraan" <fjkr...@xs4all.nl>
> Cc: pd-list@lists.iem.at
> Betreff: Re: [PD] Deken library management. Was: [pdconv16_r] Topics
> It would help the discussion if there was an inventory of actual problems
> the metadata would solve. There was a discussion about this on the Github
> deken-list, which (probably) went nowhere because of this.
This metadata would potentially solve issues with updates (I'll discuss
this later)
