Re: Huge Batch Reply: Lars

[Lars Torben Wilson <torben coastnet com>]

"Dan \"Effugas\" Kaminsky" writes:
 > Gnomeprint is created by the interface.  If the app freezes, the interface
 > should still function...meaning one could kill the app from here.

Yes. So why do we need another Exit in another menu?

 > This is something we REQUIRE.  GC1.  This is a key safety feature, it’s a
 > key interface issue...

Please stop inferring that I have said that this is something that is
not required. It is required, I think it should be required, it should
be GL1 or higher, and anybody who writes an app which modifies
information in any way without this should be drawn and quartered. :)

Seat belts are a safety feature. Are they optional equipment? Not in
any consumer vehicle I've seen, not should they be. For some reason,
the term 'safety feature' appears to mean 'optional' to you. It
doesn't mean that.

 > I never thought I’d see my girlfriend get so pissed about a UI thing.  I
 > mean, UI, my girlfriend PISSED?

OK. Can she explain why it pisses her off, other than the fact that
it's something different from what she's learned? If she can, great;
we'll learn something from her (using your girlfriend to mean 'all
people pissed off by this', of course :). I've got a feeling my wife'd 
be pretty ticked, too. However, I'd have a hard time getting her to
articulate any reason why beyond the fact that it's different from
what she's used before.

 > >I do think that it would be a mistake to have it in more than one
 > >menu, though.
 > 
 > What about Force Quit v. Exit?  Quick easy way to kill process very
 > logically.

If you can keep GTK responding after the app has frozen, sure. I'd
more likely do an xkill from a wm menu. Besides, if we get old Win95
users, they'll likely just hit Ctrl-Alt-Del for the process window.

 > >exit the app, and heaven help any app that doesn't offer to save
 > >unsaved work before it dies. ;)
 > 
 > GC1.

STOP THAT. :) We AGREE, already!


Torben