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

List:       kde-usability
Subject:    Re: konqueror's kpart system usability
From:       "Yanis Kekatos" <kekatos () gmail ! com>
Date:       2006-07-30 13:07:38
Message-ID: dea3c3190607300607x1847b3c1wb0a885d05d9df54c () mail ! gmail ! com
[Download RAW message or body]

On 7/28/06, Leo Savernik <l.savernik@aon.at> wrote:
> Am Freitag, 28. Juli 2006 16:24 schrieb Yanis Kekatos:
> > - The second issue is what menu elements are referred to konqueror
> > actions and what to the kpart object. Right now,it's really difficult
> > to tell what belongs to konqueror or to the kpart. [...]
>
> Same issue. Why should the user need to know? Whatever action he activates
> *certainly* has to affect the visible kpart or the container but this
> discrimination is of no interest to the user.
It's very important for the user to be able to predict what effect
will have the action he chooses.
All the menu items are designed to be operated in a specific context.
E.g. when the user views a pdf embedded in konqueror how can he know
if the 'Help->Report Bug' item is referred to kpdf or konqueror? To
make the problem more obvious, right now when I view a konqueror kpdf
embedded document there are two 'Tools' top level menu items. One for
kpdf and the other for konqueror (that has no child elements by the
way).

The problem is real, it's important and complicated and need to be solved.
_______________________________________________
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]