5,421
edits
Changes
From Gramps
m
no edit summary
For developers working on the [https://en.wikipedia.org/wiki/User_interface#User_interfaces_in_computing UI] (User interface), it is important to follow this guidelines to maintain consistency.
* Adhere to the [https://developer.gnome.org/hig/index.html GNOME Human Interface Guidelines] as much as possible. If you feel you have a need to deviate from these, make sure you can justify it, . Include the justification with the proposed design and get buy off in from the rest of the developers.
* Avoid using color to distinguish text. If you can, use a different mechanism. There are two issues:
# GTK allows the users to change their themes. You may be happy with your dark blue text that you've defined, but what about the person whose theme has a dark blue background? So far, the only widget that seems safe to use color is the [https://developer.gnome.org/gtk3/stable/GtkTreeView.html GtkTreeView]
# Many users (particularly males) are color blind. What you can distinguish, others may not be able to do sorecognize.* Gramps is designed to be usable, although (even if it may not look best, ) on 800x600 resolution displays. (This policy was last reviewed in [https://sourceforge.net/p/gramps/mailman/message/35551768/ 2016])
* Go for consistency. If a concept is used elsewhere in the program to represent what you want to do, use that mechanism. As an example, if someone's birth date does not exist, and you want to use a christening date instead, put the date in italics. This is what the Person View does. Be consistent with that. The more consistent we are, the less confused the user gets.
* Don't go button crazy. Buttons should be reserved for functions routinely used by all users (like Add, Delete, Edit). More obscure and less frequently used items should be in menus (such as a right context menu). Think of Firefox - The "Go to home page" function is used all the time, so it is a button. The "Send Link" function is not frequently used, so it appears in the menus.
