GenoPro Support Forum

I'll be glad to.

Here is a simple and small example:

http://familytrees.genopro.com/beraha/test-root/default.htm

Maybe it's not an elegant solution, But it works !!!

You have to change the "Script.js" as I said before, on your reports skin

changed "top." with "parent." in the "script.js" file using  "CTRL-H" and make all the replacements

Also - you have to create a new skin like  "Root-skin" and change the file "default.htm" by deleting most of it, and adding just a few lines

add a new file to your root-skin folder- "Top.htm"

Add another new file to your "Root-skin" Folder - "under.htm"

And publish a Blank GNO file using that new Root skin.

Remember that your reports (i.e - Test1 & Test2), and also your "Root report" should use a skin with the updated script.js

Then you have to type in your Internet-Explorer the link to your "Root Report"

That's it.

 

Edited: Tuesday, December 5, 2006 by beraha

I think I've found something.

I've changed "top." with "parent." in the "script.js" file using  "CTRL-H" and made all the replacements, and it seems to open now the "popups windows"

I hope I did nothing wrong.

Edited: Monday, December 4, 2006 by beraha

I have resolved this issue in the main.  Please see the following example at http://familytrees.genopro.com/poolzone/test6/new1.html

I am unable in the next couple of days to further this concept, but as you will see on my example above, the Genopro report is working properly within the frame of the page New1.html.  It needs only for you to install this within your own web page in a similar manner and work the report selection. I have not tested it from a remote FTP site, however I do not envisage that this will be an issue.

It appears there is no issue with Genopro's English Narrative Report, merely the way we introduce it into the frame.

Poolzone  a mere cog in a revolution

Thank you for your suggestion.

It seems that we have no other choice but to wait until after the release of Ver2,  and only then, maybe Ron will find a solution for the cases of an "External Parent frames".

In my point of view, the main advantage of this method, is that I can configure my "parent frames" as I like on my own website, and still make links to all the reports which are located on Genopro server. It's much more faster to update a report from genopro itself, rather than use a standard FTP.

Even when genopro will have an FTP access, so we'll be able to upload our entire website to Gonopro's servers, We'll still need a solution for this issue of the "External Parent frames" or of the "External top Frame".

I wonder When Genopro will start to work on Beta3 :::. Maybe then they could implement this feature.

 

Edited: Sunday, December 3, 2006 by beraha

I know you want to achieve this within your frame, however in the interim, it is very easy to direct users to different language versions of your report, or different families in the way that the following example moves between Test2 and Test4.   Just click on Link to Test? on either report.

http://familytrees.genopro.com/poolzone/test4/default.htm 

You could also include an icon on each tree to redirect readers back to your main Web site.

Poolzone  a mere cog in a revolution

I afraid the problem may be too deeply rooted to be easily fixed. My initial findings are:

Firstly your top frame is on a different web site to your GenoPro report, hence permission errors are generated when the GenoPro Report tries to change the title of the browser window. You can avoid this by publishing your GenoPro Report to the same web site as your top frame.

Secondly the report's javascript uses its top frame (default.htm) to store some variables that are used in other frames and the script refers to them as 'top.<variable>'. You will either need to declare these variables in a script in your top frame or change the GenoPro Report's script to take account of the changed hierarchy.

I have not reviewed all the javascript used in the reports. There may well be other places where the script references the 'top' frame via javascript's built-in 'top' object. You will need to examine the javascript closely for references to 'top' and change as appropriate.

There is also the issue identified by poolzone, i.e. clicking 'home' resets the windows URL to the the report's 'default.htm' page.

I agree a solution to this issue will be useful to others who wish to publish their trees in this way. Unfortunately at present I can see no simple fix.

If you do arrive at a solution please let us know here!

The scripting does not work under the new 'parent' frame. If 'home' is selected the parent frame is escaped and all works well. 

This is something in the report writer that Ron may be able to correct.

Poolzone  a mere cog in a revolution