[Bradley Smith]

GLD is a native D port of GLFW. It works on Windows and Linux, but has only been minimally tested using the example programs included.

By default, GLD directly links to OpenGL libraries. However, on Windows, it can optionally use the Derelict bindings for OpenGL. In the future, Derelict compatiblity may also be available on Linux.

GLD can be downloaded from http://www.baysmith.com/d/gld.zip

Since GLD is a direct port of GLFW, no documentation is provided. Instead, use the GLFW documentation. Simply subsitute gld for glfw and GLD for GLFW where necessary.

[clayasaurus]

Are you going to start up a dsource project? or are you leaving this for others to develop more.

[Bradley Smith]

I've made a request for a dsource.org project.

[elmindreda]

Thank you for making a port of GLFW to the D language. That's very cool, and it's always nice to see people make use of the code.

However, by removing the copyright and license headers from the source files originating from GLFW, you have violated its license. Please correct this.

[Bradley Smith]

According to the GLFW license,

[elmindreda]

[elmindreda]

[JJR]

This is unfortunate. After reading the notice again, it could indeed be interpreted either way. It's sad that the license wasn't clear on this. Furthermore, the menton of "source distribution" makes the intent even more unclear such that I understand why Bradley felt he was meeting the requirements . It would have been very simple to indicate "source headers" here if that was the intent.

Gld, in its current form, however does make it extremely easy to grab certain source files and repackage it without any way to trace where it came from. Even a small header might be adviseable, as a courtesy, pointing to the origin of the package and crediting the original glfw. Granted anyone could remove that, but that would require more concerted effort.

Note that DerelictGLFW removed the license because it was not redistributing a source distribution: it merely used a header mapping. I believe any complete port has to follow different rules in this matter.

That said, I think it would be a good idea to figure out a way to identify source files with a small header that gives the appropriate credit. It would be good if it makes a reference to readme.txt in the package ("for further reference").

Just a suggestion.

-JJR

[clayasaurus]

Could you simply have a comment like...

/// see readme.txt for license details

in each header file?

[aldacron]

[JJR]

I believe the decision is up to elmindreda now since Marcus gave the project up.

The fault appears to remain the result of imprecise wording of the license. Adding credits to the source headers might be a nice touch but that likely doesn't accomplish much from the maintainer's perpective, if the license is the issue?

-JJR

[elmindreda]