NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
config dir (Score:1)
Well, I, personally would love to see a "my_config" that is designed for users, which "my_data" is not.
User-editable config files on Windows shouldn't, in my opinion, be buried in "c:\Documents and Settings\username\Local Settings\Application Data\.foo". I'd rather see it as a hidden .foo directory in "my_documents", which is as close to a "home" directory as Windows gets for all practical purposes for 99% of users.
For me, "my_data" is fine if the application manages the config info itself and for ap
Re:config dir (Score:1)
I really don't think hidden or "dot" directories are the way to go on Windows. There simple is no concept of hidden files that you should have to touch.
Hidden files should NEVER be touched by people on Win32.
Also, File::HomeDir tries very VERY hard to NOT invent new standards for things, and only use existing blessed ways of doing things.
So personally, if you want to have a user-editable config file, I guess you'd have to put it under my_documents... although on Mac I'm not sure if that's the appropriate place.
A user-editable configuration file certainly could be argued to qualify as a "document".
Reply to This
Parent