We have a class JOGLLoader that suspends normal jogl loading and instead loads the linked libraries that we distribute with NetLogo. However, I noticed that this class is relatively old (2005), and I'm not sure we still need to do it this way. Was this a response to bugs, or a preemptive strike against known issues? Has the jogl/java landscape changed in the past ten years enough to warrant distributing the jogl native jars rather than the native libraries?
Frank -- You received this message because you are subscribed to the Google Groups "netlogo-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
