jsRocket
category: code [glöplog]
mog: Huh, did my websocket-branch break compatibility with the C++ code? I didn't intend to...
Well, it doesn't work without websocket - thus the exe can't be used with the cpp example, or am I off track there?
And for the example demo link from the previous side:
3ln - Feliz Navis ASD
:)
And for the example demo link from the previous side:
3ln - Feliz Navis ASD
:)
mog: The intention of the code on the websocket branch is to add support for WebSocket without removing support for normal sockets. So at least in theory, the editor that you built should be able to speak to both JavaScript and C/C++ clients. But I didn't actually test that the C/C++ clients can still connect. The websocket-hack branch were less helpful to C/C++ clients, though :P
Oh! That's even cooler then! :D
Turns out, I had slightly broken the non-websocket code-path. Pushed out a fix, and considering taking this upstream soon.
Damn. And here I was watching the Excess Dropbox coming to life was the early signs of a new demo ;)
Good job guys.
This is awesomeness, thanks guys!
Hmmm -- all was going wonderfully; with mog's jsRocket-RocketWebsocket and kusma's rocket-work-websocket I found myself in a veritable nirvana of synchronicity and was merrily hacking away on some manner of glorious Rocket-enriched scene management framework when SUDDENLY!
I chanced to look upon the window, and spied a large barn owl sitting on the windowsill gazing beadily back at me. At least, I think it was a barn owl. I'm not an owl expert.
"What the fuck!" thought I, when the awkward silence was broken by the owl: "Dude -- You should probably try this in Chrome".
Aghast, I turned to Chrome and loaded the prod; Chrome said no!
For the threeJS_Cube example, for instance:
XMLHttpRequest cannot load file:///D:/Code/jsRocket-RocketWebsocket/jsRocket-RocketWebsocket/example/threeJS_Cube/cube.rocket. Cross origin requests are only supported for HTTP.
Heart racing, I turned back to the window. The owl was gone.
Any thoughts?
I chanced to look upon the window, and spied a large barn owl sitting on the windowsill gazing beadily back at me. At least, I think it was a barn owl. I'm not an owl expert.
"What the fuck!" thought I, when the awkward silence was broken by the owl: "Dude -- You should probably try this in Chrome".
Aghast, I turned to Chrome and loaded the prod; Chrome said no!
For the threeJS_Cube example, for instance:
XMLHttpRequest cannot load file:///D:/Code/jsRocket-RocketWebsocket/jsRocket-RocketWebsocket/example/threeJS_Cube/cube.rocket. Cross origin requests are only supported for HTTP.
Heart racing, I turned back to the window. The owl was gone.
Any thoughts?
That darn owl should have told you to either run the stuff on your localhost, or feed --allow-file-access-from-files as parameter to Chrome.
For the latter one it's crucial to close all Chromes before, otherwise two owls may appear :)
The cause for why this is necessary, imagine any website being able to read stuff from your harddisk - jupp, would suck :)
For the latter one it's crucial to close all Chromes before, otherwise two owls may appear :)
The cause for why this is necessary, imagine any website being able to read stuff from your harddisk - jupp, would suck :)
Mog, thanks very much for the ornithological clarification :)
Quote:
Hmmm -- all was going wonderfully; with mog's jsRocket-RocketWebsocket and kusma's rocket-work-websocket I found myself in a veritable nirvana of synchronicity and was merrily hacking away on some manner of glorious Rocket-enriched scene management framework when SUDDENLY!
I chanced to look upon the window, and spied a large barn owl sitting on the windowsill gazing beadily back at me. At least, I think it was a barn owl. I'm not an owl expert.
"What the fuck!" thought I, when the awkward silence was broken by the owl: "Dude -- You should probably try this in Chrome".
Aghast, I turned to Chrome and loaded the prod; Chrome said no!
For the threeJS_Cube example, for instance:
XMLHttpRequest cannot load file:///D:/Code/jsRocket-RocketWebsocket/jsRocket-RocketWebsocket/example/threeJ S_Cube/cube.rocket. Cross origin requests are only supported for HTTP.
Heart racing, I turned back to the window. The owl was gone.
Any thoughts?
Yes. You win at life with that post right there :)
(no Wacom at work though ;_;)
Another error that bugged me for quite a while until I put some thought into, is the Rocket limbo between two rows when one moves quickly in Rocket.
You usually render when you get a row update from Rocket, though you also want rocket to know where you are in the demo when you play it. So one usually updates the row towards Rocket in render as well.
However if you send the row update while not playing the demo, you might end up in the row limbo. The problem seems to be JS not giving accurate enough position data on the audio, so you send row 4 on getting row 5 from Rocket - and that keeps going on forever, until you manage to slip out by hitting spacebar like a mad man in Rocket.
The current fix is to only update the row towards Rocket when playing the demo.
The Rocket spasm fix as source
(This isn't a Rocket error, but might be something I can address in jsRocket - if I bring more thought into it O_o)
You usually render when you get a row update from Rocket, though you also want rocket to know where you are in the demo when you play it. So one usually updates the row towards Rocket in render as well.
However if you send the row update while not playing the demo, you might end up in the row limbo. The problem seems to be JS not giving accurate enough position data on the audio, so you send row 4 on getting row 5 from Rocket - and that keeps going on forever, until you manage to slip out by hitting spacebar like a mad man in Rocket.
The current fix is to only update the row towards Rocket when playing the demo.
The Rocket spasm fix as source
(This isn't a Rocket error, but might be something I can address in jsRocket - if I bring more thought into it O_o)
Just thought I'd let you know that I've *finally* gotten my act together and pushed out websocket support to the master-branch.
Cool! =)
And now I've finally gotten my act together, and merged jsRocket into the main GNU Rocket repo! Thanks a lot for the great work, mog!
fuck yea kusma :)
<3
Also there's now a list of alternate ports!
Also there's now a list of alternate ports!
wooot :)
cool!
