Re: [Usability] spatial desktop

2006-09-16 Thread Matthew Paul Thomas
On Sep 16, 2006, at 1:03 AM, brian muhumuza wrote:

 Does that mean I won't be able to have both applications open on the
 same file on the same screen?

 we would have both tools open/loaded onto the document but not using 
 both at the same time. When using the text editor, we have the text 
 editor's tool bar and menu bar, etc on the document, then with a key 
 stroke to switch tools, the editor's tool and menu bars are replaced 
 with the hex editor's tool and menu bars.

I agree that would be a useful ability in general (and Microsoft's OLE 
has allowed something similar since 1990). I also agree that if you try 
to open a document a second time, the application should automatically 
focus the already-open copy instead of doing anything weird (like 
gedit opened this instance of the file in non-editable way [sic]).

But if you explicitly choose to open the same file in multiple 
applications, I do not think there is any benefit in preventing you 
from doing so. Obvious example: for an HTML document, I don't want to 
have to constantly flick between source editing mode and browsing mode. 
I want the document to update automatically in one window as I type in 
the other. (Epiphany nearly does this already, updating whenever I 
save.)

  I am completing a topaz mock up for which i'll post a link soon.
 ...

Why mention topaz here? It makes your idea less credible. :-)

Cheers
-- 
Matthew Paul Thomas
http://mpt.net.nz/

___
Usability mailing list
Usability@gnome.org
http://mail.gnome.org/mailman/listinfo/usability


Re: [Usability] sticky keys and alt-tab

2006-09-16 Thread Matthew Paul Thomas
On Sep 14, 2006, at 4:37 AM, Joachim Noreiko wrote:

 --- Shaun McCance [EMAIL PROTECTED] wrote:
 On Wed, 2006-09-13 at 09:57 +0100, Joachim Noreiko
 wrote:
 Urg. Why do we even have this ugly little tab section? I understand 
 these options are provided by X, but why? What needs to happen to 
 kill them off or fold them into GNOME properly, or bring them 
 kicking and screaming into the rest of the GUI?

 Easier said than done.  There are people who use those options.  I'm 
 one of those people, because I like using a Compose key.  We can't 
 just ditch them. The list of options comes from the X server,

 And what comes from the X server is bizarre and limiting -- eg the 
 options for the compose key -- and sometimes archaic. I know it's 
 black magic that I have no hope of understanding, but will there ever 
 come a time when it's part of GNOME, and we therefore can update it?
 ...

First, design the ideal configuration interface, offering the most 
useful options you can think of, whether they exist or not.

Then, talk with the maintainer (Sergey Udaltsov, I believe) to find out 
which are possible with the current code and which aren't.

Then, go bribe some X hackers to implement the missing parts. :-)

-- 
Matthew Paul Thomas
http://mpt.net.nz/

___
Usability mailing list
Usability@gnome.org
http://mail.gnome.org/mailman/listinfo/usability


Re: [Usability] Quicky review of Seahorse encryption key manager

2006-09-16 Thread Matthew Paul Thomas
On Sep 14, 2006, at 1:52 PM, Nate Nielsen wrote:

 Alan Horkan wrote:
 ...
 The first dialog includes the following labels on the Tabs:
 My Personal Keys
 Keys I trust
 Keys I've Collected
 ...
 More appropriate labels would be:
 Personal Keys
 Trusted Keys
 Collected Keys.

 I've changed all but the first tab label. As Murray pointed out
 Personal Keys is ambiguous. I'm all out of ideas on this one, ie: How
 to remove the 'my' but still convey:

  * They're keys I've created. My very own keys. Only for me.
  * These aren't the keys of people I feel 'personal' about.

 The concepts behind encryption (and PGP in particular) are so confusing
 for people than being unambiguous is necessary in the labels.

I think this is the right approach. I'd go so far as to say that Keys 
You Trust is better than Trusted Keys, and Keys You've Collected 
better than Collected Keys, because they answer the vital question: 
By whom?

(And yes, I would say You've rather than You Have. Contractions 
aren't excessively informal, and allowing space for longer translations 
shouldn't be used as an excuse to make the English unnecessarily long.)

Whether to use you/your or me/my to refer to the person using 
the computer is tricky, but I try to follow the rule: you/your for 
headings and instructions (such as these tabs), me/my for controls 
that express the user's intent (such as checkboxes and buttons).

 ...
 For example one thing you'll notice once you install seahorse is that
 there are check boxes and descriptions that have to do with trust which
 look like:

  [x] I have verified that this key belongs to who it says it does.
  [x] I trust signatures on other keys made with this key.

 These are in a sort of contract or 'legal form' wording on purpose. 
 This helps convey the weight, effects, and idea behind the action 
 properly.
 ...

These are fine, except that checkbox labels shouldn't end with periods. 
:-) (You might also want to shorten verified that to checked, and 
who it says it does to the actual name used in the key.)

Cheers
-- 
Matthew Paul Thomas
http://mpt.net.nz/

___
Usability mailing list
Usability@gnome.org
http://mail.gnome.org/mailman/listinfo/usability


Re: [Usability] Mac-style menubar in GNOME

2006-09-16 Thread Daniel Borgmann
On 9/16/06, Joachim Noreiko [EMAIL PROTECTED] wrote:
 One thing I might add to mpt's notes is:
 * integration with the current panel menubar
 How will it look? How do we on the one hand link the
 two menus together seamlessly to avoid GUI ugliness,
 yet make it visually clear which part is constant and
 which part changes?
 It might be worth thinking about reducing the
 three-menu menubar, perhaps returning to the single
 icon foot menu as a default. (For example, anytime
 you're using Nautilus, you'd have two Places menus,
 which currently have different contents.)

Or two modes for the menu bar, one which looks like the current one
(and keeps application menus in their own windows) and one which
swallows the application menus and collapses the desktop menu into a
single foot menu. But the real challenge clearly is to implement the
menu swallowing in a portable way. Once that's available, we can still
think about presentation details...

Daniel
___
Usability mailing list
Usability@gnome.org
http://mail.gnome.org/mailman/listinfo/usability