WM: grouping applications (TAI)
Matthew Woehlke
mw_triad at users.sourceforge.net
Wed Apr 29 23:22:06 CEST 2009
Maciej Pilichowski wrote:
> On Wednesday 29 April 2009 21:45:47 Matthew Woehlke wrote:
>
> Matthew, please do not add key bindings to the actions, ok? Because I
> am bit lost, and besides, we can discuss key bindings later.
Yes. Um... I didn't, did I?
>> Maciej Pilichowski wrote:
>>> PS2. And I have difficulties with this:
>>>
>>> wm-switch-window-{previous,next}-sequence
>
> I mean what do we need sequence switch for. It is redundant imho.
I'm confused, where did "-sequence" come from?
The list I know about is:
wm-switch-window-{up,down,left,right}
wm-switch-window-{previous,next}
wm-switch-window-{previous,next}-historic
wm-switch-window-{previous,next}-spatial
wm-switch-window-desktop-{up,down,left,right}
wm-switch-window-desktop-{previous,next}
wm-switch-window-global-{previous,next}
>> "Smart" just means that it is either spatial or historic, depending
>> on the container type.
>
> This is redundant too.
I don't think it's redundant. The point is to be able to bind one set of
keys and have that set do the "most sensible" thing depending on the
container, rather than /always/ spatial or /always/ historic.
> For TAI user would have both historic and spatial (for all containers
> actually), so when I choose "smart" switch what the action will be?
> For TAI let's say. Why spatial would be more important than historic
> or vice-verse.
TAI - spatial
GAI - probably spatial?
FAI - historic
The reason is that (pardon) historically, "historic" is how users are
used to window switching in FAI working. And I think there is a reason
why FAI uses historic by default and not spatial. But for TAI, precedent
is for spatial, and again I think that makes sense.
> And mostly, what do we need that smartness for? If I would like to go
> left, I go left, I want to go back, I go back, I don't need smart
> level to make a choice instead of me.
I guess my answer is that I feel like I would only want to mess with one
set of bindings, that would be as described.
>> I'm not sure what
>> you mean "user can change the windows order"?
>
> I was referering to sequence switch. Usually it make sense for widgets
> (focus order) or for TDI, but for FAI, you can have
> A B C
>
> apps, and the sequence is like this, user moves the windows and now it
> is
> A C B
Well, sure, but you can do that to tiled also. Or tabbed for that
matter. I guess I don't see why it is surprising that you can change the
spatial ordering of FAI, but not surprising that you can do likewise to
GAI or TAI?
--
Matthew
Please do not quote my e-mail address unobfuscated in message bodies.
--
This is not a sig. I am too lazy to steal one, perhaps you could loan me
yours? -- Unknown
More information about the Kde-usability-devel
mailing list