Difference between revisions of "GEPS 041: New Selector"
m (→Current limits on current selectors) |
m (→Current limits on current selectors) |
||
Line 76: | Line 76: | ||
# Consistency, mixup of features and widgets | # Consistency, mixup of features and widgets | ||
− | + | Note, there is still a [[#Interactive_Search|Gtk SearchEntry bug and limitation (latency/seizure)]] | |
− | limiting a good search match. | + | limiting a good search match by using GtkSearchEntry. |
==Proposals== | ==Proposals== |
Revision as of 11:55, 19 March 2016
What should be the Selector?
Contents
What is the need?
- Select one record (object) via the Graphical User Interface
- Display main data, for letting the user make the selection
- Usability and consistency
- Search and filter features
Screenshots
Usability
- Selection
- Edition
- Reports
- Filtering for selecting a group of records (objects)
- Navigation, history and active objects
- Runtime and performance
- Selection expected by the user, marked and tagged objects
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.
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.
Interactive Search
For limiting a gtk issue on Search field, gramps42 has it own interactive search widget.
Just write the first letters 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
- Performance
- Time for search
- Few fast and filter rules, by default
- Consistency, mixup of features and widgets
Note, there is still a Gtk SearchEntry bug and limitation (latency/seizure) limiting a good search match by using GtkSearchEntry.
Proposals
- Fast filter by default
Some experimentations have been made on feature request 5024.
Current selector ecosystem already provides this ability.
See Person 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
- Replace the Show all check box at the bottom by a Switcher at the top of the dialog.
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