I don't think calc est is possible. It would be a new qualifier.

You could use the approach as in eg unused objects tool: calculate everything, then show a treeview with the changes that will happen, allowing people to deselect changes they do not want.

To recognize which dates have been created by the tool before, I'm out of ideas. It should be done cleanly, so best not to have a special identifier, it would have to be supported everywhere. As the meaning is not different from calc, that looks like a bad move.

Perhaps an attribute you can recognize. Would be usefull for the reseacher too, you see attribute indicating you calculated it with the tool, to eg key= generator, value: thetool.

Don't know. Anybody better ideas?


2007/11/21, Douglas S. Blank <dblank@cs.brynmawr.edu>:
I've been exploring integrating ideas around "possibly alive" into GRAMPS
for a while, for example:

Thanks to suggestions by Benny, it seems like the right way to do this is
to have a tool that goes through and adds birth and death events for
people,  and marking the dates as calculated (marked with "cal"). Adding
them seems easy enough. But one issue might be: how would GRAMPS update a
calculated date that it has already added previously?

First, is it legal having both "cal est" (calculated and estimated) in a
date field? If I used "cal est" would it be a problem if GRAMPS considered
those type of dates auto-changable (ie, when you re-run the tool, could it
better estimate the dates and update)?

Anyone see any problems with this approach? Any other suggestions? Questions?


This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
Gramps-devel mailing list