kdebase/konqueror

[Frans Englich]

(Replying two similar threads on kfm-devel and kde-usability)

On Thursday 01 April 2004 19:44, Datschge wrote:
> On Wednesday 31 March 2004 23:13, Frans Englich wrote:
> > s/Remove View/Close View/
>
> What is the reasoning behind this? A view (which can be removed) is
> not necessarily the same as a window (which can be closed), the
> former makes space for whatever other view is there, the latter
> disappears completely.

But that did not bring any new, I could do the same, playing a little game:

"A window(which can be removed) is not necessarily the same as a view(which 
can be closed), the former makes space for whatever other windows is there, 
the latter disappears completely."
(and it sounds just as sensible)

I committed for consistency. A view is just as a tab or window a widget/"a 
thing" which contains stuff(a window). Since it acts and is treated as a 
window it makes sense to use the same word.

(In either way, I'm not going to have an endless discussion over this. Just do 
a decision, kfm people)

>
> > Can't "Active" in "Close Active View" be removed? No?
>
> Don't make descriptions more blurry than they already are, 


> this has 
> nothing to do with usability.

Cool.

> The "Active" part can serve has an 
> important hint of what's actually considered a "View", and if not
> that it at least clarifies that you close the active view and not
> some random inactive one in some kind of hidden order. 

I just find it excessive. If not "Close View" close the active view what does 
it then close?(An arbitrary view? :) Since nothing else make sense I think an 
implicit agreement works. 
OTOH, main menus are not context based as RMBs are. That's why there's various 
"... Current Tab".
I suggest we do either 

A: s/View/Current/(consistency with tabs) and also add "Current" to the split 
actions.
or
B: Remove all occurrences of "View" and "Current"(view and tab actions).


> But who got 
> hurt by "Active" anyway, or what is your reasoning for that
> suggestion now?

Yes, such things occurs as a mystery to so many people. I got some usability 
docs coming up on that and I rather prefer to explain it once for all then.


Cheers,

		Frans