On Thu, Dec 29, 2011 at 3:04 PM, Jeffrey Van Voorst
<[email protected]> wrote:
> Ok, but my Java understanding is practically nil (other than recalling
> how annoyingly rigid it is).
that's ok, there's java2py, and a couple of other conversion
programs. that takes care of 95 to 98% of the work, leaving you to
fix the few remaining things. you should be done in a couple of days.
> I haven't actually looked into any of the translation/compiling code.
> Do I need to use PyOpenGL calls and then translate them to javascript
> as per gwtgl?
absolutely not.
> In other words, what OpenGL (if you prefer one other
> than PyOpenGL) should be used in Python land so that the opengl calls
> work (as much as possible) the same on pyjd as pyjs?
you don't.
you literally and i mean literallly use exactly the same functions.
it is *not* your problem. just make sure that there are zero JS("")
blocks.
in other words it is the browser engine's responsibility to thunk
down to opengl. it is *absolutely nothing* to do with pyopengl.
l.