GRAMPS › GRAMPS - Dev

DescendantsLines plugin

Classic

List

Threaded

16 messages Options

lcc .

DescendantsLines plugin

I've been trying the DescendantsLines plugin --
http://www.gramps-project.org/wiki/index.php?title=DescendantsLines --
and I can second Jerome's claim -- it works! I found some problems
though which I have solved, so I'm writing so you can make it work
easily.

Copy the files to $GRAMPSHOME/gramps/gramps33/plugins from svn. But
that's not enough. If you only do that, the plugin will choke because
the hardcoded directory it writes the temporary .xml file to does not
exist, and error. So after copying the files you need to create the
directory: mkdir DescendantsLines inside
$GRAMPSHOME/gramps/gramps33/plugins. Then select whichever output
format you want, I did .pdf, and select the output path. It will
create the pdf file with a list of entries, but that's not the
plugin's output. The output is to be found in
$GRAMPSHOME/DescendantsLines.png . I have commented out lines 665, 666
and 670 of DescentantsLines.py for a much nicer naming format imo. The
code seems good. Please help test this and we will probably be able to
release it soon. I can assure you it will be a major Gramps feature,
even though it's not using the standard interface (misleading output
path/real output path). That should be easy to fix with time.

lcc

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel

Helge@Gramps

Re: DescendantsLines plugin

I tried to use it, but:
37141: ERROR: _reportdialog.py: line 641: Failed to run report.
Traceback (most recent call last):
File "C:\ProgrammeNeutral\GrampsTrunk\src\gui\plug\report\_reportdialog.py", line 616, in report
MyReport.write_report()
File "D:\GRAMPS\ZZ_Trunc\gramps\gramps33\plugins\DescendantsLines\DescendantsLines.py", line 159, in write_report
self.write_tmp_data(ind_list)
File "D:\GRAMPS\ZZ_Trunc\gramps\gramps33\plugins\DescendantsLines\DescendantsLines.py", line 227, in write_tmp_data
self.write_xml_person(identifiant, child, gender, first, surname, event_list)
UnboundLocalError: local variable 'surname' referenced before assignment

Environment:
Win7, 64 Bit German
Python 2.6.5
GTK+ 2.16.6
pyGTK 2.16.0
gobject 2.20.0
cairo 1.4.12
enchant 1.5.3
graphviz 2.26.3

-Helge

lcc .

Re: DescendantsLines plugin

I think that's a bug with people with no surnames in a database. I have added:
if not surname:
surname = ''
after line 225. Try the attached file with all modifications I'm
using. Works for me, hopefully it will work for you now.

lcc

On 12/23/10, Helge@Gramps <[hidden email]> wrote:

>
> I tried to use it, but:
> 37141: ERROR: _reportdialog.py: line 641: Failed to run report.
> Traceback (most recent call last):
> File
> "C:\ProgrammeNeutral\GrampsTrunk\src\gui\plug\report\_reportdialog.py", line
> 616, in report
> MyReport.write_report()
> File
> "D:\GRAMPS\ZZ_Trunc\gramps\gramps33\plugins\DescendantsLines\DescendantsLines.py",
> line 159, in write_report
> self.write_tmp_data(ind_list)
> File
> "D:\GRAMPS\ZZ_Trunc\gramps\gramps33\plugins\DescendantsLines\DescendantsLines.py",
> line 227, in write_tmp_data
> self.write_xml_person(identifiant, child, gender, first, surname,
> event_list)
> UnboundLocalError: local variable 'surname' referenced before assignment
>
> Environment:
> Win7, 64 Bit German
> Python 2.6.5
> GTK+ 2.16.6
> pyGTK 2.16.0
> gobject 2.20.0
> cairo 1.4.12
> enchant 1.5.3
> graphviz 2.26.3
>
> -Helge
> --
> View this message in context:
> http://gramps.1791082.n4.nabble.com/DescendantsLines-plugin-tp3162328p3162438.html
> Sent from the GRAMPS - Dev mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
> to consolidate database storage, standardize their database environment,
> and,
> should the need arise, upgrade to a full multi-node Oracle RAC database
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Gramps-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel

DescendantsLines.py (40K) Download Attachment

lcc .

Re: DescendantsLines plugin

Sorry about that, that was not a fix. The attached file now might
actually work. If any error occurs please reply.

On 12/23/10, lcc . <[hidden email]> wrote:

> I think that's a bug with people with no surnames in a database. I have
> added:
> if not surname:
> surname = ''
> after line 225. Try the attached file with all modifications I'm
> using. Works for me, hopefully it will work for you now.
>
> lcc
>
> On 12/23/10, Helge@Gramps <[hidden email]> wrote:
>>
>> I tried to use it, but:
>> 37141: ERROR: _reportdialog.py: line 641: Failed to run report.
>> Traceback (most recent call last):
>> File
>> "C:\ProgrammeNeutral\GrampsTrunk\src\gui\plug\report\_reportdialog.py",
>> line
>> 616, in report
>> MyReport.write_report()
>> File
>> "D:\GRAMPS\ZZ_Trunc\gramps\gramps33\plugins\DescendantsLines\DescendantsLines.py",
>> line 159, in write_report
>> self.write_tmp_data(ind_list)
>> File
>> "D:\GRAMPS\ZZ_Trunc\gramps\gramps33\plugins\DescendantsLines\DescendantsLines.py",
>> line 227, in write_tmp_data
>> self.write_xml_person(identifiant, child, gender, first, surname,
>> event_list)
>> UnboundLocalError: local variable 'surname' referenced before assignment
>>
>> Environment:
>> Win7, 64 Bit German
>> Python 2.6.5
>> GTK+ 2.16.6
>> pyGTK 2.16.0
>> gobject 2.20.0
>> cairo 1.4.12
>> enchant 1.5.3
>> graphviz 2.26.3
>>
>> -Helge
>> --
>> View this message in context:
>> http://gramps.1791082.n4.nabble.com/DescendantsLines-plugin-tp3162328p3162438.html
>> Sent from the GRAMPS - Dev mailing list archive at Nabble.com.
>>
>> ------------------------------------------------------------------------------
>> Learn how Oracle Real Application Clusters (RAC) One Node allows
>> customers
>> to consolidate database storage, standardize their database environment,
>> and,
>> should the need arise, upgrade to a full multi-node Oracle RAC database
>> without downtime or disruption
>> http://p.sf.net/sfu/oracle-sfdevnl
>> _______________________________________________
>> Gramps-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>>
>

DescendantsLines.py (40K) Download Attachment

jerome

Re: DescendantsLines plugin

In reply to this post by lcc .

> surname = ''
> after line 225.

Yes, surname was not set ...
You can add it after or before line 225!

I was maybe too lazy on this part! As I thought it was not possible to have a name without surname on trunk.

> I can second Jerome's claim -- it works!

True, but you also pointed out some limitations (patronymic line is not the best choice for Spanish, Portuguese, Slavic names)

> If you only do that, the plugin will choke because
the hardcoded directory it writes the temporary .xml file to does not exist, and error. So after copying the files you need to create the directory: mkdir DescendantsLines inside
$GRAMPSHOME/gramps/gramps33/plugins.

As it was very experimental I did not generated to addon package... You cannot try it with python sources only (need some paths set on const.py)

> Then select whichever output format you want, I did .pdf, and select the output path. It will create the pdf file with a list of entries, but that's not the plugin's output.

I do not know how to generate a 'real' draw report with this code.
I also made a 'fake' list, not directly related to report. Options (except person selector) are not active, because I do not know for what they are used!

I still get an error with the code used for script: it does not really use 'FamiliesDescendants' filter rule of selected person. I guess there is one error for checking spouse, so I exported all the database for not breaking the script logic ...

> Please help test this and we will probably be able to
release it soon.

I am not very confortable with the pass two
http://www.gramps-project.org/wiki/index.php?title=DescendantsLines#Pass_2:_use_draw_report_environment
but I suppose something hybride (not really a draw report) might be also released!

Note, I have tried to keep the script logic (DOM on XML), but it does not run like standard reports. I just tried to Grampsify a little bit the code, feel free to remove, improve, rewrite what you want.

I also like the print, result: it works!
But having working a little bit on it, and knowing that python quickly generates 'in use' code, maybe this cannot use in production! It is like laughing about current Gramps' report environment...

Jérôme

--- En date de : Jeu 23.12.10, lcc . <[hidden email]> a écrit :

> De: lcc . <[hidden email]>
> Objet: Re: [Gramps-devel] DescendantsLines plugin
> À: "Helge@Gramps" <[hidden email]>
> Cc: [hidden email]
> Date: Jeudi 23 décembre 2010, 19h46
> I think that's a bug with people with
> no surnames in a database. I have added:
> if not surname:
>
> surname = ''
> after line 225. Try the attached file with all
> modifications I'm
> using. Works for me, hopefully it will work for you now.
>
> lcc
>
> On 12/23/10, Helge@Gramps <[hidden email]>
> wrote:
> >
> > I tried to use it, but:
> > 37141: ERROR: _reportdialog.py: line 641: Failed to
> run report.
> > Traceback (most recent call last):
> >   File
> >
> "C:\ProgrammeNeutral\GrampsTrunk\src\gui\plug\report\_reportdialog.py",
> line
> > 616, in report
> >    MyReport.write_report()
> >   File
> >
> "D:\GRAMPS\ZZ_Trunc\gramps\gramps33\plugins\DescendantsLines\DescendantsLines.py",
> > line 159, in write_report
> >    self.write_tmp_data(ind_list)
> >   File
> >
> "D:\GRAMPS\ZZ_Trunc\gramps\gramps33\plugins\DescendantsLines\DescendantsLines.py",
> > line 227, in write_tmp_data
> >
>    self.write_xml_person(identifiant, child,
> gender, first, surname,
> > event_list)
> > UnboundLocalError: local variable 'surname' referenced
> before assignment
> >
> > Environment:
> > Win7, 64 Bit German
> > Python 2.6.5
> > GTK+ 2.16.6
> > pyGTK    2.16.0
> > gobject   2.20.0
> > cairo    1.4.12
> > enchant   1.5.3
> > graphviz 2.26.3
> >
> > -Helge
> > --
> > View this message in context:
> > http://gramps.1791082.n4.nabble.com/DescendantsLines-plugin-tp3162328p3162438.html
> > Sent from the GRAMPS - Dev mailing list archive at
> Nabble.com.
> >
> >
> ------------------------------------------------------------------------------
> > Learn how Oracle Real Application Clusters (RAC) One
> Node allows customers
> > to consolidate database storage, standardize their
> database environment,
> > and,
> > should the need arise, upgrade to a full multi-node
> Oracle RAC database
> > without downtime or disruption
> > http://p.sf.net/sfu/oracle-sfdevnl
> > _______________________________________________
> > Gramps-devel mailing list
> > [hidden email]
> > https://lists.sourceforge.net/lists/listinfo/gramps-devel
> >
>
> -----La pièce jointe associée suit-----
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node
> allows customers
> to consolidate database storage, standardize their database
> environment, and,
> should the need arise, upgrade to a full multi-node Oracle
> RAC database
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> -----La pièce jointe associée suit-----
>
> _______________________________________________
> Gramps-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>

lcc .

Re: DescendantsLines plugin

The DescendentFamilies rule needs to be checked, and then the surname,
but these are minor issues. The output is excellent, so I don't mind
if it's using the report environment resources or not. As long as it
is stable and works. It can always be improved later.

lcc

On 12/23/10, jerome <[hidden email]> wrote:

>> surname = ''
>> after line 225.
>
> Yes, surname was not set ...
> You can add it after or before line 225!
>
> I was maybe too lazy on this part! As I thought it was not possible to have
> a name without surname on trunk.
>
>> I can second Jerome's claim -- it works!
>
> True, but you also pointed out some limitations (patronymic line is not the
> best choice for Spanish, Portuguese, Slavic names)
>
>> If you only do that, the plugin will choke because
> the hardcoded directory it writes the temporary .xml file to does not exist,
> and error. So after copying the files you need to create the directory:
> mkdir DescendantsLines inside
> $GRAMPSHOME/gramps/gramps33/plugins.
>
> As it was very experimental I did not generated to addon package... You
> cannot try it with python sources only (need some paths set on const.py)
>
>> Then select whichever output format you want, I did .pdf, and select the
>> output path. It will create the pdf file with a list of entries, but
>> that's not the plugin's output.
>
> I do not know how to generate a 'real' draw report with this code.
> I also made a 'fake' list, not directly related to report. Options (except
> person selector) are not active, because I do not know for what they are
> used!
>
> I still get an error with the code used for script: it does not really use
> 'FamiliesDescendants' filter rule of selected person. I guess there is one
> error for checking spouse, so I exported all the database for not breaking
> the script logic ...
>
>> Please help test this and we will probably be able to
> release it soon.
>
> I am not very confortable with the pass two
> http://www.gramps-project.org/wiki/index.php?title=DescendantsLines#Pass_2:_use_draw_report_environment
> but I suppose something hybride (not really a draw report) might be also
> released!
>
> Note, I have tried to keep the script logic (DOM on XML), but it does not
> run like standard reports. I just tried to Grampsify a little bit the code,
> feel free to remove, improve, rewrite what you want.
>
>
> I also like the print, result: it works!
> But having working a little bit on it, and knowing that python quickly
> generates 'in use' code, maybe this cannot use in production! It is like
> laughing about current Gramps' report environment...
>
>
>
> Jérôme
>
>
> --- En date de : Jeu 23.12.10, lcc . <[hidden email]> a écrit :
>
>> De: lcc . <[hidden email]>
>> Objet: Re: [Gramps-devel] DescendantsLines plugin
>> À: "Helge@Gramps" <[hidden email]>
>> Cc: [hidden email]
>> Date: Jeudi 23 décembre 2010, 19h46
>> I think that's a bug with people with
>> no surnames in a database. I have added:
>> if not surname:
>>
>> surname = ''
>> after line 225. Try the attached file with all
>> modifications I'm
>> using. Works for me, hopefully it will work for you now.
>>
>> lcc
>>
>> On 12/23/10, Helge@Gramps <[hidden email]>
>> wrote:
>> >
>> > I tried to use it, but:
>> > 37141: ERROR: _reportdialog.py: line 641: Failed to
>> run report.
>> > Traceback (most recent call last):
>> > File
>> >
>> "C:\ProgrammeNeutral\GrampsTrunk\src\gui\plug\report\_reportdialog.py",
>> line
>> > 616, in report
>> > MyReport.write_report()
>> > File
>> >
>> "D:\GRAMPS\ZZ_Trunc\gramps\gramps33\plugins\DescendantsLines\DescendantsLines.py",
>> > line 159, in write_report
>> > self.write_tmp_data(ind_list)
>> > File
>> >
>> "D:\GRAMPS\ZZ_Trunc\gramps\gramps33\plugins\DescendantsLines\DescendantsLines.py",
>> > line 227, in write_tmp_data
>> >
>> self.write_xml_person(identifiant, child,
>> gender, first, surname,
>> > event_list)
>> > UnboundLocalError: local variable 'surname' referenced
>> before assignment
>> >
>> > Environment:
>> > Win7, 64 Bit German
>> > Python 2.6.5
>> > GTK+ 2.16.6
>> > pyGTK 2.16.0
>> > gobject 2.20.0
>> > cairo 1.4.12
>> > enchant 1.5.3
>> > graphviz 2.26.3
>> >
>> > -Helge
>> > --
>> > View this message in context:
>> > http://gramps.1791082.n4.nabble.com/DescendantsLines-plugin-tp3162328p3162438.html
>> > Sent from the GRAMPS - Dev mailing list archive at
>> Nabble.com.
>> >
>> >
>> ------------------------------------------------------------------------------
>> > Learn how Oracle Real Application Clusters (RAC) One
>> Node allows customers
>> > to consolidate database storage, standardize their
>> database environment,
>> > and,
>> > should the need arise, upgrade to a full multi-node
>> Oracle RAC database
>> > without downtime or disruption
>> > http://p.sf.net/sfu/oracle-sfdevnl
>> > _______________________________________________
>> > Gramps-devel mailing list
>> > [hidden email]
>> > https://lists.sourceforge.net/lists/listinfo/gramps-devel
>> >
>>
>> -----La pièce jointe associée suit-----
>>
>> ------------------------------------------------------------------------------
>> Learn how Oracle Real Application Clusters (RAC) One Node
>> allows customers
>> to consolidate database storage, standardize their database
>> environment, and,
>> should the need arise, upgrade to a full multi-node Oracle
>> RAC database
>> without downtime or disruption
>> http://p.sf.net/sfu/oracle-sfdevnl
>> -----La pièce jointe associée suit-----
>>
>> _______________________________________________
>> Gramps-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>>
>
>
>
>

Helge@Gramps

Re: DescendantsLines plugin

In reply to this post by lcc .

Hi,

Using the attached file, it runs now behind the line containing "self.write_xml_person(identifiant, child, gender, first, surname, event_list)"

But I got the next error:
21480: ERROR: _reportdialog.py: line 641: Failed to run report.
Traceback (most recent call last):
File "C:\ProgrammeNeutral\GrampsTrunk\src\gui\plug\report\_reportdialog.py", line 616, in report
MyReport.write_report()
File "D:\GRAMPS\ZZ_Trunc\gramps\gramps33\plugins\DescendantsLines\DescendantsLines.py", line 190, in write_report
p = load_gramps(input_fn, pid)
File "D:\GRAMPS\ZZ_Trunc\gramps\gramps33\plugins\DescendantsLines\DescendantsLines.py", line 629, in load_gramps
x = xml.dom.minidom.parse(f)
File "C:\Program Files (x86)\Python26\lib\xml\dom\minidom.py", line 1918, in parse
return expatbuilder.parse(file)
File "C:\Program Files (x86)\Python26\lib\xml\dom\expatbuilder.py", line 928, in parse
result = builder.parseFile(file)
File "C:\Program Files (x86)\Python26\lib\xml\dom\expatbuilder.py", line 207, in parseFile
parser.Parse(buffer, 0)
ExpatError: mismatched tag: line 7345, column 18

- Helge

lcc .

Re: DescendantsLines plugin

The error you got is not in the script code, but the exported xml is
being considered invalid by the python xml parser module. Maybe
there's a problem in write_tmp_data(). If you can look at the xml and
tell us which tag is not being matched (line 7345, column 18) it might
help.

lcc

On 12/23/10, Helge@Gramps <[hidden email]> wrote:

>
> Hi,
>
> Using the attached file, it runs now behind the line containing
> "self.write_xml_person(identifiant, child, gender, first, surname,
> event_list)"
>
> But I got the next error:
> 21480: ERROR: _reportdialog.py: line 641: Failed to run report.
> Traceback (most recent call last):
> File
> "C:\ProgrammeNeutral\GrampsTrunk\src\gui\plug\report\_reportdialog.py", line
> 616, in report
> MyReport.write_report()
> File
> "D:\GRAMPS\ZZ_Trunc\gramps\gramps33\plugins\DescendantsLines\DescendantsLines.py",
> line 190, in write_report
> p = load_gramps(input_fn, pid)
> File
> "D:\GRAMPS\ZZ_Trunc\gramps\gramps33\plugins\DescendantsLines\DescendantsLines.py",
> line 629, in load_gramps
> x = xml.dom.minidom.parse(f)
> File "C:\Program Files (x86)\Python26\lib\xml\dom\minidom.py", line 1918,
> in parse
> return expatbuilder.parse(file)
> File "C:\Program Files (x86)\Python26\lib\xml\dom\expatbuilder.py", line
> 928, in parse
> result = builder.parseFile(file)
> File "C:\Program Files (x86)\Python26\lib\xml\dom\expatbuilder.py", line
> 207, in parseFile
> parser.Parse(buffer, 0)
> ExpatError: mismatched tag: line 7345, column 18
>
> - Helge
> --
> View this message in context:
> http://gramps.1791082.n4.nabble.com/DescendantsLines-plugin-tp3162328p3162694.html
> Sent from the GRAMPS - Dev mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
> to consolidate database storage, standardize their database environment,
> and,
> should the need arise, upgrade to a full multi-node Oracle RAC database
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Gramps-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>

jerome

Re: DescendantsLines plugin

Hi,

Have a look at your
D:\GRAMPS\ZZ_Trunc\gramps\gramps33\plugins\DescendantsLines\DescendantsLines.xml

If malformed, you will not be able to open it with Firefox (and its XML parser): this will display the line with the problem.

> (x86)\Python26\lib\xml\dom\expatbuilder.py", line
> 207, in parseFile
> parser.Parse(buffer, 0)

Not tested under {SVN}\plugins, XML file was planned to be written under $HOME\.gramps\gramps33\plugins\DescendantsLines\DescendantsLines.xml

Jérôme

--- En date de : Ven 24.12.10, lcc . <[hidden email]> a écrit :

> De: lcc . <[hidden email]>
> Objet: Re: [Gramps-devel] DescendantsLines plugin
> À: "Helge@Gramps" <[hidden email]>
> Cc: [hidden email]
> Date: Vendredi 24 décembre 2010, 0h10
> The error you got is not in the
> script code, but the exported xml is
> being considered invalid by the python xml parser module.
> Maybe
> there's a problem in write_tmp_data(). If you can look at
> the xml and
> tell us which tag is not being matched (line 7345, column
> 18) it might
> help.
>
> lcc
>
>
> On 12/23/10, Helge@Gramps <[hidden email]>
> wrote:
> >
> > Hi,
> >
> > Using the attached file, it runs now behind the line
> containing
> > "self.write_xml_person(identifiant, child, gender,
> first, surname,
> > event_list)"
> >
> > But I got the next error:
> > 21480: ERROR: _reportdialog.py: line 641: Failed to
> run report.
> > Traceback (most recent call last):
> >   File
> >
> "C:\ProgrammeNeutral\GrampsTrunk\src\gui\plug\report\_reportdialog.py",
> line
> > 616, in report
> >    MyReport.write_report()
> >   File
> >
> "D:\GRAMPS\ZZ_Trunc\gramps\gramps33\plugins\DescendantsLines\DescendantsLines.py",
> > line 190, in write_report
> >    p = load_gramps(input_fn,
> pid)
> >   File
> >
> "D:\GRAMPS\ZZ_Trunc\gramps\gramps33\plugins\DescendantsLines\DescendantsLines.py",
> > line 629, in load_gramps
> >    x = xml.dom.minidom.parse(f)
> >   File "C:\Program Files
> (x86)\Python26\lib\xml\dom\minidom.py", line 1918,
> > in parse
> >    return
> expatbuilder.parse(file)
> >   File "C:\Program Files
> (x86)\Python26\lib\xml\dom\expatbuilder.py", line
> > 928, in parse
> >    result =
> builder.parseFile(file)
> >   File "C:\Program Files
> (x86)\Python26\lib\xml\dom\expatbuilder.py", line
> > 207, in parseFile
> >    parser.Parse(buffer, 0)
> > ExpatError: mismatched tag: line 7345, column 18
> >
> > - Helge
> > --
> > View this message in context:
> > http://gramps.1791082.n4.nabble.com/DescendantsLines-plugin-tp3162328p3162694.html
> > Sent from the GRAMPS - Dev mailing list archive at
> Nabble.com.
> >
> >
> ------------------------------------------------------------------------------
> > Learn how Oracle Real Application Clusters (RAC) One
> Node allows customers
> > to consolidate database storage, standardize their
> database environment,
> > and,
> > should the need arise, upgrade to a full multi-node
> Oracle RAC database
> > without downtime or disruption
> > http://p.sf.net/sfu/oracle-sfdevnl
> > _______________________________________________
> > Gramps-devel mailing list
> > [hidden email]
> > https://lists.sourceforge.net/lists/listinfo/gramps-devel
> >
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node
> allows customers
> to consolidate database storage, standardize their database
> environment, and,
> should the need arise, upgrade to a full multi-node Oracle
> RAC database
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Gramps-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>

Helge@Gramps

Re: DescendantsLines plugin

In reply to this post by lcc .

Of course I could give more information without additional request. Sorry for that, but it was really late in the night...

There is a simple solution for me to prevent this error: Don't use "<" and/or ">" within names, surnames, ...

But I think, there should be a warning inside Gramps if one uses such special characters for some values.

After removing all "<" and/or ">" within names the report runs to a result.
But I got a lot of warnings like:
"...
Unknown event type: Residence
Unknown event type: Occupation
Unknown event type: Religion
Unknown event type: Occupation
Unknown event type: Residence
Unknown event type: Religion
Unknown event type: Occupation
Unknown event type: Occupation
Unknown event type: Religion
..."

As result of the report I always get a complete list of all person in my database. That's all.
No influence of any selected center person.

Question: Is there any where a description for all parameters?
It's difficult for me to understand Option S, O, F, ...

-Helge

PS: Merry Christmas to all. I'm fare from my computer for the next few hours...

lcc .

Re: DescendantsLines plugin

Hi,

Thank you. You might have found another bug with the "<and/or>"
problem. Gramps shouldn't choke if people use xml-tag-like data.

That said, the report works with the center person for me. It seems
you need to read my original email again and check the file
$GRAMPSHOME/DescendantsLines.png instead of the path you entered for
the output inside Gramps, which will indeed contain a list of all
people in your database. The real output is there for you to look at,
DescendantsLines.png. You just didn't open it yet.

There is another problem which I didn't mention: if I don't delete the
file DescendantsLines.png, it seems not to overwrite the old one.

The warnings are not from Gramps but are caused by the report code.
Don't mind them. The report only knows two event types, birth and
death it seems. For every other event it prints a line. Merry
Christmas.

lcc

On 12/24/10, Helge@Gramps <[hidden email]> wrote:

>
> Of course I could give more information without additional request. Sorry
> for
> that, but it was really late in the night...
>
> There is a simple solution for me to prevent this error: Don't use "<"
> and/or ">" within names, surnames, ...
>
> But I think, there should be a warning inside Gramps if one uses such
> special characters for some values.
>
> After removing all "<" and/or ">" within names the report runs to a result.
> But I got a lot of warnings like:
> "...
> Unknown event type: Residence
> Unknown event type: Occupation
> Unknown event type: Religion
> Unknown event type: Occupation
> Unknown event type: Residence
> Unknown event type: Religion
> Unknown event type: Occupation
> Unknown event type: Occupation
> Unknown event type: Religion
> ..."
>
> As result of the report I always get a complete list of all person in my
> database. That's all.
> No influence of any selected center person.
>
> Question: Is there any where a description for all parameters?
> It's difficult for me to understand Option S, O, F, ...
>
> -Helge
>
> PS: Merry Christmas to all. I'm fare from my computer for the next few
> hours...
> --
> View this message in context:
> http://gramps.1791082.n4.nabble.com/DescendantsLines-plugin-tp3162328p3163176.html
> Sent from the GRAMPS - Dev mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
> to consolidate database storage, standardize their database environment,
> and,
> should the need arise, upgrade to a full multi-node Oracle RAC database
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Gramps-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>

lcc .

Re: DescendantsLines plugin

Some comments below for what I wrote last message:

>You might have found another bug with the "<and/or>"
> problem. Gramps shouldn't choke if people use xml-tag-like data.

This can be fixed adding some sort of quotemeta() in the report code
which is writing the xml. So it's a report issue. Gramps itself
doesn't have these problems anymore that we know of. If it did, it'd
be a bug, as this is a bug.

>The report only knows two event types, birth and
> death it seems. For every other event it prints a line.

That is, know two events for now. It should be easy to expand its
range of events and remove the warnings.

lcc

> On 12/24/10, Helge@Gramps <[hidden email]> wrote:
>>
>> Of course I could give more information without additional request. Sorry
>> for
>> that, but it was really late in the night...
>>
>> There is a simple solution for me to prevent this error: Don't use "<"
>> and/or ">" within names, surnames, ...
>>
>> But I think, there should be a warning inside Gramps if one uses such
>> special characters for some values.
>>
>> After removing all "<" and/or ">" within names the report runs to a
>> result.
>> But I got a lot of warnings like:
>> "...
>> Unknown event type: Residence
>> Unknown event type: Occupation
>> Unknown event type: Religion
>> Unknown event type: Occupation
>> Unknown event type: Residence
>> Unknown event type: Religion
>> Unknown event type: Occupation
>> Unknown event type: Occupation
>> Unknown event type: Religion
>> ..."
>>
>> As result of the report I always get a complete list of all person in my
>> database. That's all.
>> No influence of any selected center person.
>>
>> Question: Is there any where a description for all parameters?
>> It's difficult for me to understand Option S, O, F, ...
>>
>> -Helge
>>
>> PS: Merry Christmas to all. I'm fare from my computer for the next few
>> hours...
>> --
>> View this message in context:
>> http://gramps.1791082.n4.nabble.com/DescendantsLines-plugin-tp3162328p3163176.html
>> Sent from the GRAMPS - Dev mailing list archive at Nabble.com.
>>
>> ------------------------------------------------------------------------------
>> Learn how Oracle Real Application Clusters (RAC) One Node allows
>> customers
>> to consolidate database storage, standardize their database environment,
>> and,
>> should the need arise, upgrade to a full multi-node Oracle RAC database
>> without downtime or disruption
>> http://p.sf.net/sfu/oracle-sfdevnl
>> _______________________________________________
>> Gramps-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>>
>

Helge@Gramps

Re: DescendantsLines plugin

In reply to this post by lcc .

Hi,

better reading help (me) some time: For the moment the real report is the $GRAMPSHOME/DescendantsLines.png not the report selected by within the dialogue.
So I assume that there is no usage of option S, O, F, ... for the moment.

Here are two further findings:
1. Families having a father and children only (no value for the mother; I didn't check if the same happens for families having a mother and children only but no father)
see example: test_data01.gramps results in a graph without the children:

If you add a wife (e. .g. "[unknown Family], [unknown]"; see test_data02.gramps) ) you will get this complete result:

2. If you look at the result image you'll see: the last pixel column of each secondary line of each entry is wrong coloured (red instead black)

-Helge

lcc .

Re: DescendantsLines plugin

Hi Helge,

Thanks for the interest. I had just fixed the problem you noticed
about families with a single
partner. Please try the latest version from svn. I also added some
information to the wiki page,
http://www.gramps-project.org/wiki/index.php?title=DescendantsLines ,
and a new example which illustrates families with a single partner.

Regarding the options, they're there and seem to be relevant, but we
still don't know exactly what they're for, since we didn't write the
original script code which is actually drawing the tree. They seem to
be related to the spacing of the tree, among other things maybe.

The pixel problem should be checked sometime, will take not on the wiki.

lcc

On 12/26/10, Helge@Gramps <[hidden email]> wrote:

>
> Hi,
>
> better reading help (me) some time: For the moment the real report is the
> $GRAMPSHOME/DescendantsLines.png not the report selected by within the
> dialogue.
> So I assume that there is no usage of option S, O, F, ... for the moment.
>
> Here are two further findings:
> 1. Families having a father and children only (no value for the mother; I
> didn't check if the same happens for families having a mother and children
> only but no father)
> see example:
> http://gramps.1791082.n4.nabble.com/file/n3164392/test_data01.gramps
> test_data01.gramps results in a graph without the children:
> http://gramps.1791082.n4.nabble.com/file/n3164392/DescendantsLines01.png
> If you add a wife (e. .g. "[unknown Family], [unknown]"; see
> http://gramps.1791082.n4.nabble.com/file/n3164392/test_data02.gramps
> test_data02.gramps ) ) you will get this complete result:
> http://gramps.1791082.n4.nabble.com/file/n3164392/DescendantsLines02.png
>
> 2. If you look at the result image you'll see: the last pixel column of each
> secondary line of each entry is wrong coloured (red instead black)
>
> -Helge
>
>
>
> --
> View this message in context:
> http://gramps.1791082.n4.nabble.com/DescendantsLines-plugin-tp3162328p3164392.html
> Sent from the GRAMPS - Dev mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
> to consolidate database storage, standardize their database environment,
> and,
> should the need arise, upgrade to a full multi-node Oracle RAC database
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Gramps-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>

Helge@Gramps

Re: DescendantsLines plugin

Hi,

nice solution for families having a single partner.

So far I played with all report parameters I didn't found any influence for the resulting graph.
-Helge

jerome

Re: DescendantsLines plugin

Hi,

> So far I played with all report parameters I didn't found any influence for
> the resulting graph.

You need to play with hardcoded parameters or to run the standalone
script, because fields are not yet linked with code ... I guess pad
values is for adding spaces, F is for Father, S for Spouse ?

Jérôme

Helge@Gramps a écrit :
> Hi,
>
> nice solution for families having a single partner.
>
> So far I played with all report parameters I didn't found any influence for
> the resulting graph.
> -Helge

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel