[10:47] <maco> if you have 3 screens, (1 left, 1 right, 1 center) and you're looking at the one on the left, and it pops up on the one on the right...are you actually going to see it?
[14:12] <bratsche> davidbarth: https://wiki.ubuntu.com/NotificationDesignGuidelines#Morphing alert box
[14:17] <davidbarth> This is a meeting on morphing windows
[14:17] <davidbarth> (we're using IRC while the gobby service is being restored)
[14:17] <davidbarth> The agenda of the meeting is
[14:17] <davidbarth> 1. Introduce the concept of morphing windows
[14:18] <davidbarth> 2. Discuss the implementation
[14:18] <davidbarth> 3. Identify development steps and milestones for the karmic cycle
[14:18] <davidbarth> 1. Introduction
[14:18] <davidbarth> The concept originated from the notification development thread
[14:18] <davidbarth> Morphing windows provide an alternative way to interact with the user.
[14:19] <davidbarth> The concept is described in more details at https://wiki.ubuntu.com/NotificationDesignGuidelines#Morphing
[14:19] <davidbarth> The concept encompasses
[14:19] <davidbarth> morphing alert box
[14:23] <davidbarth> morphing windows
[14:24] <davidbarth> Feedback from the audience (Guadalinex) (correct me if i'm wrong)
[14:25] <davidbarth> using an ID card that is previously using notifications with actions (3 buttons)
[14:27] <davidbarth> we should refer to the Hermes project that makes heavy use of notifications (and actions)
[14:30] <davidbarth> The concept relies on raising a window, but in the background and unfocused by default (to prevent focus stealing if the window manager does not handle that already)
[14:37] <davidbarth> 2. Implementation discussion
[14:38] <davidbarth> The feature would be provided as a library
[14:40] <davidbarth> It is not a service that the notification system should provide, nor should it be a part of libnotify (unless it becomes usefull as part of the xdg discussion)
[14:40] <davidbarth> The implementation would provide a frame A and frame B
[14:40] <davidbarth> Opportunity to use the gtk timeframe
[14:40] <davidbarth> (that's gtk timeline really)
[14:41] <davidbarth> Note: should follow up at Guadec/Akademy
[14:41] <davidbarth> for the implementation details
[14:42] <davidbarth> Note: the morphing window feature can apply to a top-level window
[14:47] <davidbarth> 3 options (non-exclusive)
[14:47] <davidbarth> - can extend or shrink the (toplevel) window frame
[14:48] <davidbarth> - can (in-replace) replace a set of widgets with another one
[14:48] <davidbarth> - can re-use the existing frame
[14:49] <davidbarth> Adding to the design discussion
[14:50] <davidbarth> The concept should allow for grouping a set of staked dialog windows, and instead re-use the available window frames
[14:51] <davidbarth> Launchpad is using the same concept of morphing windows (searching for an example)
[14:57] <davidbarth> On the resize operation, we should support resizing in both directions (vertical / horizontal) 
[14:58] <davidbarth> We may provide a smooth transition between two frames, including with the ability to fade out / fade in widgets
[14:59] <davidbarth> (and/or frames)
[15:02] <davidbarth> The Ajax library that provides this morhoinbg window feature should be taken as an example 
[15:02] <davidbarth> ACTION: cody to implement a prototype that can swap to sets of widgets
[15:03] <davidbarth> ACTION: cody/dbarth to check the Ajax library features
[15:04] <davidbarth> Commitment for Karmic will be decided after the prototype phase (1 month, by the time we reach Guadec/Akademy)
[18:14] <bratsche> kenvandine: I think my latest csdeco revision should fix the issues you're having.
[18:18] <kenvandine> woot
[18:18] <kenvandine> email me the patch please
[18:18]  * kenvandine is heading out for a team dinner
[18:19] <kenvandine> bratsche: my ppa build is failing anyway, but might get back in time to fix it tonight :)
[18:43] <bratsche> kenvandine: Cool, no rush anyway.
[18:44] <bratsche> I haven't actually tested in xnest or anything.. but the problem was for applications that turn off decorations.
[18:44] <bratsche> And that's fixed.