
Ted Gould wrote:
On Sat, 2006-06-03 at 12:20 +0100, Alan Horkan wrote:
that one of them may be current, and that the commands in this menu operate on that current effect. All of these assumptions are true for layers, objects, and paths, but none of them is true for effects.
However I pointed out Inkscape (and many other programs) have: File not Files, Edit not Edits, Layer not Layers, View not Views. These are verbs not nouns/objects which is what underlies your assumptions.
It may not be the most reputable source but here is what I found in Wikipedia: "According to traditional human interface guidelines, menu names were always supposed to be verbs, such as "file" "edit" and so on[citation needed]. This has been largely ignored in subsequent UI developments." http://en.wikipedia.org/wiki/Menu_%28computing%29
Uhm, I don't think they're verbs.
File - Actions that effect the "file" or the current data that you're working with. I would argue that Nautilus more adequately takes care of filing, which would be more organization of multiple files.
Layer - Actions that effect the current "layer", as in the noun.
But, in the end, it doesn't really matter. I have no problem adding the shortcut, but again, I think that really messes up translators. Fuzzy doesn't work there when many languages (especially Asian ones) have to do funny things with the shortcuts.
--Ted
IMHO, this has gone too far. I mean, 20+ messages for what? For an "s"? Come on, you would all have fixed some bugs in the time it took to write all these e-mails. :-)
Having witnessed many discussions in the few months I am monitoring this list, it seems that UI is a hot issue. I am planning on working on a UI customizer (like OpenOffice and most KDE apps have) to allow a user to change the UI as he sees fit (adding extra menus, changing toolbars, changing shortcut keys).
I hope such functionality will make such issues easier to resolve and will actually lighten the burden on the devel team, so that it doesn't make permanent UI decisions (and gets the blame).
However, I am pretty busy for the next weeks and I will start looking into it after that. I can't guarantee anything, but judging from a very quick code sweep it certainly looks feasible.
- Spyros Blanas