Thanks a lot for your kind responses. Any response is appreciated dearly, but still I have some questions (sorry for the lengthiness – see at the end):
And please excuse me that I perhaps get your instructions – and the nice hype-file – all wrong (I openly admit: js is not my turf!).
But it seems to me, that the “Waypoint_postMessage_to_iFrame”-file is designed to load “innerframe.html” into an unique id element named “iframe” in an html-file called “parent.html”. Right?
When loading “parent.html” in a iframe on a remote page it still wont work, like this “http://raaskot.dk/raalab/ase/waypoint-iframe-raaskot/iframe_setup_01/index.html”
If I load it in a new iframe deployed on another server (with an external link) the problems still persist: the animations will only run once due to the iframe issue.
Yet my wish is (as mentioned) to display the entire hype project in a remote html-iframe (non-hype generated) maintaining the scroll effects like this example (where the hype effects is lost):
“http://raaskot.dk/raalab/ase/waypoint-iframe-raaskot/iframe_setup_02”
It should work like this non-iframe example here: “http://raaskot.dk/raalab/ase/waypoint-iframe-raaskot/iframe_setup_02/waypoint_iframe_raaskot.html”
A hype-compilation of the above: “http://raaskot.dk/raalab/ase/waypoint-iframe-raaskot/iframe_setup_02/waypoint_iframe_raaskot.zip”
Questions:
(1) Is my above linked waypoint setup suited to be modified with the functions found in the “Waypoint_postMessage_to_iFrame” – and – excuse me that this question somehow gets extensive 
– where to drop the string-blocks in Hype?
(2) Can the script (“postMessage”) used in “parent.html” also be utilized in the index.html (the one with the iframe-tag) – if you understand?
Kind regards and with thanks! 
Mikael