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