Re: new hint for EWMH

[Tapani Pälli <tapani palli nokia com>]

ext Lubos Lunak wrote:
> On Monday 13 of August 2007, Tapani Pälli wrote:
>   
>> ext Lubos Lunak wrote:
>>     
>>> On Friday 03 of August 2007, Tapani Pälli wrote:
>>>       
>>>> New Window type is fine for WM but a list of rectangles is much better
>>>> toolkit-wise. Without this hint toolkit would need to go through whole
>>>> window tree and pick input-method windows and then make collision
>>>> detection logic. This is much heavier that having coordinates from the
>>>> start.
>>>>         
>>>  I see, I guess that makes sense. However that's only some kind of
>>> optimization, I think a window type is still needed to find out which
>>> windows create the regions. That's from somebody who has no clue about
>>> input methods though - from your suggested description I wouldn't have
>>> any idea how to actually implement the support.
>>>       
>> Yep this is 'minor' optimization and makes toolkit code more clean, it's
>> a bit 'ugly' to have these 'go through all windows' loops there. WM
>> naturally knows the IM windows (hint needed for this aswell ... Maemo
>> uses '_NET_WM_WINDOW_TYPE_INPUT' for this)
>>     
>
>  Please don't use such name for private properties, use a private prefix.
>
>   
>> and updates hint whenever 
>> such windows is (un)mapped, so implementation is quite trivial.
>>     
>
>  Could you please post a complete text you'd like to see included in the spec?
>   

OK, 2 new things specified here. a new window type + a new root window
property

---------- 8< -------------------------------------------------------

Section : Application Window Properties

...

_NET_WM_WINDOW_TYPE_INPUT, Atom

_NET_WM_WINDOW_TYPE_INPUT indicates that the window includes an input-method such as a virtual keyboard or area used by hand-writing recognition software. Window manager can use this information to position input-methods in it's own fashion and avoid overlaps with regular application windows.


---------- 8< -------------------------------------------------------

Section : Root Window Properties (and Related Messages)

...

_NET_INPUT_AREAS

_NET_INPUT_AREAS CARDINAL[]/32

This array contains a list of input-method areas. Toolkit and applications can use this information to place their pop-up (such as entry-completion or search pop-up) windows so that they won't overlap input-method areas. Property is set and updated by the Window Manager.


// Tapani