|
|
|
Famous Writer
 
 
Group: Customers
Last Login: 8/24/2008 2:00:00 PM
GenoPro Version: 2.0.1.5
Posts: 230,
Visits: 3,758
|
|
| When trying to watch the entire timeline of a large report, under the "Family Subtree Timelines", the IE6 is "Not responding". After 10 minuets of waitnig for the bowser to be responding, I've closed it. The GNO I'm using has about 1000 names. I'm using: P4D2.88Mhz 1024MB, XP, IE6
|
|
|
|
|
Famous Writer
Group: Customers
Last Login: Today @ 6:06:46 PM
GenoPro Version: 2.0.1.4
Posts: 372,
Visits: 2,862
|
|
| I can not recommend strongly enough the use of smaller Genomaps when using Genopro. The Autoarrange works better, the Reporting works better, the entire program benefits by the use of smaller Genomaps. The overall result by splitting my Database of over 9000 members is enhanced greatly by creating Family groups of about 20 to 30 people, allows far better manipulation of the data, and a better result from the Report Generator. And to see 1000 timelines on a single page would render them unreadable anyway.
Poolzone a mere cog in a revolution
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 8:17:12 PM
GenoPro Version: 2.0.1.6
Posts: 3,431,
Visits: 14,266
|
|
beraha (4/20/2007)
When trying to watch the entire timeline of a large report, under the "Family Subtree Timelines", the IE6 is "Not responding".The timeline is done in JavaScript and is slow when displaying thousand of entries, making the browser appear as frozen. After 10 minuets of waitnig for the bowser to be responding, I've closed it. I suspect the timeline code is O(n2), meaning if you double the number of entries, you quadruple the computation time. If you have 1000 names, then the computation time will be 10,000 longer than you have only 10 names in your GenoMap. The GNO I'm using has about 1000 names. The timeline code should be revised to limit the number of entries in case a GenoMap has too many entries. I will ask Ron to take a look at this, to make sure the browser response time are reasonable. I'm using: P4D2.88Mhz 1024MB, XP, IE6 You have a great machine configuration. The timeline should be fast on your machine - 10 seconds waiting for rendering a timeline should be the absolute maximum.
|
|
|
|
|
Famous Writer
Group: Customers
Last Login: 8/24/2008 2:00:00 PM
GenoPro Version: 2.0.1.5
Posts: 230,
Visits: 3,758
|
|
The timeline is done in JavaScript and is slow when displaying thousand of entries, making the browser appear as frozen. Maybe the entire "Timeline processing", should be done "just once" during the creation of the report, so the HTML files will contain just the output. It means that the browser won't have to process the "timeline" each time. It's much faster. Doesn't it?
|
|
|
|
|
Grand Master
Group: Customers
Last Login: Today @ 5:34:09 PM
GenoPro Version: 2.0.1.6
Posts: 1,084,
Visits: 4,967
|
|
beraha (4/21/2007)
Maybe the entire "Timeline processing", should be done "just once" during the creation of the report, so the HTML files will contain just the output. It means that the browser won't have to process the "timeline" each time. It's much faster. Doesn't it?
The timeline is dynamic, creating the required Html code 'on the fly' as the user scrolls the timeline. I have exploited this fact by modifying the code to allow the timeline to be expanded and contracted or repainted with/without duration bars. It is not possible to create it 'just once'. The code used is an open source javascript written by individuals at the Massachusetts Institute of Technology and cannot easily be changed to improve performance. My advice is to limit your genomaps to around 100-150 individuals, or ideally ~50 individuals. You can create an overview GenoMap linking to all the subsiduary GenoMaps via hyperlinks. You also have the option of turning off the Timeline feature if you want to keep large genograms for other reasons (to do this create a Document Custom Tag named Timelines and set value to N)Maybe I will add a check in the Report Generator to warn users if a Timeline contains more than say 150 events, indicating a potentially slow response.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|