[Trac #1287] Make the sugar shell more friendly to non-activity windows

[Zarro Boogs per Child]

#1287: Make the sugar shell more friendly to non-activity windows
--------------------+-------------------------------------------------------
 Reporter:  marco   |        Owner:  marco  
     Type:  defect  |       Status:  new    
 Priority:  high    |    Milestone:  BTest-3
Component:  sugar   |   Resolution:         
 Keywords:          |  
--------------------+-------------------------------------------------------
Comment (by jg):

 I think a good goal is to encourage the use of collaborative applications
 in the community as a whole; this will increase the number of applications
 available to us in the long term.

 And in fact, speaking to your specific example, it may already make sense:
 for example, believe it or not, GNU emacs can already clone windows across
 the network to other machines; 2 (or more) people can edit the same
 document simultaneously.  This has been possible for 20 years, though most
 people aren't aware of it.

 Furthermore, latent in most GTK+ applications, is the ability to migrate
 on the fly from one screen to the other (e.g. from your screen to a X
 server driving a projector).  We were doing this on iPAQ handhelds 3 years
 ago or so; what is more, the applications were able to reload their user
 interface on the fly to match the different screen characteristics.

 Similarly, GTK is capable of simultaneously using multiple X servers
 already; it is actually quite straight-forward to start building these
 shared applications today (though work on security and authentication
 should really be done to complete the story here).  Depending on
 circumstances, it may or may not make sense to use GTK for this sort of
 sharing; but sometimes it certainly does.

 I suspect that we should try to capture these techniques, and more
 importantly, the vision of collaborative applications being the norm
 rather than the exception.

 So we should be casting these sorts of things in terms of extensions to
 the EWMH, and not other ad-hoc mechanisms.

 We certainly need to grow the sugar team, and encourage
 contributions/patches in these areas from the community as well.

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