From: Jérôme <rom...@ya...> - 2008-12-29 10:03:41
|
>>> Second -- Descendants >>> >>> The pedigree view is great for viewing ancestors. Is there a view >>> for descendants? >>> >> You can of course view part of a descendant line in pedigree view, by >> selection, but otherwise no. It's a nice idea though. How would a >> descendant view control which children to display (an ancestor view >> displays parents, of which there are only two...)? > > Having 2 parents definitely simplifies the ancestor view! The > layout for descendants is more complex since the numbers vary. I'll > give some thought to it and let you know. The 'interactive descendant browser' tool should do the job ! I cannot access to www.gramps-project.org ([Gramps-devel] GRAMPS web site down?) and online documentation, but on tool menu something like : "Analyse and search -> Descendant browser" will display the descendants of active person. Jérôme David Relson a écrit : > On Mon, 29 Dec 2008 13:34:55 +1100 > Martin Steer wrote: > >> David Relson <re...@os...> writes: >> >>> Second -- Descendants >>> >>> The pedigree view is great for viewing ancestors. Is there a view >>> for descendants? >>> >> You can of course view part of a descendant line in pedigree view, by >> selection, but otherwise no. It's a nice idea though. How would a >> descendant view control which children to display (an ancestor view >> displays parents, of which there are only two...)? > > Having 2 parents definitely simplifies the ancestor view! The > layout for descendants is more complex since the numbers vary. I'll > give some thought to it and let you know. > >>> Third -- Marriage >>> >>> What's the best way to add a spouse, i.e. a new "married to" person? >>> >>> What's the easiest way to take two people records and link them >>> as married? >>> >> I'd use the Families view for both of these. Add a family then select >> for the details. > > Info appreciated. I was looking for a way to add attributes to a > person rather than creating a new entity and adding to it. > > As I'm using Gramps, I'm noticing a variety of niggles -- things that > could be improved. I've been doing some importing of trees and the > resulting cleanup is a bit of a pain. A couple of ideas have occurred > to me: > > When merging duplicate people, auto-prune duplicated events. > Consider when 2 John Does with identical birth dates are merged. > Gramps produces 1 John Doe with a duplicate birth date event. It > should be easy to auto-prune these. Merging trees can also produce > duplicated families -- another pruning opportunity. I'm sure there > are many such opportunities. I'll take a look at the python code and > see what I can come up with. > > In a similar vein, orphan events can be handled better. Merging > people and removing duplicated (but not identical) events, > produces such orphans. Gramps is already able to tell me whether an > event is still referenced or not. A logical extension is "remove > non-referenced events". Again, I'll take a look at the code. > > 'Tis nice to have an open source program available as niggles > like these are fixable. > > Regards, > > David > > ------------------------------------------------------------------------------ > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |