Re: FSCopyObjectAsync: useless and crippled
Re: FSCopyObjectAsync: useless and crippled
- Subject: Re: FSCopyObjectAsync: useless and crippled
- From: Ondra Cada <email@hidden>
- Date: Mon, 16 May 2005 18:34:07 +0200
On 16.5.2005, at 5:49, Mark Munz (DevList) wrote:
I could also use an installer. But that isn't the Macintosh way
Quite the contrary. It is THE RIGHT WAY, presumed you want a user to
be able to install anything into admin realm.
There may be a point in just copying--but *only if an admin does
that*. Again: no sweat, that's what fast user switching is for. Quick
and easy.
On 16.5.2005, at 7:33, Mark Munz (DevList) wrote:
BOA = Background Only Application, daemon if you like (although
it's more a UIElement Cocoa app than a true Unix daemon).
Such a thing does not belong to /Library nor ~/Library, but into the
application package Resources subfolder.
From a user's stand point, drag-n-drop installation is much
friendlier than forcing the use of an Installer.
Quite the contrary, at least from *this* user's standpoint :)
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,
Yup, and that's exactly the case of this Finder behaviour. What it
does is plain wrong. If you want to have admin privileges, well, *do
log in as admin* -- with fast user switching it's easy and quick. Or
launch an application as an admin -- that would be just as easy if
only Apple made Finder a normal application which it should have
been, and not something extra hidden in CoreLibrary or whatever :)
Installers are ugly from a user's stand point
Myself, being a user for years and years, I very strongly disagree. I
do *much* prefer packages to dragdrops, for packages automagically
keep the track of which and when and where was installed, not forcing
me to recall it using my poor memory, or to keep the track myself in
my own proprietary way. Actually, my only complaint is Apple crippled
the Installer application, which originally was able to (a) list (b)
remove whatever was installed, when the appropriate receipt was opened.
There are, of course, more subtle advantages -- like, receipts could
be used to easily clone the disk contents using DiskBuilder (another
case of very nice app which was alas trashed), to find where the
thing was installed for an easy and robust upgrade, and so forth. As
user who prefers to know what I did yesterday without having to
remember it myself :), I would *much* prefer if *anything* was
installed into system usign packages.
Perhaps if I had said the need "installing" files to privileged
locations w/o requiring a full installer interface
... in my personal opinion, there is *no* such a need. Or, more
precisely: if there is, it means the design of the thing (which wants
that) is flawed.
Just again: the privileged location is privileged *SO AS* the plain
user cannot mess with it. So he should not. If he is *also* an admin,
well, he *should login as admin* to mess with the privileged space,
and not to do that from the user account. It's that plain.
---
Ondra Čada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
_______________________________________________
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