• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: More - Safari Download Security Alerts
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: More - Safari Download Security Alerts


  • Subject: Re: More - Safari Download Security Alerts
  • From: email@hidden
  • Date: Tue, 16 Dec 2008 14:14:36 +0100


On 16 Dec 2008, at 13:54, Dave wrote:

I don't install files into that folder, my application writes files to that location (by default, the user can change it) once installed. From the above document:
"It is important to remember that the user domain (/Users) is intended for files created by the user. With the exception of the ~/ Library directory, your application should never ***install*** files into the user’s home directory. In particular, you should never install files into a user’s Documents directory or into the /Users/ Shared directory. These directories should only be modified by the user."


They keyword here is ***install***.


OK, so if these files are really your apps 'documents' (ie the user- driven output of your app) then they should probably go into ~/ Documents/MyApp instead of ~/MyApp by default. If they are just settings/caches/other things then they belong somewhere in ~/Library. It is very uncommon for applications to write directly into ~/ on the Mac. (Looking on my own home folder, on a machine with multiple 3rd Party products in use for 2 years there are no (zero, zilch) non- standard folders/files that have been created by anything. By all means allow the user to define the default location.

Please note that the replies you got on this list may seem a bit snobby ("Don't put that there", "don't do that", "why do you want to do that" etc) if you are coming from another platform. Please understand that these are only intended as suggestions to help your app feel familiar to Mac users (i.e your potential customers). If you deviate too much from what they expect just to fit in with the way you do things on other platforms (which these customers have probably never used) then you will just confuse/frustrate them.

Matt Gough_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


  • Follow-Ups:
    • Re: More - Safari Download Security Alerts
      • From: Dave <email@hidden>
References: 
 >Safari Download Security Alerts (From: Dave <email@hidden>)
 >Re: Safari Download Security Alerts (From: Peter Blazejewicz <email@hidden>)
 >More - Safari Download Security Alerts (From: Dave <email@hidden>)
 >Re: More - Safari Download Security Alerts (From: Mike Abdullah <email@hidden>)
 >Re: More - Safari Download Security Alerts (From: Dave <email@hidden>)
 >Re: More - Safari Download Security Alerts (From: Bill Bumgarner <email@hidden>)
 >Re: More - Safari Download Security Alerts (From: Dave <email@hidden>)
 >Re: More - Safari Download Security Alerts (From: Bill Bumgarner <email@hidden>)
 >Re: More - Safari Download Security Alerts (From: Dave <email@hidden>)
 >Re: More - Safari Download Security Alerts (From: "Kyle Sluder" <email@hidden>)
 >Re: More - Safari Download Security Alerts (From: Dave <email@hidden>)

  • Prev by Date: Solved - sorta (Was: NSURLConnection & NSInputStream issue)
  • Next by Date: Re: More - Safari Download Security Alerts
  • Previous by thread: Re: More - Safari Download Security Alerts
  • Next by thread: Re: More - Safari Download Security Alerts
  • Index(es):
    • Date
    • Thread