I’m not sure where this cloning would start and stop.
Do you expect that the secondary objects will be clone too? Or shared? How would you designate one or the other?
If you look at the Data Entry gramplet, it templates People from another person using the Copy Active Person button. It has rules about what 2ndry items to clone and which to share.
My bad!
By secondary object, I mean “second level” or “not primary” (gramps db). Child objects on iteration will not be “secondary objects”. So, secondary objects, like attributes, addresses, associations, etc.
@emyoulation,
You are right, I thought on the tiny XML viewer (hierarchical view) when Doug asked for a challenge.
Yes, something like that would be nice.
Could that be used to achieve this feature request?
With great power comes … the probability that you can really create a mess. One would have to be very careful about what was copied and what wasn’t in a clone. I think a clone function (and a GUI controls) are out of scope for this gramplet. Although still worth thinking about. If we went to the trouble of making it though, it would be easy to just add as a popup on an object.
I didn’t add any new functionality to Gramps, I just made an easy interface for Gram.py
