#2328 BLOC Update.: Bitfrost requires that the 'File New' and 'Share' features be initiated through Sugar itself, not through the activities.

[Zarro Boogs per Child]

#2328: Bitfrost requires that the 'File New' and 'Share' features be initiated
through Sugar itself, not through the activities.
----------------------+-----------------------------------------------------
  Reporter:  mstone   |       Owner:  marco          
      Type:  defect   |      Status:  new            
  Priority:  blocker  |   Milestone:  Update.2       
 Component:  sugar    |     Version:                 
Resolution:           |    Keywords:  security, sugar
  Verified:  0        |    Blocking:                 
 Blockedby:           |  
----------------------+-----------------------------------------------------

Comment(by gnu):

 A UI change might make this easier.  I have never understood why the
 "close box" (X) is in the application's top line instead of in the top
 line of the Frame.

 The Frame is drawn by Sugar, not the activity.  Sugar already has a way to
 send a Quit to an activity.

 If you did the same for "Open" or "New" (put it in the Frame) then Sugar
 will automatically be the process to handle these user requests.

 Also, it makes sense.  The Frame is much more accessible than the multi-
 layered-upside-down-tab interface that's clogging the screen for
 applications.  You can always get the Frame with mouse motion into a
 corner; or the dedicated Frame key.  Navigating to a particular tab
 requires understanding the structure of the activity.

 (I do think it's more important to get hundreds or thousands of X
 applications running on the XO than the importance of more fully
 implementing the Bitfrost spec and thus breaking all X apps as well as
 breaking all existing XO activities.)

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