Search found 4 matches

by Meekrat
Thu Aug 27, 2009 7:42 pm
Forum: Wolfire
Topic: Awesomium (technical)
Replies: 5
Views: 3439

Re: Awesomium (technical)

by Meekrat
Thu Aug 27, 2009 6:14 pm
Forum: Wolfire
Topic: Awesomium (technical)
Replies: 5
Views: 3439

Re: Awesomium (technical)

Ah, there is some wrapper code that is eval'd into the JavaScript context. For instance, Camera.allowCollision is actually function (){ Client.__ConsoleFunc_Camera_allowCollision.apply(Client, arguments); } Hmm... Got it. And had I done Camera.allowCollision.toString(), I would have seen that. Are ...
by Meekrat
Thu Aug 27, 2009 12:55 pm
Forum: Wolfire
Topic: Awesomium (technical)
Replies: 5
Views: 3439

Re: Awesomium (technical)

We do actually use the ClientObject. :) Every command that communicates with the Phoenix Engine uses Client.something While there is plenty of use of Client.* code, I'm also seeing Camera.setFOV(..) instead of Client.setCameraFOV(), Graphics.setFullscreen(..) instead of Client.setFullscreen(..), an...
by Meekrat
Wed Aug 26, 2009 7:33 pm
Forum: Wolfire
Topic: Awesomium (technical)
Replies: 5
Views: 3439

Awesomium (technical)

Hey Guys, great work. You're blog posts have turned my team onto Awesomium. We were hoping you might spend a little time talk about what you've done, either on the blog or here. In particular, I wonder three things: * How did you work around the silly ClientObject for your Javascript binding? When p...