On Thu, 2005-05-26 at 16:04, Don Allingham wrote:
> Now that 2.0.x is released, it is time to start looking at reports. If
> you have a chance, please answer the following questions:
> 1) What reports does GRAMPS have that are useful?
I currently use the Relationship Graph to get a graphical family tree.
I use Detailed Descendant because it uses the images I have.
> 2) What reports does GRAMPS have that are not useful?
> 3) What reports does GRAMPS need that it does not have?
> 4) How can the current reports be improved.
Actually, the answers to each are the same, kinda. The Relationship
Graph is good. What Gramps needs in the way of text reports is one that
can print most (if not all) of the information that Gramps can hold.
You can argue that it would be hard to print the stuff that a particular
user adds (like a new event), but the text report should be able to
write up the information stored in the basic fields that Gramps comes
What I would like are things like:
1) Ability to print out information stored in all the Gramps basic
2) Pictures (with the ability to select 'use all pictures' or 'use first
picture' -- which implementation wise could just be an 'use only first
picture' checkbox which, if not checked uses all pictures).
3) Being able to add the pictures with captions which would be the title
associated with each image in the database.
4) Ability to save options. I always have to repick the same stuff. It
would be nice if I could save and reload my settings or have Gramps just
remember the last settings used. Even going back without quitting, all
the options are reset back to defaults.
For anybody that rememberd the proof-of-concept 'All-In-One' report
plugin a while ago, I tried to solve the problems I saw. Since then, I
started again on a report plugin that I called 'Extensive Report' (I
didn't like All-In-One but I couldn't think of a better name at the
time). Both had the same type of architecture (with Extensive being a
better design of it). Features included:
1) Plugin support (yes, a plugin can have it's own plugins!) This
allowed multiple people to help develop independently (as long as they
weren't changing the core part). The report plugin would only offer
options for those plugins that it could find (a plugin to write
Birth/Death information, a plugin to write Marriage information, etc.).
This would also allow the report plugin to write out more information as
the subplugins got created.
2) Abililty to load and save options. No more having to remember what
There is probably more, but I haven't been able to work on it for a
while and I don't remember all the particulars anymore. It was written
and works with Gramps v1.0.11. 'Extensive' right now can write out
Birth/Death & Marriage information crudely (so it's not as fully
featured as I would like -- no infrastructure to do pictures yet).
Now that 2.x is out, I don't know if the plugin part changed. I now run
Red Hat 9 at work (still run Solaris at home), and I couldn't find any
RPMs of the newer GNOME version needed for Gramps v2.x for RH9. I can't
even figure out how to see what version is installed (I run the KDE
desktop and I can see a version for that, but don't know what to do
about GNOME). Given that, it might be a long time before I start up on
'Extensive' again. I'm guessing that better report plugins might come
out in the meantime. If anybody is interested in seeing it, I can make
it available online.
Adam Stein @ Xerox Corporation Email: adam@...
Disclaimer: Any/All views expressed
here have been proved to be my own. [http://www.csh.rit.edu/~adam/]