PHPGEDVIEW and GRAMPS (online)

[Duncan Lithgow]

Over on the GRAMPS list we are once again talking about how GRAMPS can be part of the online world and offer something like what this project does but using the GRAMPS XML format.

So please take a look, have your say, let's see how we can work together to make online genealogy even better and easier!

For threaded discussion see http://www.nabble.com/GRAMPS---Dev-f1186.html and especially (at the moment) http://www.nabble.com/GRAMPS-server-mode-tt24775835.html and others.

[Lester Caine]

I was going to reply on the GRAMPS thread, but I suspect that they are not ready for a move to PHP.
Coming from the other side, I see no problem in replacing the PDO layer with a GRAMPS interface, but I do get the impressinon that GRAMPS still needs a database layer to provide the indexing? So that the real problem is replacing GEDCOM records with GRAMPS ones while retaining the existing index structure anyway?
I did look at GRAMPS, but adding another development language switched me off straight away ;)

[Wes Groleau]

I went through the tedious but necessary process:
I registered, clicked the confirmation link in the e-mail,
was told I was OK, went back to the forum, logged in
(which worked), opened the post of interest, and replied. 
Got a bounce saying only members are allowed to post.

So, in case anyone  cares, here's that reply:
-----------------
Doug Blank-2 wrote:
If you have used phpgedview, two things are apparent: it is closely tied
to
GEDCOM, and is written in PHP. Ok, that might be obvious from the name :)
But, my point is that GRAMPS nicely hides and abstracts the GEDCOM issues.
phpgedcom attempts to make the GEDCOM visible. And PHP and Python
programmers have two different toolboxes.

....

I see the gramps webapp as an evolutionary step of the current code and
team
to the web, not a completely revolutionary project. When looked at that
way,
phpgedcom and gramps occupy their own distinct spaces.

Your comments make sense, and two independent projects could give each other
valuable ideas for features.  For example, in a collaborative online system,
I would _definitely_ encourage a close look at PhpGedView's "relationship
privacy"
feature.

I would also encourage actively discussing with the PhpGedView folks some
sort of
standard interface for inter-DB references and queries.  Wouldn't it be cool
if you
could get a few generations down a branch that you aren't interested in, and
put a link to another DB in a format you could trust to not be a dead link
the
day after tomorrow?
---------
PGV could learn from them too--we could learn to dump this SourceForge forum for something decent.

I think that forum's thread view sucks.  But at least they HAVE a thread view that's chronologicaly tolerable--we don't.  I also note they don't have light gray text on a beige background.  Somebody at SourceForge trying to persuade us old folks to get lost?  And what's with this asinine five-line box to post into?  I know some of us (mea culpa) are too verbose, but five lines is ridiculous.