[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:          |  
--------------------+-------------------------------------------------------
Comment (by Eben):

 Replying to [comment:4 AlbertCahalan]:
 > The initial "close" operation might cause the app to query the user.
 ("Are you sure you want to quit?") Even if such behavior might violate
 some UI guideline, it needs to be supported.

 Actually, this does go against our guideline and shouldn't be necessary
 that often.  Since objects are automatically saved to the Journal, the
 file "quit" button equates to "save and quit."  The only case when an "are
 you sure" style message might be needed is if some lengthy process (such
 as compression of video or rendering of a filter etc.) is in progress.

 This also means that we need to be very careful about force quitting when
 such a process is actually the cause of the activity's lack of response.
 To prevent that, we may just need to make an explicit button and educate
 kids about what it means.  It may never be safe to assume an activity is
 truly hung.

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