By 754790 - Monday, September 1, 2014
|
Most browsers no longer use frames and so I have to ensure anyone who uses my report has the browser shipped with the report.
Will this be changed in the next version?
|
By jcmorin - Monday, September 1, 2014
|
The html report is created and maintain by Gnome; an avid user of GenoPro. While frame are unpopular; are they really not supported by a browser? What browser give you trouble?
|
By genome - Tuesday, September 2, 2014
|
Most browsers no longer use frames and so I have to ensure anyone who uses my report has the browser shipped with the report.
Browser's do not 'use' frames, they either support use of them or not. Use of frames in web sites is now deprecated by common concensus but all modern browsers AFAIK still support rendering of frames. Historically the narrative Report was developed exploiting frames and there are no plans to revise this due to the huge development effort involved. There is a possibility of other reports being developed using modern techniques and libraries e.g. HTML5, jQuery, Jointjs
Since you are shipping a browser with your report it indicates to me that maybe the problem you are having is not actually with use of frames but the 'same domain' issue that occurs when accessing 'web' pages on a local disc/usb drive using the FILE scheme rather than the web server based HTTP scheme. This occurs with Chrome and other browsers when the report files are opened locally.
The solution to this issue is to publish your report to a web server such as familytrees.genopro.com. Publish a dummy report first and then set a password on it before publishing your full report if privacy is required.
|
By powery - Tuesday, September 2, 2014
|
Another possibility is to revive this project: |