Actually would a better idea be to leave the large libraries such as zexy as they are and work on a library that puts together all the other little externals from other people who are just beginning to develop objects for pd? Would this make more sense?

--- Joschi joschi@eds.org wrote: > This is a good idea, anything to ease the

installation of a good PD system for the end user is great. I do think that the challenge of this is that it is going to take a committed team to keep up with all the parrallel development that goes on in the pd community over a long period of time. There is no point in starting such a project unless you are willing to spend 5-10 hours a week for the next 2 years at least. There are many people working on externals in their own bubble, at their own schedule, and I don't think that is going to change, so what it is going to take is a committed group of people who want to invest serious time into bundling up all this exciting work into an easy to install form.

On Mon, 2002-04-15 at 05:45, mark wrote:

...

Hi,

I have just rebuilt my laptop and the biggest

problem

...

with PD is gathering together all of the externals

and

...

documentation.

It occurs to me that unified libraries would be

the answer -

...

probably hosted on sourceforge and gathering

together

...

as many externals as possible.

I guess there would have to be a number:

non~tilde (nt) cross platform tilde (t) cross platform

nt - linux only t - linux only

nt - win only t - win only

How does this strike people? Would all you

external writers

...

contribute?

cheers

mark

Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com

Hi all, has there ever been an attempt to introduce namespaces or a convention how to name externals that belong to a library? Do we/you want such a convention? I find it very useful to stick to the fs.* or vasp.* naming, especially when there are a lot of objects involved. Maybe there should be a restructuring (parallel naming) of the objects of the zexy and other libraries, so that one can find their home library more easily.

greetings, Thomas

1. using hyphenated class names (xeq-follow, instead of xeq_follow);

2. changing sys_load_lib() routine so that if passed a classname with

a hyphen, it uses only prefix name in its attempt to load a library -- which is just a few very simple lines of code, and would not break anything of what we have now.

Yes, the automatic loading by prefix is a good approach! I rather support the dot delimiter, though ;-) (maybe we can search for both...)

Thomas

... I like this idea, will have to think about how to make it work though...

cheers Miller

On Wed, Apr 17, 2002 at 11:46:05AM +0200, Thomas Grill wrote:

...

1. using hyphenated class names (xeq-follow, instead of xeq_follow);

2. changing sys_load_lib() routine so that if passed a classname with

a hyphen, it uses only prefix name in its attempt to load a library -- which is just a few very simple lines of code, and would not break anything of what we have now.

Yes, the automatic loading by prefix is a good approach! I rather support the dot delimiter, though ;-) (maybe we can search for both...)

Thomas

am 17.04.2002 18:53 Uhr schrieb günter geiger unter geiger@xdv.org:

What if a "/" would be used as a delimiter .... I already prosed that, but what was the disantvantage ?

In my case (with the upcoming vasp package) the basic objects are C++ externals but the rest is abstractions. Both parts should share the same namespace as they provide a common functionality. In this and comparable situations the / would (for abstractions) not be a good choice.

Thomas

My general policy on pure-data.org has been to link whatever file had the source archive in it. In many cases this is the version with the linux binaries, but no windows binaries. If one were to submit a download that was to a package with windows binaries in it, I would gladly include it, but as it is I have been the one to add 99% of the links to the download listing, I needed to somehow make my volunteer work load manageable. Of course, this makes Yves D. send me hate mail regularly, as if I am somehow poisoning the well, working around the clock to subvert him personally.

(Note that since my day job is as an Open System evangelist, including Windows software on a web site I run privately is a real danger to my career. But I do it anyway since I want to see Pd enjoyed by as many as possible.)

I would suggest that you use pure-data.org as a starting point for links to "every" Pd object (I'm sure some have been missed). Use the "homepage" link for a particular download to see if there is a windows binary-only release for the package. If there is, you might consider submitting that as a link on pure-data.org. You can put "(Windows Binaries)" or "(Windows Binaries Only)" after the name, perhaps. I will then approve them right away, for all to benefit from. Perhaps then all these voodoo-doll affects on myself and my family will stop...

On Tue, 2002-04-16 at 13:55, Rory Walsh wrote:

I have decided to create a library of ALL the "windows" externs I can find, it's basically for the students here in the lab so they don't have to waste time looking for and compiling extra externs. I think it's a good idea, especially for educational purposes so I'm going to give it a go. If any of the developers out there do not want me to include there objects please let me know. The names and websites of all the developers will appear in both their source code and in the help files for each of their objects. I'd also like to do this in Linux but my Linux skills are not too great! Sorry.

Rgards, ROry.