Re: Effects of "allow relocation" in Components tab
Re: Effects of "allow relocation" in Components tab
- Subject: Re: Effects of "allow relocation" in Components tab
- From: Nathan Duran <email@hidden>
- Date: Tue, 4 Mar 2008 14:10:48 -0800
On Mar 4, 2008, at 5:43 AM, Rick Hoge wrote:
the new PackageMaker looks really good on the surface
Funny, I always thought it looked like an AppleScript Studio front-end
for a CLI tool some intern whipped up over the weekend after glancing
over a technote on the subject.
Ignoring the fact that its functionality could not possibly have been
included on anyone's testing matrix given how badly broken it is, is
there anyone, anywhere who upon first encountering the "allow
relocation" checkbox actually understood what it meant? Maybe there
wasn't enough time to make it work, or to document it in any
meaningful way, but surely someone had a few seconds with which they
could have changed the text to read "locate existing" or "search
drive" or pretty much anything else. That table view is not exactly
starved for space; it would have fit, and if not, hey, Apple
practically invented the help balloon. Remember those crazy things?
Yeah, that was the same company.
I get the impression that several members of the developer's tools
team are generally resentful of the fact that they are expected to put
a filthy GUI on their precious Unix binaries so they purposely do as
lackluster a job as they possibly can without getting fired--kind of
like when you tell a little kid to wash the dishes before he plays
Nintendo. Either that or the department just doesn't get enough money
to hire anyone with UI experience since priorities have shifted away
from fostering enthusiasm amongst developers to growing the uberbrand
through walkman sales. But I have a hard time buying that explanation
since every product Jack Matthew seems to be in charge of sucks in so
many similar ways.
Somebody should really pay Stéphane for his services on this list.
It's about as useless as Radar without him, and even then it's still
pretty useless since Apple never seems to deign to acknowledge the
existence of these bugs let alone provide pertinent information on how
best to work around them or (gasp!) fix anything in an expeditious
manner. I'm sure that's an official DTS policy written in Eskimo blood
on a doublewide pair of khaki shorts somewhere, but that doesn't mean
it's doing anybody any favors. I know for a fact that there's some
really good people working those help lines whose tongues are simply
shackled by the post-NeXT bureaucracy, but those people really need to
start telling their bosses when they're full of prunes lest we have to
put up with this dreckware until they finally amass enough money to
buy a backdated house next to Rubenstein's and voluntarily quit
writing code.
Cull away.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden