Eclipse Dynamic Language Toolkit
JAXenter: Hello Mr. Platov! Can you describe the Eclipse DLTK Project in a few words?
Andrey Platov: Yes, the idea behind the DLTK project is to reduce development time of an Eclipse-based IDE for a programming language in times, say from years required to develop fully featured modern JDT-alike (Java Development Tooling) IDE to months, or even weeks. DLTK's Core Frameworks provide language-independent building blocks for such IDEs. So IDE developers are focused only on language-aware tasks like source code parsers, runtimes, etc.
JAXenter: Can you give a typical use case for the project?
Andrey Platov: Typical use case for DLTK's Core Framework is to build an IDE for particular languages. For example, Eclipse PDT (PHP Development Tools) project was done with PDT 2.x versions, which is built on top of DLTK.
End user (TCL or Ruby) developers may use TCL/Ruby IDEs in their everyday work.
JAXenter: What´s new in the Galileo Version of DLTK?
Andrey Platov: The goal for Galileo version was to improve stability. DLTK is a relatively young project, but this is the 3rd simultaneous Eclipse release for us. In the past year more and more people have come to rely on DLTK as a foundation for their IDEs. PDT's decision to switch to DLTK is obviously very important for us: PDT is the most popular project within Eclipse Foundation (as in June 2009). This means DLTK code is working on thousands of desktops around the globe. So with this release DLTK has reached a mature state; we released version 1.0 and graduated from the Eclipse incubator.
JAXenter: Where do you see DLTK in one year? How will the project evolve after Galileo?
JAXenter: Thank you very much for this conversation!