1
* Allow for multiple notes. A tabbed interface would be really useful,
2
since there are no titles for notes. Not all objects would necessarily
3
need multiple notes. Determine which ones should and shouldn't.
4
=== THESE should be obsoleted once we move to a database
5
* Speed up the reading of the database. The python XML routines are not
6
as fast as I would like, and it can take a minute or so to read a
7
large database. This is way too slow.
8
* Finish the generic load of revision control interfaces to allow a
9
revision control plugin system. Most of the work is already done.
10
* Disable the save buttons if gramps database is marked read-only. Disable
11
the adding of media objects as well, since this will cause gramps to
12
try to create a thumbnail in a readonly database.
16
See http://sourceforge.net/mailarchive/forum.php?thread_id=3252078&forum_id=1993
17
* Add string substitutions for web page generation (name, report name,
19
* Add support for sources of the parent/child relation
20
* Add support for storing reliability (confidence) of the marriage information;
21
see http://sourceforge.net/mailarchive/forum.php?thread_id=3066997&forum_id=1993
22
and http://sourceforge.net/mailarchive/forum.php?thread_id=3134931&forum_id=1993
24
* Make Date parsing locale dependent, like relationship calculator
25
* Add Confession as a standard event
26
* Now that the completeness flag exists, create filters that are using it
27
(both individual and family).
28
* Add autofill feature for City, Church parish, County, State and Country?
29
* Sort events by date (currently sorted by the order of entry).
30
* Select an alternative birth (death) as a prefered one.
31
* Add alternative dates/names into reports (substitutions?)
32
* Report designers (based on substitutions)
33
* Image regions support
34
* Report containing all related people.
35
* And a whole lot more....
added
removed
TODO
