Apple's Dylan environment was never released in source form.
On Linux and Mac OS X, we do have the command line tools. We have emacs integration available:
https://github.com/dylan-lang/dylan-mode
On Windows, we have a full IDE, including debugging, but it is a bit difficult to get running correctly as it requires having PellesC on the path (or a really outdated version of Visual C 6). The next release or two will simplify and improve this some.
There's some information about why the IDE is on Windows only and the status of our Windows support on the Dylan Foundry blog:
http://dylanfoundry.org/2013/01/23/windows-current-state-of-...
http://dylanfoundry.org/2013/01/18/why-is-the-opendylan-ide-...
Despite the IDE itself being Windows only, a lot of the backend code to support the IDE is part of the command line tools, but without a UI. This can be seen by a prototype web-based IDE that Bastian Muller was working on as a university project:
http://turbolent.github.com/hula-presentation/
One of the interesting tools that Apple had was one called Creole which was for making it easier to produce bindings for libraries in C, etc. The Gwydion Dylan team at Carnegie Mellon University produced a similar tool called "melange". I recently wrote about using melange to produce bindings for the nanomsg library:
http://dylanfoundry.org/2013/01/25/binding-nanomsg-with-mela...
In addition, melange documentation has recently been restored to a form where we can build and maintain it:
http://opendylan.org/documentation/melange/
As for the future ... it would be entirely possible to build some nice SublimeText integration, improve the emacs integration, build a web-backed IDE, get our UI toolkit (DUIM) up and running on Linux or OS X and start making the IDE work on those platforms, or many other possible projects in this area.
I've also been looking at writing some extensions or Python scripts to use with lldb and the binaries that we get from the Dylan compiler's C backend. That looks pretty promising and will be even more promising once the LLVM compiler backend is up and running.
The foundations are there and in general are pretty strong. We just need some help.