Combining Genealogy program with eZ publish?

Author Message

Terje J. Hanssen

Monday 04 April 2005 5:26:45 pm

I wonder if someone has experience with using eZ publish for genealogy applications?

Actually, I think of the possibility to combine "TNG" (The Next Generation of Genealogy Sitebuilding) with eZ publish. My project idea is to build a genealogy database with TNG/MySQL with GEDCOM import. This may next be used ot generate reports for an "eBook" authored and published with eZ publish.

The interesting thing here is that TNG looks to be based on the same LAMP-platform as eZ publish, and both generate dynamic web pages. The following links are meant as related information (not spam!):
http://lythgoes.net/genealogy/software.php
http://eogn.typepad.com/eastmans_online_genealogy/2004/06/the_next_genera.html
http://lythgoes.net/genealogy/demo.php
A couple of examples, Norwegian sites using TNG:
http://hemneslekt.net/
http://indregaard.net/

Constructive comments and suggestions are welcome,

Terje J. Hanssen

Bård Farstad

Wednesday 20 April 2005 2:41:04 am

Terje, this sounds like an exciting project. I think eZ publish will fit well with your needs. It's easy to build hierarchies and relations with eZ publish.

Would be nice to get information about the project once you start progressing with it.

--bård

Documentation: http://ez.no/doc

Terje J. Hanssen

Thursday 21 April 2005 2:12:16 am

Bård,

While the TNG license is "almost" free ($27), PhpGedView is another genealogy program that is GPL licensed. PhpGedView is similar web oriented and can typical run on LAMP or WAMP servers:
http://phpgedview.sourceforge.net/

There is also similar developed module files to integrate phpGedView with PostNuke.
http://phpgedview.sourceforge.net/modules.php

It is similar wishible to run these programs as modules under eZ publish, without the need to login extra to the genealogy programs.

Is there some kind of documentation and command examples for eZ publish how to do this?

Terje J. Hanssen

Bård Farstad

Thursday 21 April 2005 3:41:04 am

Terje,

there is information about how to write a module and how to connect to the user information in eZ publish (login handlers). There is both a tutorial on how to write a module and information on how you can write your own login handler.

You can find this under the eZ publish documentation.

--bård

Documentation: http://ez.no/doc

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 18 2025 18:33:32
Script start
Timing: Jan 18 2025 18:33:32
Module start 'layout'
Timing: Jan 18 2025 18:33:32
Module start 'content'
Timing: Jan 18 2025 18:33:32
Module end 'content'
Timing: Jan 18 2025 18:33:32
Script end

Main resources:

Total runtime0.0155 sec
Peak memory usage2,048.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0060 592.7344152.6406
Module start 'layout' 0.00600.0028 745.375039.4766
Module start 'content' 0.00880.0045 784.851693.3359
Module end 'content' 0.01330.0021 878.187534.3047
Script end 0.0154  912.4922 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002516.3631140.0002
Check MTime0.00127.8553140.0001
Mysql Total
Database connection0.00085.284210.0008
Mysqli_queries0.002717.384130.0009
Looping result0.00000.103310.0000
Template Total0.001811.510.0018
Template load0.00095.822510.0009
Template processing0.00095.622010.0009
Override
Cache load0.00064.204510.0006
General
dbfile0.00021.542480.0000
String conversion0.00000.052440.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs