I see, so you are wrapping the C interface with classes? This is what I wanted to avoid, hence the port.
As you said there don't seem to be a good solution until D 2.0 is stable enough. May I ask how you were thinking of linking with the C++ code on 2.0? I haven't really looked at 2.0 yet since I'm just starting out.
But your way is probably the best one for now as it's easier to maintain when going from one SFML version to another.
I think I'll keep my version though, since I only need the Windows package for now. And the interfaces seem to be identical.
At least it's good to see that there's an interest in maintaining a D binding.
Edit: Did you consider how to create a shared sf namespace for all the packages? Not that it's a big of a problem but it would help creating a consistent interface with the other bindings.
Edit2: You mentioned you use Derelict to load symbols from the DLL. How does this affect the license? Isn't Derelict licensed as LGPL? This was also one of the reasons I decided to port SFML.
Edit3: Ah sorry I probably should have looked that up. Looks like the Util library uses a modified zlib/libpng license?