I am currently working on Csound 5, and I plan to implement this
auto-import directory. Which would be better:

$CSOUND_HOME/auto_import

$CSOUND_AUTO_IMPORT

Original Message:
-----------------
From: Anthony Kozar anthony.kozar@utoledo.edu
Date: Mon, 05 Jan 2004 17:50:24 -0500
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3905] Re: REVIEW


On 12/17/03 6:34 PM, Matt J. Ingalls etched in stone:

> 
> 
> how about an auto-import directory?
> 
> this could be for both opcode libs and user-def opcodes.
> backwards compatibility opcodes could be implemented either way.

I think that this is a very good idea.  Most of the old opcodes being
converted into plugins could then be installed by default in the auto-import
directory to maintain compatibility.  This would not deny a user the freedom
though to move them elsewhere and import as needed.

Anthony Kozar
anthony.kozar@utoledo.edu


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

i would rather see the 2nd one.


On Mon, 5 Jan 2004, gogins@pipeline.com wrote:

> I am currently working on Csound 5, and I plan to implement this
> auto-import directory. Which would be better:
>
b> $CSOUND_HOME/auto_import
>
> $CSOUND_AUTO_IMPORT
>
> Original Message:
> -----------------
> From: Anthony Kozar anthony.kozar@utoledo.edu
> Date: Mon, 05 Jan 2004 17:50:24 -0500
> To: csound-dev@eartha.mills.edu
> Subject: [CSOUND-DEV:3905] Re: REVIEW
>
>
> On 12/17/03 6:34 PM, Matt J. Ingalls etched in stone:
>
> >
> >
> > how about an auto-import directory?
 >
> > this could be for both opcode libs and user-def opcodes.
> > backwards compatibility opcodes could be implemented either way.
>
> I think that this is a very good idea.  Most of the old opcodes being
> converted into plugins could then be installed by default in the auto-import
> directory to maintain compatibility.  This would not deny a user the freedom
> though to move them elsewhere and import as needed.
>
> Anthony Kozar
> anthony.kozar@utoledo.edu
>
>
> --------------------------------------------------------------------
> mail2web - Check your email from the web at
> http://mail2web.com/ .
>
"nd>

This was discussed somewhat before.  One key thing I think we should
remember is that it should be a collection of paths, not a single path.

On OS X, there is an established trend of having two places to put add-ons
and plug-ins.  One is the system wide /Library directory and the other is
each individual users ~/Library directory.  A similar practice may be
desirable on other Unix systems.

Another thing to keep in mind is that not all platforms have environment
variables.  MacOS doesn't for sure (do full-fledged Windows apps?).  The
SFDIR, SADIR, and SSDIR settings have always been implemented as a work
around in the MacOS and this will have to be also if you implement it as an
environment variable.

That would be OK.  Although a more portable solution might be a preferences
file located in the default place for each platform (:System
Folder:Preferences on the Mac, /etc or ~/.csoundrc on Unix).


On 1/5/04 7:27 PM, Matt J. Ingalls etched in stone:

> 
> i would rather see the 2nd one.
> 
> 
> On Mon, 5 Jan 2004, gogins@pipeline.com wrote:
> 
>> I am currently working on Csound 5, and I plan to implement this
>> auto-import directory. Which would be better:
>> 
>> $CSOUND_HOME/auto_import
>> 
>> $CSOUND_AUTO_IMPORT

>>>>> "Matt" == Matt J Ingalls  writes:

 Matt> i would rather see the 2nd one.

I agree

==John ff

 On Mon, 5 Jan 2004, gogins@pipeline.com wrote:

 >> I am currently working on Csound 5, and I plan to implement this
 >> auto-import directory. Which would be better:
 >> 
 b> $CSOUND_HOME/auto_import
 >> 
 >> $CSOUND_AUTO_IMPORT
 >>