|
Post by lcurtisboyle on Jan 23, 2008 0:36:48 GMT -5
First, a question: On the descendants list, is there a way to get it to list more than just the first and last sub-field for the birth and death place? That is fine if I have the first part as the city, and the last as the country (although having the state/province would be nice), but in some cases where I have more specific information (ex. the hospital someone was born at), it will list "so-and-so Hospital,Canada" 2) I think there is a bug when listing spouses (those proceeded by the '+' sign)... it seems to be listing the birth/death dates and places twice. 3) The one I listed for our family (and is now on my website: boylephotos.lcurtisboyle.com/fulltree/names.htm) has over 12,000 files (which is fine by itself), but if I do some minor corrections to a few people and regenerate it, does it keep the exact naming convention, so that I can just re-upload the changed sub-pages, or do I have to reupload the whole thing again? Thanks for your time, and a great program!
|
|
|
Post by Howard Metcalfe on Jan 23, 2008 19:38:52 GMT -5
First, a question: On the descendants list, is there a way to get it to list more than just the first and last sub-field for the birth and death place? That is fine if I have the first part as the city, and the last as the country (although having the state/province would be nice), but in some cases where I have more specific information (ex. the hospital someone was born at), it will list "so-and-so Hospital,Canada" 2) I think there is a bug when listing spouses (those proceeded by the '+' sign)... it seems to be listing the birth/death dates and places twice. 3) The one I listed for our family (and is now on my website: boylephotos.lcurtisboyle.com/fulltree/names.htm) has over 12,000 files (which is fine by itself), but if I do some minor corrections to a few people and regenerate it, does it keep the exact naming convention, so that I can just re-upload the changed sub-pages, or do I have to reupload the whole thing again? Thanks for your time, and a great program! Hi, At first I thought you were referring to the standalone HTML descendants listing, but after checking your site I understand you were generating an HTML web site. I could change to generating the full place names in the descendents list. I tried to keep it short so the page wouldn't be too wide. The code is common to HTML pedigrees so such a change would appear there too. The next version of PAWriter is due out at the end of next week, jury duty permitting. If you think this is really important, let me know, and I will consider making the change in the subsequent version, and let you beta test it. Yes, I noticed that spouses which have descendants do have their birth and death info duplicated. I will have to fix that at the same time. Regenerating the web site will keep the same file names, which are based on the RINs and FRINs. If the interconnections are not changed, you should be able to just upload just the changed files. I haven't tried this but if you do please let me know if it's successful. Best, Howard
|
|
|
Post by lcurtisboyle on Jan 24, 2008 11:39:03 GMT -5
Sure, I could test the expanded locations on the HTML generation. I was thinking a checkbox to turn on/off the full location vs. what you have now, as some people may just be entering city/country, and would not want the "wider" format. Good news to here about the HTML filenames being based on RIN/FRIN - the changes I have to do shortly to the page you saw will be a test of that, and the changes themselves are just spelling mistakes, etc. (no changes of relationships between people). I would assume that if I do have to reassign children between wives (for example), that the RIN would stay the same (and thusly, all individual RIN html files would stay the same), and just the specific FRIN html files would change. A nice option (in the future... it would be a bit more difficult to implement) would be to have PAWriter be able to compare the copy it is about to write out with the copy last written out (since the html filenames and contents should match if nothing has affected that particular record), and skip it is the same; only re-writing the changed files. This way,one could sort by Date modified and just upload the changed files easily, rather than re-upload the whole site. As it stands, I may have to write a batch file of some sort to do file compares between the original and the new files (saved into 2 separate folders) to figure out which ones need to be updated.
|
|
|
Post by Howard Metcalfe on Jan 24, 2008 14:19:05 GMT -5
Sure, I could test the expanded locations on the HTML generation. I was thinking a checkbox to turn on/off the full location vs. what you have now, as some people may just be entering city/country, and would not want the "wider" format. Good news to here about the HTML filenames being based on RIN/FRIN - the changes I have to do shortly to the page you saw will be a test of that, and the changes themselves are just spelling mistakes, etc. (no changes of relationships between people). I would assume that if I do have to reassign children between wives (for example), that the RIN would stay the same (and thusly, all individual RIN html files would stay the same), and just the specific FRIN html files would change. A nice option (in the future... it would be a bit more difficult to implement) would be to have PAWriter be able to compare the copy it is about to write out with the copy last written out (since the html filenames and contents should match if nothing has affected that particular record), and skip it is the same; only re-writing the changed files. This way,one could sort by Date modified and just upload the changed files easily, rather than re-upload the whole site. As it stands, I may have to write a batch file of some sort to do file compares between the original and the new files (saved into 2 separate folders) to figure out which ones need to be updated. Hi Curtis, As noted in an email to you, I hope to have the correction and the long place names in version 77 if it passes your beta test. I think I'll pass on the option for the short or long place names. I like just having the long place names. It's consistent with the rest of the web site files. Yes, it seems at this poiint that just rewriting changed files would be difficult, but I'll continue to think about that. Let me know if you do write a comparison program. That sounds interesting and very useful. Best, Howard
|
|