-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

With the Pd-extended build in its current setup, those abstractions would always be available with a [pixeltango/fx/] prefix. Or if we had the using/declare/import object, that would set the path to them for you, then you wouldn't need the prefix.

.hc

On Nov 28, 2005, at 10:32 AM, B. Bogart wrote:

Hey all,

As some of you know pixelTANGO dynamically generates an array of abstractions from a directory. These are a kind of plugin implimented in a patch (pixelTANGO).

The biggest issue is installing pixelTANGO on multiple operating systems. Since we need to read the "plugin" directory then we need to know where it is, which could be:

/applications/blah/contents/extra/fx /usr/lib/pd/extra/fx

or some horrible path in windows.

Any brilliant ideas on setting these messages in an abstraction from a hans's package build-system?

The only things I can think of are:

1. Try and use zexy to test the OS and assume we know where the fx/

should be installed. The user would only be able to install it where we assume...

2. instruct the user to edit the path manually. :(

I really dislike both these options..

Any brilliant ideas about setting this path based on where those fx/ are actually installed?

(and in case your wondering according to Miller there is indeed no way of telling where an abstraction is loaded from. (fx/ would be in the same directory as pt.layerfx.)

Thanks .b. _______________________________________________ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev

________________________________________________________________________ ____

"Terrorism is not an enemy. It cannot be defeated. It's a tactic. It's about as sensible to say we declare war on night attacks and expect we're going to win that war. We're not going to win the war on terrorism." - retired U.S. Army general, William Odom