[PD] (netpd)U(Pd-extended)

[patrice colet]

(assuming that this message didn't arrive to the list, sorry if you've
received this mail twice, I've also corrected the end of the message)

Hi eni,

Le samedi 09 juin 2007 à 11:26 +0200, Enrique Erne a écrit :
> hi patko

> if you miss an abstraction there is something wrong with your setup.

No, I seriously think that if I miss an abstraction, there is something
wrong with the documentation, or comments, and I am not talking about
net-pd. I'd rather rebuild my own set of abstractions than looking for
the missing patch if I have to surf internet, ask questions to pd-list
for getting answers. An undocumented patch is almost always a waste of
time for every pd users. I can tell this for myself too.


> i think i can say _every_ netpd-patch that uses abstractions has
> a subpatch [pd abslist] with a list of msgs containing all used 
> abstractions.
> 
> when one netloads a patch, _creator.pd will read the abslist and
tells 
> all
> the users that it is going to upload a patch with the specific 
> abstractions
> and version number.

Yes, that's a very cool functionning, it could save everyone a lot of
time, and it would be even better if _creator.pd was able to update
itself, and why not letting it update absolutely all the files (even the
ones in the bin directory)? It would certainly require a 'pd
repositories'.


> i was thinking about removing my name from the patches and make it
more
> welcome for changes (see kyle's movie about os)... so far we were
> cautious in changing others patches.
> usually we change the name ultrahardcoresynth-eni.pd and do changes
and 
> suggest it
> to the original author... but many authors are not active.. hmm
that's 
> an other topic.

Instead of uploading abstraction from a net-pd user's computer, it might
be better if the abstraction were uploaded from a net-pd repository.
 Any one that would like to add abstractions to net-pd would have to
submit them to an active authority of the net-pd project, then it would
avoid a lot of mistakes, and the autor would still be referenced but
rather in a net-pd database than into the patch, were more usefull
information could be displayed.  

> what information would you like to see in the patches ?

I simply would like to be able to understand without having to browse
all patches and subpatches hundreds of times for having a clue about how
the objects are functionning. For example if I want to put an FX-insert
into an net-pd instrument I've made, I take a look at how it has been
implemented in other intruments and in the mixer, and I give up after
two hours because it's a real mess, there is absolutely no explanations
anywhere.
Just seeing 'information' would be a good start, ;).

> - dependencies...

Well I hope you've seen that we are talking about two different things
through this discussion, net-pd and pd-extended, and net-pd allready
resolve this 'dependence' problem with [pd abslist].
Maybe [import] in pd-extended would fix missing externals, with at least
giving the name of the missing ones.

> what do you mean with "original abstractions" ?

Let's say: "an abstraction that isn't into the pd documentation"