On Jul 10, 2013, at 08:43 , Scott Ribe <[email protected]> wrote:
> The convention that we're talking about is that the apps' directories in
> Application Support should be named by bundle identifier, not by application
> name. The list that I provided was the result of ls Application\ Support, so
> as you can see the convention of using bundle identifiers is generally not
> followed.
The convention has always been "or", rather than "instead of". The choice is
still documented here:
https://developer.apple.com/library/mac/#documentation/FileManagement/Conceptual/FileSystemProgrammingGUide/FileSystemOverview/FileSystemOverview.html
> The Library Directory Stores App-Specific Files
>
> Application Support
>
> All content in this directory should be placed in a custom subdirectory whose
> name is that of your app’s bundle identifier or your company.
My vague recollection is that it used to say something like "or your app name"
too. A similar description here:
https://developer.apple.com/library/mac/#documentation/FileManagement/Conceptual/FileSystemProgrammingGUide/MacOSXDirectories/MacOSXDirectories.html
doesn't mention the alternatives at all:
> OS X Library Directory Details
>
> Application Support
>
> By convention, all of these items should be put in a subdirectory whose name
> matches the bundle identifier of the app.
so it's possible that we're seeing a change in the convention in progress.
My guess is that the app-name variant was previously preferred because
Application Support was always envisioned as a folder that users might have a
reason to visit in the Finder. But in sandboxed apps, Application Support
doesn't seem to have as big a role to play as before.
_______________________________________________
Cocoa-dev mailing list ([email protected])
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
