[Trac #1166] UI to kill not responsive activities

[Zarro Boogs per Child]

#1166: UI to kill not responsive activities
--------------------+-------------------------------------------------------
 Reporter:  marco   |        Owner:  Eben    
     Type:  defect  |       Status:  assigned
 Priority:  normal  |    Milestone:  BTest-3 
Component:  sugar   |   Resolution:          
 Keywords:          |  
--------------------+-------------------------------------------------------
Changes (by Eben):

  * status:  new => assigned

Comment:

 I had some discussions with Marco about this issue months ago, since it
 was my concern that we would in fact need such an ability.  I think that
 modifying the close button is a good way to do it.  However, it might not
 even be necessary to require the close button to be clicked twice.  The
 system should be able to determine when an activity is not responding.  If
 an activity is in this state when the close button is pressed, we could
 just send a KILL instead of a TERM and eliminate the need for the user to
 understand the difference.

 I suppose the only reason this isn't done in general is because the KILL
 signal will prevent the activity from running any necessary finalization
 scripts (such as saving to journal on quit, in our case, and perhaps other
 cleanup).  That unpredictability could be a big reason not to go that
 route...

 My ideas are evolving as I type:  How about if the activity isn't
 responding, we change the icon to indicate that closing it now will have a
 different effect; Or we could visually provide options for 'quit' and for
 'force quit' at the same time when that is the case, so they can choose
 the one they want on the first click.

 Thoughts?

-- 
Ticket URL: <http://dev.laptop.org/ticket/1166#comment:3>
One Laptop Per Child <http://laptop.org/>