D and the demo scene

[maelp]

> has potential to become industry standard). So - I think - it would be  
> easy to get a bunch of them to adopt D and it could have the long-lasting  
> benefit of getting D users into gaming companies.

What's more important, is, in MY opinion, to get more "artsy" people to use D, and
therefore to develop the equivalent of www.processing.org or of _why's Shoes ruby GUI toolkit .
I am already trying to develop dVision, a smallish  embryo of a image processing, interaction and graphics D library, that is not yet mature enough to be used (though you can check some code at github.com/maelp/dvision) but would be nice to build with a small team.

What I'm aiming at is :
  - A nice image processing API that must be usable enough so that (students and) newcomers can get a grab at it very quickly, even if they don't want to use intricate D programming
  - can be easily extended and use all the features of generic programming that D can provide (although "regular" users do not have to know how to use them to their fullest extent)
  - a small processing-like or shoes like GUI / rapid prototyping environment, featuring a lot of libraries, to do interaction and graphics, hopefully enabling the processing of videos and webcams, etc
  - if we can do it, a dsss-like plugin system, where people can share repositories and do dsss net install my_extension to extend the framework

If someone has ideas / wants to help, I'm more than happy to have people join the project!