[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    Re: kdebase/kpager
From:       Antonio Larrosa =?iso-8859-1?q?Jim=E9nez?= <larrosa () kde ! org>
Date:       2002-03-13 2:03:05
[Download RAW message or body]

El Miércoles 13 Marzo 2002 01:05, Waldo Bastian escribió:
> On Tuesday 12 March 2002 03:22 pm, Antonio Larrosa Jiménez wrote:
> > And anyway, what are the reasons for this change ? Can you give me an
> > argument which surpasses the "it's been that way since the dawn of
> > time and people are already used to that" ?
>
> I think this new order is much more intuitive. I have been using this
> old order since the dawn of time (KDE 1.0) and I am still not used to it
> >:-)
>

Not sure of that. IMHO, a first vertical, then horizontal mode makes more 
sense because when you run through Ctrl-F1, F2, F3, F4, etc. You run 
through desktops which are one next to the other (just below, or just next 
to the current one). In this "intuitive mode", you can run through 
desktops 1, 2, 3 and 4 easily, but then you have to "jump" to the opposite 
side of the pager in the next row to find the 5th desktop. Anyway, I don't 
have a strong opinion here. I think anyone can get used to any of these 
both orders of desktops quite fast (ok, except you, but I doubt you were 
serious :) ), so I think mainly on people who are already used to the 
current way and will have to change their habits.

In any case, I'll revert it as it will break documentation, screenshots, 
kwin (as you said), and some other things maybe. Let's discuss after 3.0 
if it should be commited.

> That's of course no reason not to send a patch to kde-core-devel first.
>

He replied to me in private, it seems he sent a mail to kde-core-devel a 
month ago and some people agreed it was more intuitive. The problem is 
that it may have been committed then, but I think now it is too late.

Greetings,

--
Antonio Larrosa Jimenez
KDE Core developer  - larrosa@kde.org
http://perso.wanadoo.es/antlarr
KDE - The development framework of the future, today.
[prev in list] [next in list] [prev in thread] [next in thread]