44
I Use This!
Activity Not Available

News

Analyzed 11 months ago. based on code collected 11 months ago.
Posted about 9 years ago
adding the LWJGL* prefix to any class makes it feel verbose FortressBuilder does raise a good point about the Runtime being confusing with java.lang.Runtime as that is a core java vm class.Other names options could include "Library", "Lib", "LibLWJ...
Posted about 9 years ago
"Environment" comes to my mind when thinking about aspects 1. and 3.However, I think "Environment" does not fit aspect 2. as good as "Runtime."EDIT: Or better (I think) would be "Platform."
Posted about 9 years ago
The problem with calling it Runtime is that this would clash with java.lang.Runtime. Maybe something like LWJGLRuntime?
Posted about 9 years ago
Okay, I just had a more closer look at the LWJGLUtil and Sys classes what they actually do.As I see it, there are the following aspects currently dealt with by those classes:1. Obtaining the platform that LWJGL is running on (LWJGLUtil)2. Loading sh...
Posted about 9 years ago
Quote from: spasi on November 04, 2015, 23:12:48Does it work if you launch the JVM with:Code: [Select]-Dorg.lwjgl.opengles.libname=libGLESv2.so.2Yes it works! Thank you again for help!
Posted about 9 years ago
A major difference is that Configuration contains mutable state. The user may set values there and LWJGL reads those values (usually only once at startup). The Sys and LWJGLUtil fields are all immutable (finalized at runtime, on class init).
Posted about 9 years ago
Does it work if you launch the JVM with:Code: [Select]-Dorg.lwjgl.opengles.libname=libGLESv2.so.2You can also do it programmatically with:Code: [Select]Configuration.LIBRARY_NAME_OPENGLES.set("libGLESv2.so.2");
Posted about 9 years ago
Quote from: kappa on October 31, 2015, 09:00:19Quote from: bobjob on October 31, 2015, 08:57:58I decided to give LWJGL 3 a try on El Capitan ("HelloWorld") and ran into an even bigger problem where the app...
Posted about 9 years ago
I have been working on a GUI library for about a year now. The library is completely platform independent and thus could be used with LWJGL 3. Unfortunately progress is slow and it is not on the same level as Swing by far. Perhaps I am going to publish...
Posted about 9 years ago
I am planning to do what @Spasi proposed: Taking the good and working classes from LWJGL2, which do OpenGL context creation themselves via JNI, and porting them to the native platform API exposed as Java methods by LWJGL3. This should not be too much w...