double051

But it is. This post by Nathan de Vries [0] shows how you can hack the UIWebView to enable WebGL contexts in your iOS apps. You have to get a little more creative these days (the compiler has gotten stricter about private types and functions), but all it takes is something like this:

    -(void)setWebGLEnabled:(BOOL)enableWebGL forWebView:(UIWebView *)uiWebView
    {
        id webDocumentView = [uiWebView performSelector:@selector(_browserView)];
        id backingWebView = [webDocumentView performSelector:@selector(webView)];
        [backingWebView performSelector:@selector(_setWebGLEnabled:)
                             withObject:[NSNumber numberWithBool:enableWebGL]];
    }

[0] http://atnan.com/blog/2011/11/03/enabling-and-using-webgl-on...

Should start working after a refresh.

Maybe that's the problem? I wear mine in moderation and I've never had any pain problems with it on.

Two months later, the certs were expiring soon and we changed our configuration to something Android liked by default. The bad news was that our production Android app rejected the new configuration and only wanted to accept the current certs.

We ended up quickly shipping a hotfix that accepted the current and upcoming configuration a few days before the certs expired. There technically wasn't any 'downtime' as long as users updated the app, but this all took place right before 'holiday vacations', and the QA team had to test the fix while all the devs were away.

BTW, this is John from B&&C.

http://en.wikipedia.org/wiki/Geostationary_orbit

Missed triggers no more!

Trying again, but now I'm seeing this: "Try again. We couldn't find you a ticket, but there still might be tickets left!"

Github repo: https://github.com/mrdoob/three.js/

Examples: http://mrdoob.github.com/three.js/

The accounts they used weren't fake, they were just the two guys building a site with a lot of test accounts.