Nevertheless all the components exists and mature (Eclipse, languages, and interpreters), no one project in Eclipse scripting did not hit minds of Eclipse software engineers yet. During the talk we'll try to understand real values of scripting and understand why this scripting race has no aim in some cases. We'll recap various efforts in scripting area, and try to dispel some prepossession (e.g. "scripting and/or dynamically typed languages increases developer productivity").
As we understand before Monkey DOMs can do some useful tasks and as a result hide complexity and increase developer productivity. If so they might be interested to much wider audience. So when Java engineers will start to use DOMs from their code, and will provide DOMs to others, DSLs operating on that DOMs may become best chioce for some development cases, scripting and Eclipse autmation. I believe Monkey is not popular because DOMs are designed specially for scripting needs. Instead of Monkey DOMs we need domain-specific structures designed for problem domain needs. And the solution we may find within Eclipse Modeling Projects.
Eclipse Command Language (ECL) is a new language initially designed for Eclipse Scripting and Automation needs, and to be integrated with Eclipse EMF and M2T projects. For automation needs heavy console usage is supposed so most of existing scripting languages were refused. TCL was considered as a good choice for building DSLs but refused due to it's non object-oriented nature.
This talk will explain backgrounds of ECL, show reference implementation of the language, Eclipse ECL console with current OSGi Console functions and more.
Andrey Platov is a Project Lead for the Eclipse Dynamic Languages Toolkit (DLTK) project.
Andrei is Senior Software Engineer at xored software, Eclipse DLTK co-project lead.