UltraVox:
Obviously, it works. There is no reason why it does not work : the page is almost empty.
1) The fact that it works has nothing to do with "how empty the page is".
2) The objective here was to try and figure out "where it stops working for you" ... we can surmise from your response that ...
- NeoBook's
RefreshObject command works in your environment (Windows 8 and IE 11) ... i.e. NeoBook is able to tell IE 11 to Refresh the contents ... and IE 11 is correctly doing it using the updated file contents on disk.
- the problem lies with "the servicing of the html/javascript in the changed file".
Firefox ...
- shows just a black canvas for the first one
- tells me "my video card does not support WebGL" for the second one
Chrome renders both ... perhaps my slow computer, perhaps due to lack of capable video card, but it took a long time for the animation to show up.
Three.js is just a JavaScript Library. But, If there is a SkyBox, the RefreshObject does not work in NB. There is no reason for that.
Debugging in an environment with 3 different technologies (NeoBook, IE 11, your javascript library) requires you to carry out your investigation "one step at a time" ... in a methodical/logical manner.
So, the next step would be to ...
a) have two files on disk ... one with the (scene.add(floor);) command ... the other with the (alert(12345);) command ... composed with notepad++
b) instead of doing a
FileWrite from NeoBook, just change the name of the file associated with the WebBrowser object
... tell us if the rendering was as expected.
And it's not normal to lose between 40 FPS with the first experience (IE locally), and the second (and same) experience, but with NB.
I do not have expertise with video cards ... but this could perhaps be due to ...
- the video card NOT being used for rendering when going through NeoBook
- an automatic dumbing down of the FPS because of the inability to handle the higher load