Difference between revisions of "GEPS 041: New Selector"

From Gramps
Jump to: navigation, search
(Set of filter rules)
m (Screenshots)
Line 10: Line 10:
 
===Screenshots===
 
===Screenshots===
  
[[File:Select-family.png|Family selector]]
+
[[File:Select-family_42.png|Family selector]]
  
 
{{-}}
 
{{-}}

Revision as of 11:00, 19 March 2016

What should be the Selector?

What is the need?

  1. Select one record (object) via the Graphical User Interface
  2. Display main data, for letting the user make the selection
  3. Usability and consistency
  4. Search and filter features

Screenshots

Family selector


Usability

  1. Selection
  2. Edition

Additional features and related concepts

  1. Reports
  2. Filtering for selecting a group of records (objects)
  3. Navigation and active objects
  4. Runtime and performance
  5. Selection expected by the user

Filter vs. Search

There are two ways to find data in Gramps: Search and Filter.

  • The Search will only match what is visible.
  • Filters are not limited to what you see on the screen, but looks at the actual data.

See some filters for more details.

Search Bar

The current design of the Search bar lets us find visible data on active column. The Search Bar is often available on selectors.

Search Bar concept

Set of filter rules

For now, some selectors, on reports and on Family Editor, provide a fast filter, by default.

The Search bar is disabled and an additionnal Show all bouton is available at the bottom of the dialog.

These windows are trying to provide a quick and common selection of people.

e.g., filtered by gender on Family Editor, or bookmarked people on reports.

Mother selector via fast filtering and 'Show all' button at the bottom


Interactive Search

For limiting a gtk issue on Search field, gramps has it own interactive search widget.

Interactive Search

Just write the first letter of the word on the dialog, and the cursor will try to find this word.

Like the Find shortcut box, available with CTRL+F or CMND+F.

Current limits on current selectors

  1. Performance
  2. Time for search
  3. Few fast and clever filter rules, by default
  4. Consistency
  5. Mixup of features and widgets

There is also a Gtk SearchEntry bug and limitation (latency/seizure) limiting a good search match.

Proposals

  • Fast filter by default

Some experimentations have been made on feature request 5024.

Current selector ecosystem already provides this ability.

See selector on reports and Father/Mother selector on Family Editor.

There is a bug 9315 on the Show all/Find features. See others

  • Clever search for each selector
  • Interface for handling and selecting custom filters on selectors

Additional proposals

  1. Replace the Show all check box at the bottom by a Switcher at the top of the dialog.

GtkSwitcher


See also

Feature requests

  • 9276: Need ability to search alternate place names when selecting place
  • 8762: Last Used places in the Select Place window
  • 8743: Search for place needs more options
  • 7342: Show "Main Participants" with events
  • 6558: Optimize the use of citations
  • 5142: Keep selected the last selected source
  • 5037: [Reports] More names listed in the person/family selector box
  • 5024: By default, to display [Last Recent Used] and [bookmarked] objects on selectors

Others

  • 9315: [Regression]: filter set by default on selector is ignored on load (_init_)
  • 9314: Two selectors on Places report can generate a confusion
  • 9028: Find is broken when used in the Family selector
  • 7536: Events model does not have 8 columns
  • 5032: Report selection logic