Vincent van Ravesteijn - TNW wrote:
I think that either we build something based on likes/dislikes,
or something based on HIGs. In the later case, I am happy to be
involved, in the earlier case I will not be involved very much
(but just as happy).
You're right, but:
What follow are all very valid questions (and the first two remain
unanswered).
- In the thread it was also mentioned that we would like to change the
least as possible.
We cannot fulfill everything, somewhere we have to cut. If this is HIG
compliance, legacy, or something else, is not on me to decide.
- What happens if two HIGs clash ? Which one to choose ?
The major one we decide on. So far Edwin started with Apple's (which I
am naturally not opposed to), but I kept an eye on the windows HIG.
For example, a Tools menu would be something it looks like people want
(which is more Win than Apple, but still conforms with Apple's).
Whereas Document is something that does not much conform to either one
(but feel free to convince me from the opposite), and also not Gnome [1]
and KDE [2].
- The application menu section in the Apple HIG is basically empty.
As in 1.5, we should have that Application menu only on the Mac (where
it is auto-generated by the OS).
It contains typically only Preferences, About, and Quit, and Check for
Updates, and is populated with more entries by the OS.
For LyX I do not see much question:
Certainly About, Prefs, Reconfigure, and Quit, and, if we don't have a
Tools menu, probably TeX Information.
How
do we decide on what is application-specific enough to be in such a menu
?
Does above answer that?
On other platforms, Quit belongs into (KDE, Gnome and Windows HIG) File,
and Preferences (plus reconfigure) in (Gnome and Windows HIG) Edit.
I'm really interested what your vision is on these things ?
I interpret this question mark now as typo. :)
Well I can guess the second, so don't answer: "stick to one HIG",
because that's guaranteed to be a problem.
ooops ... too late. :)
Ok, ok, the issue does not have to be as black-and-white as I paint it.
But I would still try to stay away from making our own HIG.
I can send you a link if you want to look at it. :-)
Not necessary, you already send it, and I looked at it,
I know. :)
Not sure how we proceed from here.
/Konrad
[1] <http://library.gnome.org/devel/hig-book/stable/menus-standard.html.en>
[2]
<http://wiki.openusability.org/guidelines/index.php/Guidelines:Menus>
