[PD-dev] stripping down Pd-extended's default libs

Hans-Christoph Steiner hans at eds.org
Mon Feb 16 20:59:42 CET 2009

To be clear, the libraries will all still be included in the package,  
they just won't be loaded by default.  That means you'll have load  
them as part of the patch using either [declare] or [import], or using  
namespace prefixes like [cyclone/prepend].  This puts us further  
towards the goal of having all of the patch settings stored in the  
patch itself, making it more likely to work on more computers.

That said, you can still set your own preferences so that all of the  
libraries are loaded by default, and things continue to work how they  
do in previous version.   But that means that your patches will likely  
not run on other people's computers.

Part of this effort is also pulling out as many objectclasses as  
possible from the core distribution, and making that a standalone  
library like the rest, like a 'vanilla' or 'extra' library.  One  
immediate possibility created by doing that is the ability to have  
versions of this 'extra' library that are highly optimized for your CPU.


On Feb 16, 2009, at 12:39 PM, Loic Kessous wrote:

> well, as an ex-max only user , and a new Pd-extended user, I must say
> that I was quit happy to find already installed gem , pdp and an
> several other things.
> it doesn't take time to load all the libraries, and I don't understand
> what would be the reason to change this (but maybe there is one that I
> don't see).
> That's maybe true that it takes time to understand what to use because
> there's a lot of libraries, and some new structuring of the libraries
> may help, but not including gem (and particularly the pix_'object')
> and pdp by default will not be a good idea, I think . Also some more
> documentation may help too.
> Finally, even if it is messy to understand what to use at the
> beginning, I still prefer to try things already in the extended
> distribution by default than to load things before to try.
> one thing is that, if you compare to the source, some things are not
> working or not appearing on different platforms, but as I understand
> it is not related to the way to load libraries (by default or  
> manually).
> I would suggest to think about a new way to organize and document
> libraries instead of the stripping down option.
> hope that help,
> loic
>  ---
> On Feb 16, 2009, at 5:32 PM, ydegoyon at free.fr wrote:
>>>> Gem cyclone zexy creb cxc iemlib list-abs mapping markex maxlib
>>>> memento
>> mjlib motex oscx pddp pdogg pixeltango pmpd rradical sigpack  smlib
>> toxy
>> unauthorized vbap pan freeverb hcs jmmmp ext13 ggee  iem_anything
>> flib ekext
>> flatspace pdp pidip
>>>> I think it should be something like:
>>>> cyclone zexy creb iemlib ggee iem_anything flatspace
>> i don't understand the real goal of extended,
>> wasn't it to include as much libraries
>> as possible? ( and not to rewrite the gui ? )
>> second, i dunno why you made unauthorized
>> into a lib, when it was really allright to have
>> all objects separated in extra..
>> thus loaded when needed.
>> you never asked my opinion about this neither...
>> and also people writing on the list
>> saying you shouldn't use that external,
>> i have a brilliant workaround, etc...
>> i see that the pd community if ever it existed
>> is now getting a pyramidal structure
>> where some people take decisions for all,
>> cool..
>> xiaooo,
>> sevy
>> _______________________________________________
>> Pd-dev mailing list
>> Pd-dev at iem.at
>> http://lists.puredata.info/listinfo/pd-dev
> _______________________________________________
> Pd-dev mailing list
> Pd-dev at iem.at
> http://lists.puredata.info/listinfo/pd-dev


If you are not part of the solution, you are part of the problem.

More information about the Pd-dev mailing list