Thanks for the feedback Vittorino, I will try to answer the issues you have raised.vlepore (12/20/2009)
1) For the excessive number of
individuals, not always vertical lines connect all the children.
I have been aware of this issue for some time and have been waiting to see if the author of the treeview jQuery plugin would be producing updated versions. However as yet nothing is forthcoming, so I propose to evaluate alternative tree view plugin, such as dynatree to see if they perform better.
I saw this in my own tree too but I left in the duplicated branch entries for ease of use and completeness so that a line can be traced without having to follow a cross-reference. Perhaps with the rtf version an optional cross reference can be given instead, as in the original Descendants Report.
3) With more than 9-10 generations, IE hangs and fails to complete the construction of the tree, which remains incomplete without the symbols enlarge / collapse. With over 15 generations and 4000 individuals, we plant the PC
IE does seem to be much more processor intensive when rendering dynamic HTML changes than say Firefox. I have seen IE take a very long time to display such a tree, but not to stop completely. I have not as yet compared other browsers, such as Google Chrome.
I could possibly add javascript to detect the size of a tree and the browser being used and issue a prompt to say that it will be slow and Firefox should be used instead.
Would be very interesting to include in reports of all individuals, this Descendant Tree Chart, also limited to 1-2 generations, in addition to the tree ascending
This may be possible once the report code is stabilised. It would need to be converted to VBscript to be incorporated into the Narrative Report. An alternative, which I prefer, is to retain it as a separate skin but perhaps for the Narrative Report to detect presence of a Descendants Tree Chart and include a link to it.