#5872 NORM Future : Allow activity to disable sugar frame activation

[Zarro Boogs per Child]

#5872: Allow activity to disable sugar frame activation
----------------------+-----------------------------------------------------
  Reporter:  ghopper  |       Owner:  marco                                  
      Type:  defect   |      Status:  new                                    
  Priority:  normal   |   Milestone:  Future Release                         
 Component:  sugar    |     Version:                                         
Resolution:           |    Keywords:  frame hot corner popup activity toolbar
  Verified:  0        |    Blocking:                                         
 Blockedby:           |  
----------------------+-----------------------------------------------------

Comment(by Eben):

 Replying to [comment:11 ghopper]:
 > Replying to [comment:10 HoboPrimate]:
 > > Replying to [comment:9 Eben]:
 > > > Replying to [comment:8 BHunsaker]:
 > Activities should enter full-screen mode when you press the FRAME key,
 not ALT-ENTER.  (ALT-ENTER is an example of an obscure magic key sequence,
 of which we have too many.)

 This is wholly untrue.  The Frame key is very much needed to reveal the
 interface element itself.  I don't see any argument for removing this base
 shortcut, though one might argue that something like alt-frame would be
 more appropriate.  That I could see being reasonable, but not necessarily
 any more intuitive.

 > The frame menus should be controlled by the activity.  If there is a way
 for the activity to integrate or use the parts of the sugar frame that
 make sense, that would be great, but overlaying the sugar frame on top of
 every activity is not a good idea.

 This is the very opposite of the design goals for the Frame.  It is
 supposed to provide a collection of tools that are by definition relevant
 to all views.  The new Frame design will further elucidate out goals here,
 as a place to copy/paste to/from, as a way to switch the current activity,
 and as a way to get quick access to system status and notifications.

 > (Regarding subject change: I don't know how we got sidetracked to adding
 options to the control panel.  A delayed frame activation would not solve
 my daughter's original complaint.  Please use ticket:5629 to follow up on
 the control panel options)

 On the contrary, I think this would definitely help the situation.  Most
 of the cases you site include motion of the cursor in a path which
 ''temporarily'' exceeds the boundary of the screen in a given corner.  In
 these cases, such as a wide brush stroke, the cursor will come back into
 the canvas before the delay triggers the Frame, thus lessening the problem
 a considerable amount (proportional, perhaps, to the length of the delay).
 Moreover, I'm happy to make the extreme of this control setting completely
 disable corner activation.  I fundamentally disagree with the idea that
 any corner should be treated differently, as the Frames presence as a
 peripheral on all screen edges is quite important, and the ability to
 activate it in proximity to a particular edge is likewise.

 For the time being we could configure this setting from the command line
 if Marco has time to take advantage of the set value in the Frame code,
 which I know is somewhat complex.

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