On Fri, 2007-06-08 at 20:28 +0200, Georg Holzmann wrote:
Hallo!
Net-pd is for me the ONLY project where we could have a chance one day for having ALL externals, abstractions, extensions and even the hardware dependant externals in action, without having passing hours about configuring pd, understanding how the object works, etc ...
[...]
and found out that the net-pd project is the best candidate for having a functionnal bundle of all pd candies.
that's what pd extended tries to achieve ...
So, if all the stuff inside this neat project is also documented by comments, it would not only become more efficient than any manual, stage, physical meetings ..., for both learning how to use pd and having fun with it, but it would also decrease the amount of time for developping some add-ons, or optimizing the functionning.
that's what pd extended tries to achieve ...
I don't particulary have fun with opening, testing, closing the hundreds patches grabbed from cvs, pd-extended, pd-list, etc... if all those patches were documented under a single project that is already functionnal, a new user would come to the pd world without the fear of not having the possibility of understanding how the hell this stuff works.
again, pd extended ... However, of course not all patches are working out of the box with pd extended (I think not many will work), but if everyone builds his own distribution system (like netpd in your description) then it will never work ...
a more detailed answer to patco's suggestions might follow. just a few important notes from my side:
netpd's policy (actually my policy) is to use as less externals as possible. all my own netpd-patches depend only on netpd's dependencies (zexy and maxlib) and my plans on the long run are to kick even zexy out, because it was just used, because at that time there was no way in plain pd to do certain list operations. maxlib is basically only there because of [netserver] and [netclient]. in short: netpd officially doesn't support any externals (besides zexy and maxlib). of course, anyone can do with netpd what he/she might want to do and use some fancy externals, but it is very unlikely then that the patch will work on remote computers. the goal of netpd is sharing patches and abstractions, which happens automatically, whereas there is no way to share externals automatically. my opinion is that a 'good' netpd-patch in the sense of netpd, is one, that just works out of the box without having to install additional externals. externals are neither the goal nor the idea of netpd.
also shouldn't the pd-netpd packages considered as a separated pd distribution. they have been added to give some non-pd users a userfriendly start into netpd (since there are many netpd-users, that never do pd themselves). for pd users i'd recommend to install pd-vanilla and the necessary externals or pd-extended. for a pd-user it shouldn't be a big problem to install netpd. as you said, georg, collecting externals is the goal of pd-extended. it was never intended to compete against pd-extended.
my two rappen
roman
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de