Re: [Audacity-devel] Per-user plugins directory on *nix
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Richard A. <ri...@au...> - 2008-02-12 08:23:24
|
Gale Andrews wrote: > | From Richard Ash <ri...@au...> > | Mon, 11 Feb 2008 20:05:51 +0000 > | Subject: [Audacity-devel] Per-user plugins directory on *nix >> Currently (and since 1.2.x) audacity uses ~/.audacity-files as a place >> for users to put plug-ins and the like for audacity to find and load. >> Seeing as we now have ~/.audacity-data/ with everything else >> audacity-related in it, does it seem a good or a bad idea to make the >> place for user plug-ins to go ~/.audacity-data/plug-ins/ ? To me it's >> the logical place (as ~/.audacity-data/ will be created by running >> audacity), but on the other hand most of the other files in there >> shouldn't be messed with by users. >> >> Opinions from anyone else? > > Apart from the possible objection you state, mightn't it be preferable > to keep the plug-in location consistent on all platforms? We couldn't > change it to Application Data on Windows (even if you were suggesting it) > because that directory is hidden by default on most Windows systems. There is no per-user plug-in directory on windows - the piece of code I was looking at is only compiled for wxGTK (it could be for OS X, but isn't). This could be viewed as an omission, but as you point out there is no sensible place to put such a directory in the windows file structure (logically it should be in the windows profile somewhere (ideally in the roaming part), but that means application data which most users can't find. The comparison with windows application data isn't really valid - both are hidden files on Linux since they start with dots, and really my point is that it's unusual for a Linux application to use more than one dot-file or folder in the user's home directory. I'm anticipating confusion from users who have to keep user chains in one dot-directory and plug-ins in another, as well as people who don't realise this and get confused when one or the other doesn't work. Richard |