Re: Prevent running in Rosetta
Re: Prevent running in Rosetta
- Subject: Re: Prevent running in Rosetta
- From: Kevin Boyce <email@hidden>
- Date: Tue, 17 Jan 2006 14:06:12 -0500
On Jan 17, 2006, at 10:00 AM, M. Uli Kusterer wrote:
On 28/12/05, Jonathan Hendry <email@hidden> wrote:
On Tuesday, December 27, 2005, at 07:05PM, Uli Kusterer <
email@hidden> wrote:
as a service to your users, I'd also suggest not preventing your
users from running an app in Rosetta. Rather, warn them and tell
them
there isn't any support for what they're doing and that certain
parts
won't work, and maybe replace any "file a bug report" dialogs with
warning messages that simply say something similar.
You can't really say that, not knowing anything about the app or
the customer base.
If it's an application for planning radiological treatments and
calculating radiation doses and beam angles, do you really
want customers putting it on a configuration that "kinda" works,
but might fail in unknown ways?
No, you certainly don't, no matter how convenient it might be for
them.
(I don't know what joar works on, but there was a company which
used OS X for precisely this kind of software.)
Well, I may be a usability nerd, but I'm also a firm believer in
letting the
user shoot themselves in the foot when they want to.
Um, in the example given above, it's not a matter of shooting oneself
in the foot, but of shooting an innocent patient in the [fill in the
blank], with high-energy photons.
Warning the user that
they're on thin ice but still allowing that they run the app if
they feel
the need is fair enough for me.
Not if we're talking about radiation treatment. See, e.g.
http://smi-web.stanford.edu/people/felciano/research/humanerror/
humanerrortalk.html#RTFToC18
-Kevin
_______________________________________________
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