#5208 NORM Update.: Sugar puts an extra circle in the donut for SimCity

[Zarro Boogs per Child]

#5208: Sugar puts an extra circle in the donut for SimCity
---------------------+------------------------------------------------------
  Reporter:  gnu     |       Owner:  marco                            
      Type:  defect  |      Status:  new                              
  Priority:  normal  |   Milestone:  Update.1                         
 Component:  sugar   |     Version:  Development build as of this date
Resolution:          |    Keywords:                                   
  Verified:  0       |  
---------------------+------------------------------------------------------

Comment(by marco):

 Replying to [comment:5 gnu]:
 > OK.  Yes.  So what?   Does an activity author need to understand the
 guts of the Sugar implementation?

 Not really. This is interface not implementation. Activity inherits from
 gtk.Window, so it should be expected it will create a window. If you
 create an additional window then the Sugar shell will rightly display two
 icons in the donut.

 > Or is there a well defined interface that sugar won't break or "evolve"?
 If so, where is it documented?  Someday (preferably before shipping
 600,000 copies of it) Sugar has to settle into a production component
 instead of a hacker playground -- or it will never attract a large herd of
 stable, working activities.

 The interface is not changed. Documentation is very sparse admittely, we
 will try to fix this as soon as we have resources for this work. Anyway,
 check this out, it should clarify a lot of things:

 http://wiki.laptop.org/go/Low-level_Activity_API#Security

 > If !SimCity broke because Sugar is evolving in a direction that makes it
 harder for ordinary X applications to run under it, then let's consider it
 the canary in the coal mine and quickly "ventilate" the sugar changes that
 caused it to keel over.

 Not really. Sugar was initially designed without any "support for ordinary
 X application" requirement, but it's evolving in a direction that makes it
 easier to port them.

 I guess Simcity *seemed* to work in the past because the Sugar donut was
 not displaying any icon for the actual Simcity window (bug). If that's the
 case by clicking on the activity window in home you would get an empty
 window, instead of the Simcity one.

 Since Simcity is not written in python, unless you can/want make it a gtk
 widget with python bindings, then you should just drop the python code and
 supports the bits of interface which are required by the Sugar shell.
 (command line options and X propertied which are described on the page I
 pointed you at)

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