I don't think the rules have changed at all if I understand things correctly. Apple have just made it more difficult for people to abide by their own guidelines. They say Application Support is the place to put certain types of user files (and I assume that applies to both the user and system locations of that folder), then stop you from following their guidelines without jumping through hoops.
>From the description, I'd say that SQL database files would be a good candidate to put in Application Support? If so and I have a database I want to be available to all users of a specific Mac, it seems like the system Application Support folder would be the place to put it. As an admin user, I would expect to be able to do that with the usual prompt for Admin user password and not have to issue Unix commands from Terminal. It's not the end of the world, just another installation gotcha that has to be dealt with. Pete On Fri, Jul 22, 2011 at 6:55 AM, Richard Gaskin <ambassa...@fourthworld.com>wrote: > > > The rules haven't changed all that much; it's more like a prudent closure > of a security exposure. > > Allowing all processes to write to the system's Library is dangerous. > Problem solved in Lion. > > So what do we do? > > Nothing much different from how it's been for the last decade: > > Applications: most of an app's files go here, including the executable > and other components like stack files and externals, all > the essentials you app needs to run > > Preferences: user-specific settings for the app > > Application Support: Apple says, "These are the files that your > application creates and manages on behalf of the user > and can include files that contain user data." > > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
