[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    KDE/kdebase/workspace/plasma/design
From:       Chani Armitage <chanika () gmail ! com>
Date:       2010-05-27 4:41:24
Message-ID: 20100527044124.1B862AC8C5 () svn ! kde ! org
[Download RAW message or body]

SVN commit 1131049 by chani:

activities are involved in screen handling

 M  +3 -3      plasma-desktop-screen-handling  


--- trunk/KDE/kdebase/workspace/plasma/design/plasma-desktop-screen-handling \
#1131048:1131049 @@ -1,14 +1,14 @@
 How Screens Get Managed
 -----------------------
 * PlasmaApp handles the views
-* DesktopCorona handles the containments
+* DesktopCorona handles the containments with the help of Activity classes
 
 So:
-* When a screen is added: DesktopCorona adds a new containment if needed, since it \
handles Containments and the PlasmaApp responds to their creation +* When a screen is \
added: DesktopCorona tells the current Activity, which adds a new containment if \
                needed. PlasmaApp responds to their creation
 * When a screen is removed: PlasmaApp removes the associated view(s); we don't want \
                the Containment to go away, however, since the screen may return
 * When a screen changes geometry: the Views (DesktopView, PanelView) change their \
geometry and that of their containments if needed  
 Future work:
 * Migration of panels from non-existent screens to existing screens (perhaps asking \
                if the user would like them to migrate?)
-* 'hibernation' of containments from non-existent screens?
+* 'hibernation' of containments from non-existent screens (Activity will handle \
this)  


[prev in list] [next in list] [prev in thread] [next in thread]