chris_c
Member
- Joined
- Jun 25, 2010
- Messages
- 393
- Age
- 56
http://www.youtube.com/watch?v=CbaQE4MI-44
Nearly ready for a first release! I have xlib events and full screen working to my satisfaction, all I need to do now is to package up some of the code in the sample into utility routines, oh and I should provide a way to shutdown the gles context too I suppose
) !
Events I trap are mouse motion and mouse button press/release and key press/release. I'll be turning this into :-
utilPollEvents() must be run once a "frame"
utilGetMousePos() returning a tuple
utilGetMouseButton() a bool
There will also be a Boolean array of key states so you can do
if (utilKeys[24]):
print "q pressed!"
All the GLES stuff is literally directly calling the GLES library like this for example
gles.glPopMatrix()
gles.eglSwapBuffers(egldisplay,eglwindow)
There will be a utilInitialiseGLES() function that will open up a full screen context and return some info you'll need later for example the display and window handles...
There are almost certainly bugs in the function parameter decelerations so I'll be needing feedback
I do NOT plan to include higher level features like texture loading or 3d OBJ loading etc as I feel this is out of the scope of this module
I might at a later date put some of my old python OBJ loading and other support routines into a separate module if there is need, what I'd like to add to the OBJ loader would be a TRI soup to
TRI strips routine, but I need to hunt down an algorithm for that one!!!
At this stage I would also welcome any general ideas or suggestion that people might have, baring in mind that I want to keep this module as light and close to the "bare metal" as possible
(the only reason Xlib event handling is included is because I needed to create a window for the context and I wasn't too sure how people would go about getting events given only a window handle!)
Anyone with good python skills who knows GLES interested in doing some samples to go with the module?
Nearly ready for a first release! I have xlib events and full screen working to my satisfaction, all I need to do now is to package up some of the code in the sample into utility routines, oh and I should provide a way to shutdown the gles context too I suppose
Events I trap are mouse motion and mouse button press/release and key press/release. I'll be turning this into :-
utilPollEvents() must be run once a "frame"
utilGetMousePos() returning a tuple
utilGetMouseButton() a bool
There will also be a Boolean array of key states so you can do
if (utilKeys[24]):
print "q pressed!"
All the GLES stuff is literally directly calling the GLES library like this for example
gles.glPopMatrix()
gles.eglSwapBuffers(egldisplay,eglwindow)
There will be a utilInitialiseGLES() function that will open up a full screen context and return some info you'll need later for example the display and window handles...
There are almost certainly bugs in the function parameter decelerations so I'll be needing feedback
I do NOT plan to include higher level features like texture loading or 3d OBJ loading etc as I feel this is out of the scope of this module
I might at a later date put some of my old python OBJ loading and other support routines into a separate module if there is need, what I'd like to add to the OBJ loader would be a TRI soup to
TRI strips routine, but I need to hunt down an algorithm for that one!!!
At this stage I would also welcome any general ideas or suggestion that people might have, baring in mind that I want to keep this module as light and close to the "bare metal" as possible
(the only reason Xlib event handling is included is because I needed to create a window for the context and I wasn't too sure how people would go about getting events given only a window handle!)
Anyone with good python skills who knows GLES interested in doing some samples to go with the module?