Seb Shader via Pd-list wrote:
> Hello again list,
> 
> 
>       What do y'all think of the idea of releasing Pd-extended both as a 
> "core" pd with no libraries added except maybe the libdir and hex loaders and 
> as a version with multiple libraries (2 release stages)? Perhaps it's been 
> discussed. the thing I enjoy about Extended is the features it adds to 
> pd-vanilla, and this way people can just keep the same libraries installed in 
> the same places and switch between vanilla and extended easier. In my 
> experience I never need/want to use most of the arbitrary libraries included 
> and/or loaded on startup and could easily download and install the ones I do 
> want. I also see the appeal/logic of using a standardized set of libs though.
> 
> 
> seems like a reasonable way to develop it too... everyone focusing on the 
> core and then working on their own libs for a bundled release.

That is definitely the goal of Pd-extended, I couldn't have said it better
myself. :-)  It is purely a matter of someone doing the work.  With two little
kids and full time programming work, I have little spare cycles for
programming these days.  But I'll happily help anyone who wants to take on
part of all of making this happen.


> Also about import/saving libraries to load on startup: wouldn't it make more 
> sense if either the list were editable or there were no list? Strange that 
> users get this arbitrary list to load on startup, (not even all the libs 
> included in PdX) without being able to edit it, a set of libs that they never 
> have to [import], but then they're expected to [import] everything else 
> unless they manually edit the preferences file (quite confusing for most 
> users)?
> 

The libraries that are loaded by default are an oooold legacy of the beginning
of Pd-extended.  It should be removed, but it needs to be done in a way that
is transparent when people update.  Or maybe it makes sense now to just start
fresh.  When I get back to it, I won't be working that arrangement of crufty
old libraries loaded by default.  Instead the way forward is to make a new
standard library that does things consistently and correctly across the whole
library, while only maintaining backward compatibility when it doesn't get in
the way of the primary goal.


> Btw I also have a bit of time and know a little bit of c and tcl, i'd be glad 
> to pitch in where i can when there is a concrete plan (list of to-do's) of 
> how to move forward with Pd-extended.

Excellent!  Here is the page that I maintained for release goals:

http://puredata.info/dev/NextRelease

.hc

_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Reply via email to