Re: [PyOpenGL-Users] PyOpenGL Deprecation & New Methods

[Mike C. F. <mcf...@vr...>]

Greg Ewing wrote:
> Mike C. Fletcher wrote:
>   
>> OpenGL is deprecating this
>> functionality because for the broader market (read C programmers) it is
>> of little or no use.
>>     
>
> Yes, it's understandable from that point of view. It's just a
> bit disappointing that they're ignoring the interpreted language
> community.
>
>   
>> it's close to the same amount of work as creating a scenegraph engine
>> that does what you want with direct C-level calls at native speed...
>> which can be as flexible and optimized as you need for your particular
>> rendering task
>>     
>
> But making it optimised for your particular rendering task means
> writing a new scenegraph engine for each application. Whereas a
> display list is a very simple and general mechanism that can be
> reused for many applications.
>   
Or, and really, IMO, this is the thing that needs to happen; certain
interpreted languages (i.e. Python) need to get off their posteriors and
start producing near-native speeds for this kind of task.  PyPy had some
interesting code a year or two ago that could use ctypes type
declarations to specialize code-paths for serious performance wins. 
Making that more general and available in a production-ready Python
would be my preferred approach to the problem :) .  The various
Javascript VMs have shown that dynamism can be optimized... it just
takes some non-trivial work at the interpreter level.

Have fun,
Mike

-- 
________________________________________________
  Mike C. Fletcher
  Designer, VR Plumber, Coder
  http://www.vrplumber.com
  http://blog.vrplumber.com