I also agree; user-friendliness and understandability are crucial.

Art Hunkins

----- Original Message ----- 
From: "matt ingalls" 
To: "Developer discussions" 
Sent: Monday, June 12, 2006 1:12 PM
Subject: Re: [Cs-dev] [Csnd] Sample storage in Csound5


> i agree with Istvan on this.
> 
> i would rather have just have "search paths" (SSDIR, i guess) that users
> could add paths at will and all input files are looked.  i think the  
> chance
> that a user would have different input files with the same name in
> SADIR and SSDIR or something and cause conflicts is pretty slim.
> 
> i do agree that the whole scheme is confusing and/or antiquated.
> In MacCsound, i actually only let the user set one directory
> [ defaults to the directory the .csd file is in ] and set all  
> environment
> paths to that one directory ] - i just call it 'default directory'
> and don't even let the users think about SFDIR/SSDIR/etc..
> 
> i even think SFDIR is pretty worthless, given that modern  
> applications use
> "save as" dialogs and such, but i guess for people running from
> a commandline it could be useful..
> 
> -m
> 
> On Jun 12, 2006, at 6:02 AM, Dr. Richard Boulanger wrote:
> 
> > Do the other developers feel this way?
> >
> > John?
> >
> > It would add clarity - and it is another filetype that we are
> > including more and more often.
> >
> > Also,
> >
> > I am very interested in Csound working like most commercial software
> > which will search for
> > files in directories and subdirectories (by default)
> >
> > -dr.B.
> >
> > On Jun 12, 2006, at 5:22 AM, Istvan Varga wrote:
> >
> >> I do not really like the idea of adding even more environment
> >> variables
> >> when there are already too many, and the existing ones are sufficient
> >> in practice.
> >>
> >> On Monday 12 June 2006 12:16, Dr. Richard Boulanger wrote:
> >>
> >>> I also think that we need to add at explicit path to find our
> >>> MIDIfiles as well.
> >>>
> >>> We need to be able to specify a MFDIR (with subFolder support)
> >>>
> >>> Cleary we need to be able to organize our samples and or all
> >>> included/
> >>> searched folders
> >>> so that that can have subFolders that might be named
> >>> according to the instrument catagories - like strings, brass,
> >>> soundFX, Foley,  or filetypes (as you suggest - MIDIfiles,
> >>> AnalysisFiles, etc.)
> >>>
> >>> In fact, since you are suggesting that we might be able to list
> >>> all the
> >>> folders that are searched from within a single master directory,  
> >>> then
> >>> we might not want to confuse this with the SF or SS or SA dirs and
> >>> rather come up with a more generic CSDIR (for CsoundDirectory)-  
> >>> where
> >>> we search
> >>> it and all subfolders (that need not be specified explicitly) for  
> >>> any
> >>> and all included files - samples, .h, macros, UDOs, etc...
> >>
> >>
> >> _______________________________________________
> >> Csound-devel mailing list
> >> Csound-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
> >
> >
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
> 
> 
> 
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net