Hi
On 02/01/13 02:48, Stephen Woodbridge wrote:
Hi John,
Yes, I would love to get that and I'm willing to share my code once I
have time to fix the most critical issues.
I agree this code should be shared. But read on...
Maybe Paul would like to create a "contrib" directory in the repository
that could be used to make code like this available. I guess we could
If by repository you mean the Gedcom.pm distro, that would bloat that
particular distro, which is already 116 KB.
Ideally such code would be made CPAN-ready before release, without - of
course - forcing the author to make it production-ready.
I can help with that. I've written a tool for my own use which lists
pre-reqs, so creating Build.PL and Makefile.PL is quite easy, just a bit
of editing. Still, the code need some sort of docmentation, which is the
author's job.
As for a namespace, there is a long history in Perl (i.e. on CPAN) to
add an X to the primary module's name, giving GedcomX::* as the prefix
for all such modules. There's no doubt in my mind this is the best course.
And since I've recently become one of the admins for CPAN itself, I do
take module naming very seriously.
Of course this is a bit confusing because we've just been discussing
GEDCOM X. Sigh.
So - what to do?
Here's what I suggest: Last year I registered the new namespace
Genealogy::*, so:
1) For modules using, or already based on, Gedcom.pm, I'd call them
GedcomX::*.
2) For brand new modules, e.g. implementing GEDCOM X, or not using
Gedcom.pm, e.g. me new parser we discussed on this list last year, I'd
call them Genealogy::* or (for GEDCOM X) Genealogy::GedcomX::*.
That way, we'd keep separate things separate.
all make public repos on github if we have code to contribute but I
think that makes it harder to find it. And/or we could create wiki
page(s) that describes these contrib items and how to use them.
Definitely. We'll need a road-map to help orient people to these
modules, along the lines of:
http://savage.net.au/Module-reviews.html
Anyway, please send your code when you get a chance. It might be a month
+- before I get to look at it and give it a try.
Glad to hear it.
Thanks,
-Steve
On 1/1/2013 10:37 AM, John Washburn wrote:
Dear Stephen:
I have a perl program that walks the HTML pages of e-FamilyTree.net and
pipes it out to a GEDCOM file. It is also interruptible in that you
can run
the program for a while, stop it and upon restart it will pick up
where the
search left off.
It uses the HTML:Tree builder and the wonderful look-down functionality
mentioned by Ron. It also used Date::Manip quite heavily.
I would be happy to zip up the code and send the archive to you if you
are
interested. The code is a bit bloated because the code grew over time
and I
had to add special cases for some of the errors in the e-familynet HTML
structure and to implement the 1-generation look ahead.
-----Original Message-----
From: Ron Savage [mailto:r...@savage.net.au]
Sent: Saturday, December 29, 2012 10:06 PM
To: perl-gedcom@perl.org
Subject: Re: Gedcom.pm 1.17 released
Hi Stephen
On 30/12/12 11:03, Stephen Woodbridge wrote:
On 12/29/2012 5:26 PM, Paul Johnson wrote:
What I noticed was that the data way nicely tag in the HTML so I am
writing a parser to read the HTML can generate a Gedcom file. I have
the basics working, but I have to do more work on it to fix bugs and
collect more of the data than I current am. I'm side tracked with work
at the moment so it is on hold. When I'm done it will have generated a
40K+ person Gedcom file. This should be able able to create a gedcom
from any "Second Site" generated website assuming it is similar to the
link above. Or you can ask the site owner for a copy of the gedcom :),
but this seemed like a worth challenge at the time.
Are you using HTML::TreeBuilder and the v-e-r-y nice look_down() method?
--
Ron Savage
http://savage.net.au/
Ph: 0421 920 622
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.2805 / Virus Database: 2637/5997 - Release Date: 12/30/12
--
Ron Savage
http://savage.net.au/
Ph: 0421 920 622
