#7841 NORM 8.2.0 (: Replace CP auto-launch (software update) with non-modal alert

Zarro Boogs per Child bugtracker at laptop.org
Thu Aug 14 13:32:59 EDT 2008


#7841: Replace CP auto-launch (software update) with non-modal alert
----------------------+-----------------------------------------------------
   Reporter:  Eben    |       Owner:  cscott                           
       Type:  defect  |      Status:  new                              
   Priority:  normal  |   Milestone:  8.2.0 (was Update.2)             
  Component:  sugar   |     Version:  Development build as of this date
 Resolution:          |    Keywords:  8.2.0:+ r+                       
Next_action:  review  |    Verified:  0                                
  Blockedby:          |    Blocking:                                   
----------------------+-----------------------------------------------------

Comment(by cscott):

 I second Eben's software update icon suggestion, if it is easy.  Trac
 #7947 covers 'waiting for network', which is a 9.1 feature IMO.
 Discussion on how that might work should take place there, since this bug
 looks like it will be shortly able to be closed (yay).

 Code comments:
 {{{
 +        if self._list_view in self.get_children():
 +            self._list_view.add_alert(alert)
 +        else:
 +            self._favorites_view.add_alert(alert)
 }}}
 This seems unclean to me; it would be nicer to have HomeBox define
 'add_alert' and 'remove_alert' methods which would figure out which child
 to add/remove the alert to/from, instead of having to do it everyplace
 which wants to deal with alerts.  If I could wish for the moon, I'd say
 that the code which switches between views could also transparently deal
 with moving the alerts between the currently active views.

 {{{
 +            panel.set_section_view_auto_close()
 }}}
 I wonder if this is necessary/intuitive now.  I originally added the
 autoclose functionality for joyride users who might be expected to upgrade
 (say) every day.  The idea was that you'd launch into the newly upgraded
 build, the system would check for updates, and if you were already up to
 date it would disappear w/o forcing you to click to dismiss it.  The
 dialog now already requires you to manually click on it after each upgrade
 (slightly regrettably) -- perhaps it's now more confusing to click on
 'check now' and have the control panel check and disappear before giving
 you a chance to see that there were no updates.  I suggest we remove the
 autoclose when we land #7841.

 r+, with or without the changes I suggest, since I don't care about them
 strongly enough to keep the patch waiting.

-- 
Ticket URL: <http://dev.laptop.org/ticket/7841#comment:12>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system


More information about the Bugs mailing list