Changes

Jump to: navigation, search

GEPS 034: Improve usability

3,181 bytes added, 08:43, 31 August 2015
See also
{{man menu|This GEPS is about changes that would significantly improve the user friendliness of Gramps.}} It is '''not''' about the visual details of the user interface; it is '''not''' about whether the user interface conforms to some specific guidelines or style. It is '''not''' about minor changes to the user interface.
It is appreciated that improving usability is among the hardest things to do with software, especially with Open Source, and that in some (most? all?) cases it is a matter of opinion. However, It is important to have this GEPS as a place to collect feedback on problems and as well as possible solutions.
Some of the wording below has been taken from various messages on the Gramps mailing list. The purpose of this GEPS is to stimulate radical thinking, rather than to follow what has gone before.
= Problem The challenges = <blockquote>Making a user interface that novice users can understand is hard. Making a user interface that provides the power and flexibility that advanced users require is really hard. And making an interface that does both is ... nearly impossible.<br><br>Based on my experience with the Gramps team, I think a major overhaul effort would be difficult to execute. Major projects like that require sustained focus. Our developers are volunteers who have to find time to hack code between washing the dishes and changing the oil in the car. The most substantial changes I have seen over the life of Gramps have been slow and evolutionary - and were developed over the course of a series of staged releases.<br>- '''From: Brian Matherly - 2011-03-30 - [http://sourceforge.net/p/gramps/mailman/message/27280108/ Re: (Gramps-devel) Focus On User Interface, Usability]'''</blockquote><hr><blockquote>I just can't see how this can be tackled in the incremental way that Gramps mostly works. The 'little improvements over time' approach seems to have given us a powerful but unwieldy tool.<br>- '''From: Duncan Lithgow - 2011-03-30 [http://sourceforge.net/p/gramps/mailman/message/27280425/ Re: (Gramps-devel) Focus On User Interface, Usability]'''</blockquote> == The reviews and feedback ==
In the reviews of Gramps on Gensoft for [http://www.gensoftreviews.com/?p=1648 GenSoft Review for MS-Windows], [http://www.gensoftreviews.com/?p=1649 GenSoft review for Apple Mac] and the [http://www.gensoftreviews.com/?p=286 GenSoft review for Linux], some selected comments are:
;Program complexity
* Douglas T watts says: "Too Complex when it came to adding a spouse???".
* Hal Bates says: "found it very difficult to use and it is not intuitive...Biggest Con: Hard to use or figure out".
* Nov 21, 2012 - ''Robert K. Tompsett'' says: "Gramps has no documention worth using."
* Jul 8, 2014 - ''Not ready for prime time'' says: "The documentation doesn’t match version 4 in this respect so it’s no help." Biggest Con: not intuitive, sketchy documentation
* Aug 11, 2014 - ''VRM'' says: "The manual is inaccurate ...., or just plain wrong. The developers expect you to read the whole manual before attempting anything, yet they provide directions that you’ll not remember by the time you actually get to the software. Also, as for the manual, wall-of-text alert. The program icons? Some are '''mystery meat''', where you guess what they are (Why does that green tree split apart at the bottom?)" Biggest Con: ... I don’t want to read 50 pages of manual to find out if it does or not.
* Jun 17, 2014 - ''bh'' says: "The Manuel in not helpful. ... "
==Positive remarks==
Note that in some cases, the criticisms quoted are accompanied by positive remarks. The comments in some cases also mention specific interface issues. None of these are considered here.
* A comment:
<blockquote>Recently having sought to really use GRAMPS on a regular basis for practical genealogical research has repeatedly illuminated a lack of intuitive or smooth workflow within the user interface, particularly for the new user manually entering information.
In some future major revision of GRAMPS, for example for version 4.0, how about putting a major emphasis on the user interface and its usability? It seems to me that a new user should understand how to enter basic information smoothly and effectively and not feel like they're switching back and forth between a large number of views or performing many steps which could perhaps be combined and lessening redundant processes. It also seems that a new user should not have to load alternate views, gramplets or perform any significant customization. These areas appear to need some attention.<br>- '''From: Greg Lamberson - 2011-03-29 - [http://sourceforge.net/p/gramps/mailman/message/27278184/ (Gramps-devel) Focus On User Interface, Usability]'''</blockquote>
* Another comment:
# Repeat 4-6 for death event
# Click OK
Total: 14 clicks, or 7 clicks and 15 to 17 keystrokes, plus the data you are entering (including selection of place)<br>- '''From: Michael White - 2008-02-11 - [http://sourceforge.net/p/gramps/mailman/message/18563150/ (Gramps-users) My thoughts on usability/data entry]'''</blockquote>
* Another comment:
<blockquote>When I add a person in PAF, or Ancestry, I see one screen where I entername, gender, and main events. When I do the same in Gramps, I see halfa dozen screens, one for the person, one extra to add each event, andanother extra to add a location or to choose an existing one. That's alot of work, and when I want to enter birth, baptism, death, and burial,I need at least 9 screens in Gramps, where PAF still has only one. Andin Gramps, it's actually more, because many times I need an extra clickto see whether the location that I want to enter already exists in thedatabase. In those occasions, it is not half a dozen, but a full one,really!<br>- '''From: Enno Borgsteede - 2014-03-31 - [http://sourceforge.net/p/gramps/mailman/message/32167521/ Re: (Gramps-devel) Gramps 3.4.8 from GIT --> Sources]'''</blockquote>
== Examples ==
Suppose you want to add an attribute to an event for a user. The steps involved would be:
One aspect that seems particularly confusing for (new) users is the way relatives are added to a person.
The description in [https://www.gramps-project.org/wiki/index.php?title=[Start_with_Genealogy |Start with Genealogy]] describes how to add a person and their birthdate and place. This involves opening and closing a large number of different windows. This can be contrasted with a number of other genealogy programs where all this data is input on a single window. = The challenges = <blockquote>Making a user interface that novice users can understand is hard. Making a user interface that provides the power and flexibility that advanced users require is really hard. And making an interface that does both is ... nearly impossible. Based on my experience with the Gramps team, I think a major overhaul effort would be difficult to execute. Major projects like that require sustained focus. Our developers are volunteers who have to find time to hack code between washing the dishes and changing the oil in the car. The most substantial changes I have seen over the life of Gramps have been slow and evolutionary - and were developed over the course of a series of staged releases. </blockquote> <blockquote>I just can'tsee how this can be tackled in the incremental way that Gramps mostlyworks. The 'little improvements over time' approach seems to havegiven us a powerful but unwieldy tool. </blockquote>
= Possible ideas =
== Provide more '''Natural Transcription''' input methods == This is already addressed by [[GEPS_024:_Natural_transcription_of_Records|GEPS 024]].
* This is already addressed by [[GEPS_024:_Natural_transcription_of_Records|GEPS 024]].
== Reduce the number of editors ==
<blockquote>1. Reduce (gently) the number of different interfaces: this, ofcourse, means that some interfaces will be busier. Too often, confusionresults from too many windows open simultaneously. <br>- '''From: David Lynch - 2011-03-30 - [http://sourceforge.net/p/gramps/mailman/message/27281113/ Re: (Gramps-devel) Focus On User Interface, Usability]'''</blockquote>
At present, Gramps is largely based on a paradigm of one-to-one correspondence between editors and (internal) database objects.
* Add help buttons where missing
* If no {{man button|Help}} button can be shown for the page ensure that pressing {{man key press|F1}} brings the user to the correct page and not just the Manual index eg: correct context.
 
Know your audience, who is uses this software?
* Icons are nice, text labels are better. (no mystery meat navigation)
* Add an help icon to the toolbar eg a question mark '''?''' etc.
=== Roll over of user manual ===
Currently As of 20150831 the manual roll over occurs just before a release is made, this is too late for practical use by translators etc.
I suggest we change the way this is done so that updating the user manual is in sync with changes in Gramps master.
*Tooltips
==== Existing help API's ====
 
;gramps.cli
* gramps.cli.argparser.ArgParser.print_help
:<code>print_help()</code> If the user gives the –help or -h option, print the output to terminal.
 
;gramps.gen
* gramps.gen.plug._pluginreg.PluginData.help_url
:<code>help_url</code> The URL where documentation for the URL can be found
* gramps.gen.plug.menu._option.Option.get_help
:<code>get_help()</code> Get the help information for this option. Returns: A string that provides additional help beyond the label.
* gramps.gen.plug.menu._option.Option.set_help
:<code>set_help(help_text)</code> Set the help information for this option. Parameters: help – A string that provides additional help beyond the label. Example: “Whether to include or exclude people who are calculated to be alive at the time of the generation of this report” Returns: nothing
 
;gramps.gui
* gramps.gui.editors.filtereditor.EditFilter.on_help_clicked
:<code>on_help_clicked(obj)</code> Display the relevant portion of Gramps manual
* gramps.gui.editors.filtereditor.EditRule.on_help_clicked
:<code>on_help_clicked(obj)</code> Display the relevant portion of Gramps manual
* gramps.gui.editors.filtereditor.FilterEditor.help_clicked
:<code>help_clicked(obj)</code> Display the relevant portion of Gramps manual
 
<hr>
Github searches for:
* [https://github.com/gramps-project/gramps/search?utf8=%E2%9C%93&q=WIKI_HELP_PAGE WIKI_HELP_PAGE]
* URL_MANUAL_PAGE
* WIKI_HELP_SEC
* [https://github.com/gramps-project/gramps/search?utf8=%E2%9C%93&q=help_url help_url]
* [https://github.com/gramps-project/gramps/search?utf8=%E2%9C%93&q=help_text help_text]
 
==== Idea ====
Have a unique '''gramps_help_key''' for each type of help that does not change between versions.
Existing translations are out of sync (outdated) with the English version.
UseInstall and use: * The '''Translate extension''' tool to translate every kind of text. It's used especially to translate software and to manage multilingual wikis in a sensible way. https://www.mediawiki.org/wiki/Extension:Translate
<!--
==== xxxx.gramps-project.org ====
* Select Child window to open at last used name.
* Improve usability of export assistant filters.
 
= See also =
* {{bug|8686}} Prototype for a new "Event Entry" window.
* {{bug|1577}} Cumbersome work flow to add more people to an event
* {{bug|7807}} main window makeover (full-screen option)
[[Category:GEPS|U]]

Navigation menu