|
By honyk - Tuesday, January 5, 2016
|
If you store family trees in separate GenoPro files and you need to create a report across all of them, the only solution so far is to merge all files into a single one. If your tree is quite large, covering various families and from various reasons such an operation is not an option, you can still generate reports using my web app, which merges individual files virtually. |
|
By GenoProSupport - Tuesday, January 12, 2016
|
|
I would rather have the opposite: have all your family tree data into a single .gno file, and generate a report for a specific a GenoMap. By the way, we are building GenoProX from scratch and our new file format will be JSON. If you want, we could have a Skype conversation and discuss what data format would be better for someone like you who built tools for GenoPro.
|
|
By honyk - Tuesday, January 12, 2016
|
This report is just one time job for one particular case. I made it with mind it could be reused for various styles of ancestor tree (e.g. HTML table), but not as general tool for other reports (e.g. descendant tree), which could be problematic in case of cyclic references. My family tree is quite large, initially started as several separate files which I don't plan to merge in foreseeable future as those files contain 200-500 individuals split into many genomaps which itself is quite difficult to manage. I knew there is GenoPro XML format available so I employed my XSLT skills. But it was clear that XSLT 2.0 template requiring a specific XSLT processor and running the transformation via commandline would be a blocker for majority of users. So I wrapped all this into a simple web app. It can be used even for a single GNO file. Just upload it, select a base individual and particular chart will be generated. It cannot be limited to a specific genomap though.
|
|
By powery - Tuesday, January 12, 2016
|
Dobrá vychytávka 
|
|