Hi, On 12/05/2012 12:32 PM, Pekka Paalanen wrote:
I have not even thought about sub-surfaces' implications to input handling or the shell yet. Sub-surfaces probably need to be able to receive input. The shell perhaps needs a bounding box of the set of surfaces to be able to pick an initial position for the window, etc.
indeed. On my "less intrusive" draft of subsurface, I've first started brainstorming the input focus behavior [0]. That's quite useful for the video player example that wants some kind of input control or a dialog stick window that might not. So we'll need a way to tell which subsurface gets the input focus. The way I did was enumerating methods for the subsurface, like "transient" for passing away the focus and "child" for a regular surface that wants it.. not a nice name, I agree.
That being said, I'm afraid that the input focus together with the configuration, positing and stacking, belongs more to the shells than the compositor itself, which should only control the attach -> damage -> commit. Just the concept of "windows" itself doesn't sound that good for a simple shell for instance, so at the moment it's being hard for me draw the picture why this is not an extension of the shell_surface. That's why I started drafting from this other direction.
Anyways, nice write-up and summary Pekka. Thanks for bringing this up! [0] http://cgit.freedesktop.org/~vignatti/wayland/commit/?h=xwm-client-OLD http://cgit.freedesktop.org/~vignatti/weston/commit/?h=xwm-client-OLD Tiago _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
