>>>>> "Frank" == Frank Duncan <[email protected]> writes:
Frank> We have a class JOGLLoader that suspends normal jogl loading and Frank> instead loads the linked libraries that we distribute with Frank> NetLogo. However, I noticed that this class is relatively old Frank> (2005), and I'm not sure we still need to do it this way. Was Frank> this a response to bugs, or a preemptive strike against known Frank> issues? Has the jogl/java landscape changed in the past ten Frank> years enough to warrant distributing the jogl native jars rather Frank> than the native libraries? The problem was that if the user had JOGL installed in their home directory or a system directory, NetLogo would pick up that version instead of our bundled version. And yes, this routinely caused problems. (I saw it happening to other JOGL-based apps such as Repast.) I haven't looked at anything JOGL-related in nearly a decade, but I'd guess that the need to prevent from that happening is probably still real. Both for fear of the user having a too-old version around, *and* the fear of a too-new version. Perhaps newer JOGL versions and/or newer JRE versions offer (or at least enable) a less clunky way of accomplishing the goal, though? It's possible that some digging around in our closed-source-era private archives, namely https://github.com/netlogo/netlogo-legacy-tickets and the ccl-devel mailing list archives, would turn up some additional information. I was involved to some extent, but iirc Esther and Craig did the heavy lifting. -- Seth Tisue | http://tisue.net -- 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.
