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

List:       kde-usability
Subject:    Re: New Tab
From:       "Aaron J. Seigo" <aseigo () kde ! org>
Date:       2004-02-01 19:06:30
Message-ID: 200402011206.33763.aseigo () kde ! org
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On January 31, 2004 12:44, James Richard Tyrer wrote:
> I noticed this and just fixed it on my system, but it has already been
> reported as a bug:
>
> http://bugs.kde.org/show_bug.cgi?id=55091

i just now tried to duplicate any of the problems in this bug and can't. a 
newly launched konqi instance with no URL preloaded allows me to create new 
tabs, split the window, etc. just as you noted in your replies. so.. this one 
is a non-issue, it seems.

> In general, I don't really think that some of the efforts to "improve"
> usability by removing and/or hiding stuff are going in the right direction.

cite specific examples, because your generality is wrong. there's a ballance 
to be struck between "too much" and "too little" and KDE has erred WAY on the 
side of "too much". other desktops err the other way. the goal is to get as 
close to Goldylocks country as possible ("mmm.. this desktop is juuuust 
right!")

as for the new tab button, it is re-addable by those who use it, rendered less 
important by the new tab widget (which may end up being always on in the next 
release ... ), and rarely if ever used by most people.

i know this because i've been collecting this information actively =)

- -- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
while (!horse()); cart();
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQFAHU451rcusafx20MRAkFKAJ9Nq2zB5VQTYinDbGySODvmleIQNQCfRpVT
t3VNpbcagZ5w0GriNFrLcss=
=0zZp
-----END PGP SIGNATURE-----
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]