Postponed
Project:
Family Tree
Version:
4.7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
11 May 2006 at 20:55 UTC
Updated:
2 Nov 2007 at 02:04 UTC
the CiviCRM is a complete tools to record all personnal information. It 's a very nice module. Would it be possible to use your beautifull work to be compatible with civiCRM (For your information there is definable links between persons, API to retrieve DATA, ...).
What do you think ?
Comments
Comment #1
jfriesen commentedI'm very much in favour of this... CiviCRM has the strong community and development support, and there's only a few functions that it can't do (or I can't find it to do)...
- export a visual tree structure for families
- import/export to GEDCOM (I think that's the standard format)
I'd love to see FAMILY as a modular add-on to CiviCRM, if only because CiviCRM already does so many useful things. Wouldn't that make this project much more attainable?
Comment #2
pyutaros commentedMarking this as fixed. There seems to have been no interest from the CivicRM community to take this on and it isn't a priority for any of the current developers.
Comment #3
seth.e.shaw commentedI think this is a "perhaps someday, if we get around to it, or someone has the drive to do it themselves." I think this feature request would be best written into CiviCRM. Will we have an API that other modules to use but I don't think we can take the time to adapt Family to every other module out there. There is just too many Family module specific things to do. Come to think of it, my plans to integrate GoogleMaps with locations (places) would probably be best put in a separate module.
Comment #4
pyutaros commentedGood point. I'll change it to postponed to preserve the request. I also think things like GoogleMaps Location might be better as a sub module, much like the image module has various sub modules. I'm debating making my event nodes a sub module in the same fashion.