From: Randolph B. <be...@ho...> - 2004-12-30 21:55:27
|
I've been collecting family data for some time and would like to make it available via the web such that basic information is available to all, family members see more detail, and close relatives see even more detail. This leads to some kind of authentication/authorization scheme and dynamically generated pages. Does this seem reasonable to folks? If so, I'll develop this idea further. If someone's working on it, I'll help, or I'll enjoy the results. -- Randolph Bentson be...@ho... |
From: Alex R. <sh...@al...> - 2004-12-30 22:24:34
|
On 12/30/2004 03:55:16 PM, Randolph Bentson wrote: >=20 > I've been collecting family data for some time and would like to make it > available via the web such that basic information is available to all, > family members see more detail, and close relatives see even more detail. > This leads to some kind of authentication/authorization scheme and > dynamically generated pages. Sounds pretty useful, I think many people would like to have this. > Does this seem reasonable to folks? If so, I'll develop this idea > further. If someone's working on it, I'll help, or I'll enjoy the > results. Not sure if anybody has been working on this. Looks like it is all yours to grab :-) Please feel free to ask if you need advice on gramps' internals, and to share your results/feedback! Alex --=20 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 |
From: Tim W. <tw...@re...> - 2004-12-31 09:33:49
|
On Thu, Dec 30, 2004 at 10:24:24PM +0000, Alex Roitman wrote: > On 12/30/2004 03:55:16 PM, Randolph Bentson wrote: > >=20 > > I've been collecting family data for some time and would like to make = it > > available via the web such that basic information is available to all, > > family members see more detail, and close relatives see even more detai= l. > > This leads to some kind of authentication/authorization scheme and > > dynamically generated pages. >=20 > Sounds pretty useful, I think many people would like to have this. >=20 > > Does this seem reasonable to folks? If so, I'll develop this idea > > further. If someone's working on it, I'll help, or I'll enjoy the > > results. >=20 > Not sure if anybody has been working on this. Looks like it > is all yours to grab :-) >=20 > Please feel free to ask if you need advice on gramps' internals, > and to share your results/feedback! Well, it isn't really worth re-inventing the wheel. Export to GEDCOM and import that into phpGedView: http://phpgedview.sf.net/ Tim. */ |
From: Johan V. <jvr...@sq...> - 2005-01-02 10:53:22
|
Tim Waugh <tw...@re...> writes: > Well, it isn't really worth re-inventing the wheel. Export to GEDCOM > and import that into phpGedView: > > http://phpgedview.sf.net/ Nice. Is it safe to exchange GEDCOM <-> GRAMPS and vice versa without losing information? -- Johan |
From: Don A. <don...@co...> - 2005-01-02 20:01:40
|
On Sun, 2005-01-02 at 11:53 +0100, Johan Vromans wrote: > Tim Waugh <tw...@re...> writes: > > > Well, it isn't really worth re-inventing the wheel. Export to GEDCOM > > and import that into phpGedView: > > > > http://phpgedview.sf.net/ > > Nice. > Is it safe to exchange GEDCOM <-> GRAMPS and vice versa without losing > information? > > -- Johan Exchanging does not guarantee that data won't be lost. There is information in GRAMPS that cannot be represented in standard GEDCOM (such as same-sex marriages and certain child/parent relationships). And some standard GEDCOM that we generate cannot be read by all programs (in particular, multiple names tends to cause problems). By the same token, there is some data that can be specified in standard GEDCOM that GRAMPS does not understand (such as repositories), and a lot of "custom GEDCOM" that some programs generate that is not a part of the GEDCOM specification that we cannot handle (GRAMPS will usually warn you about these when it imports data). That being said, GRAMPS is usually pretty good about reading in GEDCOM files that it creates. Don -- Don Allingham <don...@co...> |