On Jun 11, 2008, at 14:34, Christiaan Hofman wrote: >> Creating the empty folder just seems helpful for users, especially >> since the location is hardcoded and searched regardless of what's >> installed. >> >> I don't think anyone can make much of a case for that. Nearly every >> application does it, including Apple's. > > Actually, Apple makes a case in the docs (though I don't remember > exactly where). And we've run into problems due to it several times. > E.g. stuff we put there won't be updated, which is especially annoying > for users who don't care about messing with the app support files.
I don't recall ever seeing documentation saying not to create empty folders. In fact the most relevant documentation states, "How you organize the resources in this custom subdirectory [of Library/ Application Support] is entirely up to you." http://developer.apple.com/documentation/MacOSX/Conceptual/BPFileSystem/Articles/WhereToPutFiles.html In the "Don’t Pollute User Space" section, there definitely are warnings about putting things anywhere else but ~/Library. Maybe that's what you're remembering? As a script author, I would definitely like having a Scripts folder created by default. Since it would be empty, I don't think there's any problem with having to update it. The chances of renaming the "Scripts" folder in the near/mid-term future seem almost vanishingly small. If other things need to be updated in that directory, I think there should be some UI that comes up along with the release notes that says which files changed and allows the user to select the files they want to update, or at least tells them how to do it manually. -Colin ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Bibdesk-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
