Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Just couldn’t find anything regarding the purpose of android.opengl classes anywhere on the web: they seem to be copies of javax.microedition.khronos.opengles – just with static vs member methods.
So is there any special meaning in using them instead of J2ME classes: are they supposed to be faster, have additional functionality, simpler to work with?
I think of using them instead of passing that GL reference all the time.
Ok, just in case someone is really interested in the difference between android.opengl and OpenGL ES standard javax.microedition.khronos.opengles packages, the following can be found in Android’s classic ApiDemos project: javadoc for com.example.android.apis.graphics.StaticTriangleRenderer class tells that android.opengl package simply provides a bit more functionality then standard khronos package, and, quite handy, it’s easier for C developers who can simply write glBindBuffer(…) instead of ((GL20) gl).glBindBuffer(…).