gramps

On Tue, 2003-06-10 at 11:57, Tim Waugh wrote:
> Why do getBirth and getDeath make up new events if there is no event
> in the database?

A lot of this due to historical reasons. The birth and death records are
used all over the place. For this reason, it is not stored in the event
list, even though they are events. Searching the list continuously would
consume a lot of time. This, combined with the fact that they are
displayed on the EditPerson form, and not in the dynamic event lists,
made it a simpler solution at the time.

At some point I should probably revisit this and see if it can be
cleaned up.

> 
> It makes report code quite convoluted to write.  I'd like to be able
> to say:
> 
> death = person.getDeath ()
> if death:
>    ...
> 
> but instead I apparently have to check every event attribute except
> for the name!
> 
> Is there a better way to do what I'm trying to do?

It might make sense to provide a "helper" function that would perform a
similar function. Maybe:

death = person.getValidDeath()
if death:
  ....

Don

-- 
Don Allingham <dallingham@...>
GRAMPS OpenSource Genealogy

On Tue, Jun 10, 2003 at 06:54:48PM -0600, Don Allingham wrote:

> It might make sense to provide a "helper" function that would perform a
> similar function. Maybe:
>=20
> death =3D person.getValidDeath()
> if death:
>   ....

Yes, that might be a good idea.  In the mean time it is very easy to
work around for what I need.

My next question is:

How do I define cell styles and have them appear in the output HTML?
make_default_stylesheet only allows me to add paragraph styles it
seems.

Tim.
*/

On Wed, Jun 11, 2003 at 02:59:09PM +0100, Tim Waugh wrote:
> My next question is:
> 
> How do I define cell styles and have them appear in the output HTML?
> make_default_stylesheet only allows me to add paragraph styles it
> seems.

This is the minimal way to do it from the report:

cell = TextDoc.TableCellStyle()
self.doc.add_cell_style('Normal',cell)

This would produce a default cell and it would appear in all formats, 
not only HTML.

See also the following methods in TextDoc.TableCellStyle class which 
operate on the details of the cell:

set_padding(val)
set_right_border(val)
set_left_border(val)
set_top_border(val)
set_bottom_border(val)
set_longlist(val)
get_padding()
get_right_border()
get_left_border()
get_top_border()
get_bottom_border()
get_longlist()

Alex

-- 
Alexander Roitman   http://ebner.neuroscience.umn.edu/people/alex.html
Dept. of Neuroscience, Lions Research Building
2001 6th Street SE, Minneapolis, MN  55455
Tel (612) 625-7566   FAX (612) 626-9201

On Wed, Jun 11, 2003 at 09:52:06AM -0500, Alex Roitman wrote:

> On Wed, Jun 11, 2003 at 02:59:09PM +0100, Tim Waugh wrote:
> > My next question is:
> >=20
> > How do I define cell styles and have them appear in the output HTML?
> > make_default_stylesheet only allows me to add paragraph styles it
> > seems.
>=20
> This is the minimal way to do it from the report:
>=20
> cell =3D TextDoc.TableCellStyle()
> self.doc.add_cell_style('Normal',cell)
>=20
> This would produce a default cell and it would appear in all formats,=20
> not only HTML.

That's what I tried, but in HTML output in particular I don't see the
styles written out.  Try a Complete Individual report, for instance,
and look for NormalCell.  Is this an HtmlDoc.py bug?

Tim.
*/

On 2003.06.11 09:59, Tim Waugh wrote:
> On Wed, Jun 11, 2003 at 09:52:06AM -0500, Alex Roitman wrote:
> > This is the minimal way to do it from the report:
> >
> > cell = TextDoc.TableCellStyle()
> > self.doc.add_cell_style('Normal',cell)
> >
> > This would produce a default cell and it would appear in all
> > formats, not only HTML.
> 
> That's what I tried, but in HTML output in particular I don't see the
> styles written out.  Try a Complete Individual report, for instance,
> and look for NormalCell.  Is this an HtmlDoc.py bug?

As a matter of fact, I cannot create a Complete Individual report with 
the current CVS -- it complains about relationship loops no matter whom 
I choose as a center person. 
Although, the exact same thing produces correct cells in the FTM style 
descendant report. Here's the HTML excerpt:

  <td valign="top" width="10%" class="Normal"><p class="Details">2.</p>
</td>
<td valign="top" width="5%" class="Normal"><p class="Details">i.</p>
</td>
<td valign="top" width="85%" class="Normal"><p class="Details">Mason 
Michael Smith was born June 26, 1996 in Hayward, Alameda Co., CA.</p>
</td>

The only problem is that the "style" section does not contain "Normal" 
-- you're right, this has to be recorded. 
I am not sure if this is an HTML-only bug:
* Apparently, abiword writes cells without reference to the cell style 
name -- it just records all the cell properties every time the cell 
appears.
* OOo has the same problem as HTML.
* LaTeX does not have the problem since it has no style for cells.

So it seems that, at least, HTML and OOo should record the definition 
of the cell styles in the style section of the doc. 
Don, do you agree?

Alex

-- 
Alexander Roitman   http://ebner.neuroscience.umn.edu/people/alex.html
Dept. of Neuroscience, Lions Research Building
2001 6th Street SE, Minneapolis, MN  55455
Tel (612) 625-7566   FAX (612) 626-9201

Alex Roitman wrote:

> As a matter of fact, I cannot create a Complete Individual report with 
> the current CVS -- it complains about relationship loops no matter 
> whom I choose as a center person. Although, the exact same thing 
> produces correct cells in the FTM style descendant report. 

Are you applying the same filter to both reports? This message should be 
coming from the applied filter, not the report. I added the loop check 
after some people were encountering infinite loops trying to build an 
ancestor list.  The relationships had somthing like A -> B -> C -> A

Don

On 2003.06.11 11:51, Don Allingham wrote:
> Alex Roitman wrote:
> 
>> As a matter of fact, I cannot create a Complete Individual report 
>> with the current CVS -- it complains about relationship loops no 
>> matter whom I choose as a center person. Although, the exact same 
>> thing produces correct cells in the FTM style descendant report.
> 
> Are you applying the same filter to both reports? This message should 
> be coming from the applied filter, not the report. I added the loop 
> check after some people were encountering infinite loops trying to 
> build an ancestor list.  The relationships had somthing like A -> B -
> > C -> A

Now that you said that, I checked and found that I only get a loop with 
the filter "Ancestors of such-and-such". The rest of filters goes 
smoothly with the Complete Individual report. The "Ancestors" filter is 
the default, that's why I had trouble. So, it seems to be an ancestor 
filter problem, since there's no loop in the relationship. 
As for the FTM style descendant report, it does not use the filter at 
all -- it always uses the descendants of the person. 
Alex

-- 
Alexander Roitman   http://ebner.neuroscience.umn.edu/people/alex.html
Dept. of Neuroscience, Lions Research Building
2001 6th Street SE, Minneapolis, MN  55455
Tel (612) 625-7566   FAX (612) 626-9201