You can consider it in an alpha state. Currently, there are three packages: DerelictUtil, DerelictGL3 and DerelictGLFW3. The readme in the repository explains most of what you need to know to get started. Two things to note. First, if you aren’t using modern OpenGL, stick with Derelict2. Second, if you are using D1, stick with Derelict2. Otherwise, consider this an opportunity to easily get up and running with Modern OpenGL in D.

If you do want to dive in, you’ll likely want to get your hands on GLFW 3 if you haven’t got a framework already. I do intend to add bindings for SDL 2, but for now GLFW 3 is it.  You’ll have to check out the source from the Sourceforge git repository (the Subversion repository is the 2.7 branch — not what you want). You’ll then need CMake to build.

As I explain in the readme, non-Windows and/or non-DMD users will need to modify the Derelict build script to actually build Derelict3. It is currently set up only for Windows and is not in a final, configurable form yet. I just hacked it together, though I did put just a little bit of structure in it with an eye to the future. It shouldn’t take too much effort to get it going.

Enjoy!

I don’t know the history behind this particular branch, but SiegeLord has finished an initial port of Tango to D2. The announcement says it works fine alongside Phobos, a serious validation of one of the reasons behind D2′s adoption of DRuntime. This means that, as long as they use D2, library developers can make use of either Phobos or Tango without care. And app developers can use any library that suits their app, regardless of whether it’s using Phobos or Tango under the hood. Awesome stuff.

To be sure, the old religious Phobos/Tango divide has not been a problem for quite some time, as it’s been pretty much settled that you use Tango with D1 and Phobos with D2. Well, for those in the know at least. There are a lot of unenlightened people out there who go on hearsay. Now, with D2, you can get the best of both worlds. Use whichever suits your style, or both at once, and no guilty feelings. Hopefully, this will put the old infamous legend to rest once and for all.

I’ve rarely looked at Tango since moving to D2 some time ago, except for an occasional compile to make sure Derelict still builds with it. From a practical point of view, I think it’s useful to make use of both libraries. So now that we have the ability to do so, I’m more excited than I expected to be. There are certain features one has that the other lacks, or that are more complete in one than the other. There I can see great benefit. It all depends on how well they play together. From what I’ve heard so far, they seem to get along swimmingly.

Of course, I’ll have to investigate this more to see if it really is as useful for me as it appears on the surface. In the meantime, thanks for the effort, SiegeLord, Jacob Calrborg, Igor Stepanov, and whomever else contributed!

The topic of ranges is, in my opinion, the single most difficult concept for D newcomers to wrap their heads around. I know I’ve had my fair share of head-scratching moments when functions in std.algorithm or std.range didn’t work the way I expected them to. This chapter definitely goes a long way to reducing them.

Use these commands to clone the repository and get all submodules:

$ git clone git://github.com/d-widget-toolkit/dwt.git
$ git submodule init
$ git submodule update

In another post, he mentioned that he has no time for DWT development himself at the moment, but will happily accept pull requests. So those of you with the wherewithal to do some work on DWT , your country (that would be D Land) needs you.

One important related bit of news is that next year, from Dec 31, 2012, DMD 1.x will no longer be developed. So if you’ve got a D1 codebase you were considering porting to D2, now may be the time to get started on that. The D1 compilers will still be around, of course, they just will no longer have any official support.