All mainstream win32 have snake now, they just don't have any other makes
On Jul 2, 2011 8:40 AM, "chm" <devel.chm...@gmail.com> wrote:
> On 7/1/2011 10:24 AM, Kartik Thakore wrote:
>>
>> =head2 OpenGL 3.0
>> =blame kthakore, chromatic
>> =for kthakore, Chris, jtpalmer
>>
>> This comes from the following observations ( feel free to scold/correct
>> me ).
>>
>> =over
>>
>> =item Convergence to OpenGL
>>
>> SDL 1.3 is moving over to OpenGL. Having the ability to do neat things
>> with OpenGL this will help to add more performance, speed and
>> flexibility to the module.
>>
>> =item POGL still uses FreeGLUT
>>
>> POGL albeit great is getting ... old. FreeGLUT is slowing down ( SDL
>> replaces this fine and we have tests to prove it see construder. It is
>> an extra dep.
>
> FreeGLUT is the default window "provider" for POGL.
> Any GUI toolkit that supports creating OpenGL contexts
> and setting them should work fine. I'm looking into
> factoring out the GUI dependencies so that POGL works
> better with other GUI toolkits to provide the OS and
> window system support.
>
>> =item OpenGL 3.3 is a fixed target
>>
>> New OpenGL is all the way up to 4.x now. OpenGL 3.3 has been around for
>> a while and is not going to be using.
>>
>> =back
>>
>> Based on this I think we should attempt to help the POGL dev with
>> whatever he needs. I will move it to github at some point. Additionally
>> chip during my talk you mentioned some technology for doing OpenGL
>> context/display lists better. Can you mention it again chip? I seem to
>> have forgotten it.
>
> I'm not sure what the issues with context/display
> lists might be but would be interested to hear.
>
> As I see it, the top missing feature in Perl OpenGL
> is support for OpenGL versions greater than 2.x.
> Work is underway to refactor POGL to use GLEW for
> the bindings. That should improve portability and
> capability (GLEW supports pretty much all current
> OpenGL versions).
>
> The next priority for POGL is the build process
> which is hamstrung by a static probe for system
> capabilities and requires a shell and make to
> work. I would like to move detection of needed
> libraries to an Alien::Module and to Module::Build
> for POGL itself which would avoid some of the
> portability problems with win32---no shell, no
> make, no package manager. I would like to see
> POGL build on win32 platforms *without* requiring
> a MSYS or cygwin install to get things to work.
>
> Regards,
> Chris Marshall
>
>> The hope will be to make a declarative for OpenGL constructs that can be
>> sent straight to the hardware. Adam Kennedy has some work start in this
>> area (OpenGL::List).
>>
>>
>> Regards,
>

Reply via email to