Re: FSCopyObjectAsync: useless and crippled
Re: FSCopyObjectAsync: useless and crippled
- Subject: Re: FSCopyObjectAsync: useless and crippled
- From: "Mark Munz (DevList)" <email@hidden>
- Date: Mon, 16 May 2005 00:33:21 -0500
On May 15, 2005, at 11:39 PM, Andreas Mayer wrote:
Am 16. Mai 2005 um 05:49 Uhr schrieb Mark Munz (DevList):
BOA helper app
What's that?
BOA = Background Only Application, daemon if you like (although it's
more a UIElement Cocoa app than a true Unix daemon).
So, in this case, copying to the ~/Library/ folder is less
desirable and according a specific administrator customer, a
security risk
Then I suggest, the administrator moves it to the place he want's
it to be ... (?)
You asked why one would *need* to copy a file to the /Library/.
I could also use an installer. But that isn't the Macintosh way.
Looking at Apple's apps, which almost all of them require
installers, I guess it is. At least for apps that need to install
(additional) files in system folders like /Applications or /Library.
There seem be essentially two options:
Either your app gets installed in a user's folder; then it won't be
a problem to put additional files in user space, too. No added
security risk here, since malicious code could attack the app
itself, anyway.
Or the app is to be installed in /Applications, which requires
admin privileges and seems to make an installer the most logical
option.
Of course, your situation may be different enough to justify a
special approach; but IMHO that's really an exception then.
From a user's stand point, drag-n-drop installation is much
friendlier than forcing the use of an Installer. In fact, the Finder
will require authentication if you don't have privileges, just as I
would expect as a user. Apple's apps aren't generally good examples,
because they tend to break many of the HI Guidelines.
Installers are ugly from a user's stand point (I know I hate it when
the app I downloaded requires an installer before I can do anything).
It certainly seems overkill (to me) to require a full installer for
one file. I settled for putting it in the ~/Library (although it does
seem silly to have a copy of the app for each user).
Perhaps if I had said the need "installing" files to privileged
locations w/o requiring a full installer interface, it would have
become more obvious. And it can be done, but think that given Apple's
push (at least to developers) to provide First Time Run Installers
and Drag-n-Drop Installation whenever possible, providing a simple
High-Level API to "install" files to privileged locations would seem
to be a common need.
Mark Munz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden