Hi Phil B



Thank you. 





I believe the OpenGL API calls were generated by code written by Andreas Raab 15+ years ago against the OpenGL spec files (these are files from the Khronos Group which have not been maintained for modern OpenGL releases).  When I asked about this over a decade ago, he responded indicating what I just wrote and that he no longer had the code he used to generate them.



Interesting. My current project is on XTreams-Parsing and I wonder if the knowledge gained there can be leveraged here to replicate Raab's work.



This would not be a trivial task since you'd probably have to rewrite, or at least significantly restructure, most of Croquet to make it work.




Do we want Croquet to be stuck with 1.6 openGL? Or are there design patterns to decouple/loosely bind the Croquet app from the api calls?



First-things-first...I need to get the existing app  working, understand what Bert is communicating and then revisit this.



Recreating Raab's work strikes me as fundamentally important to the project. 


thank you for your time.



t








---- On Wed, 11 Mar 2020 19:54:14 -0400 Phil B <mailto:pbpublist at gmail.com> wrote ----


As Bert indicated, it's not really relevant but since you asked...

I believe the OpenGL API calls were generated by code written by Andreas Raab 15+ years ago against the OpenGL spec files (these are files from the Khronos Group which have not been maintained for modern OpenGL releases).  When I asked about this over a decade ago, he responded indicating what I just wrote and that he no longer had the code he used to generate them.

If you were to do it again today, you would want to use the OpenGL C header files instead.  But again this is somewhat moot regarding Croquet: it's written against an ancient version of OpenGL (I believe 1.6 + extensions that get it *roughly* to 2.0 feature-wise) which most desktop drivers are still backwards compatible with.  So you can just use the calls already there.  You'd really only need to worry about regenerating the API if you wanted to update Croquet to take advantage of the latest OpenGL/features and/or run it under OpenGL ES.  This would not be a trivial task since you'd probably have to rewrite, or at least significantly restructure, most of Croquet to make it work.




On Wed, Mar 11, 2020 at 5:58 PM gettimothy via Squeak-dev <mailto:squeak-dev at lists.squeakfoundation.org> wrote:





btw, the glMatrixMode:mode method tells us that it was automatically generated.



by what? When? against what?

glMatrixMode: mode

"This method was automatically generated."

"void glMatrixMode(GLenum mode);"

<apicall: void 'glMatrixMode' (ulong) module: '#openGLLibraryName'>

^self externalCallFailed





Is that "automatic generation"  an example of fundamental work that must be done to make Croquet rock-n-roll?



cheers,



tty
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20200311/9c92893a/attachment.html>