|
|
| (33 intermediate revisions by 8 users not shown) |
| Line 1: |
Line 1: |
| − | Scripting is about easy customization, and automation of common workflows. | + | = EASE - Eclipse Advanced Scripting Environment = |
| | | | |
| − | While most editors, IDE's and office tools support some sort of scripting, there is no common approach at Eclipse. Some projects exist but it's very fragmented. This effort is about getting together and unifying the efforts, such that we all get to a better solution.
| + | == What is EASE? == |
| | | | |
| − | == Mailing List ==
| + | EASE integrates script language interpreters directly into your Eclipse application. It allows to automate common tasks, extend the IDE and to create dedicated dialects of a script language. You can write, execute, debug and integrate scripts in a single Eclipse instance. |
| − | | + | |
| − | Please direct all discussions around scripting to our archived mailing list. This page will collect our current understanding of things.
| + | |
| − | | + | |
| − | * [https://dev.eclipse.org/mailman/listinfo/eclipse-scripting-dev eclipse-scripting-dev]
| + | |
| − | | + | |
| − | == Meetings ==
| + | |
| − | | + | |
| − | * [[E4/Scripting/bofecon12]] - interested parties, list of tools, and some hands-on thoughts
| + | |
| − | * [[E4/Scripting/summit08]] - hilevel list of use-cases and thoughts
| + | |
| − | | + | |
| − | == Use Cases ==
| + | |
| − | | + | |
| − | List of use-cases for scripting, most relevant ones first
| + | |
| − | | + | |
| − | * '''UI Automation:''' add a button to perform common task, and deploy that in a team easily.
| + | |
| − | ** open multiple Views
| + | |
| − | ** simple integrations with external tools (like "External Tools..." but better integrated eg context menu)
| + | |
| − | ** eg find-replace certain things in certain files
| + | |
| − | ** eg force-load a couple Preferences
| + | |
| − | * '''Data Processing:''' Create a Project with certain properties, add some files / folders. Should work non-UI on commandline too.
| + | |
| − | * '''Editor Macros'''
| + | |
| − | * Recording of steps (as a help to find ID's and edit the script afterwards)
| + | |
| − | * Drive operation inside running Eclipse from the outside
| + | |
| − | | + | |
| − | === Non-functional requirements ===
| + | |
| − | | + | |
| − | Most important requirements first.
| + | |
| − | | + | |
| − | * '''View-Source''': make it easy to read existing scripts, and modify for my own purpose
| + | |
| − | * '''Easy Sharing''': Send a script around that I like and make it super easy to deploy
| + | |
| − | * '''Simple API for common things (DOM)''': Eclipse API is too complex for simple things. Make simple things simple, allow break-out to full Eclipse API for complex things.
| + | |
| − | * '''Extendable''' for new commands / DOM's
| + | |
| − | * Support '''recording of UI interaction''' in order to discover ID's and create a minimal basic frame for a script
| + | |
| − | * Can '''drive from the outside'''
| + | |
| − | * Works '''in non-UI mode'''
| + | |
| − | * Multiple languages supported (everyone has their favorite ... though if there is ONE common good solution that's maybe better than yet more fragmentation)
| + | |
| − | | + | |
| − | === Success Criteria ===
| + | |
| − | | + | |
| − | Looks like Eclipse Monkey supported the first four requirements (above) already, why didn't it succeed ? What can be done to make a new approach succeed ?
| + | |
| − | | + | |
| − | == Known Approaches ==
| + | |
| − | | + | |
| − | Known software that brings scripting to Eclipse, most interesting ones first. May want to create sub-sections per tool as we collect more information about each.
| + | |
| − | | + | |
| − | * [https://github.com/xored/ecl Eclipse Command Language (ECL)]. Core is Open Source. Commercial [https://github.com/xored/q7.extensions.ecl extensions] used by Xored in Q7 for [http://www.xored.com/products/q7/q7-discover/eclipse-command-language/ test automation].
| + | |
| − | ** Every command created manually as an EMF object, data passed as EMF. Pipes and functional programming.
| + | |
| − | ** Supports recording of UI interaction into the scripts in Q7.
| + | |
| − | * [http://www.eclipsecon.org/2012/sessions/modular-and-extensible-osgi-shell OSGi Shell] in Equinox 3.8 Juno and newer
| + | |
| − | ** Builtin commands for OSGi interactions and basic manipulation. Telnet and SSH connectivity. Contribute commands as OSGi Services.
| + | |
| − | * [[Eclipse_Monkey_Overview|Eclipse Monkey (archived)]] - the original approach contributing menus through metadata in scripts residing in the workspace. Javascript only.
| + | |
| − | ** [http://groovy.codehaus.org/Groovy+Monkey Groovy Monkey] - The successor of Eclipse Monkey, supporting Groovy, Beanshell, Ruby or Python.
| + | |
| − | ** [http://www.topcased.org/ TOPCASED] supports scripting, from what it seems another Eclipse Monkey clone. ''Details TBD.''
| + | |
| − | ** [http://www.viplugin.com/scripteclipse/ ScriptEclipse] - Another sequel of Eclipse Monkey it seems. ''Details TBD''.
| + | |
| − | * [http://www.jython.org/ Jython] - Drive Java from Python. Used in commercial test tool [http://www.qfs.de/ QF-Test].
| + | |
| − | * [https://wiki.appcelerator.org/display/tis/Creating+a+new+Ruble Aptana: Rubles] - Ruby bundles to extend the IDE. Modeled after the [http://macromates.com/ TextMate] editor.
| + | |
| − | * [http://www.mulgasoft.com/ Emacs+] - Editor scripting through Emacs emulation.
| + | |
| − | * GroovyEclipse (Editor scripting)
| + | |
| − | * DLTK - Console for running scripts
| + | |
| − | * Javascript / Rhino engine
| + | |
| − | * Java 6 and later - scripting interface (being used in several approaches above)
| + | |
| − | * BeanScripting foundation for WebSphere
| + | |
| − | ** Scala etc in plugins
| + | |
| − | ** Mohammed's old extension point infrastructure
| + | |
| − | | + | |
| − | === Automated Recording ===
| + | |
| − | * Not perfect, but may help finding ID's etc.
| + | |
| − | ** SWTBot
| + | |
| − | ** [http://eclipse.org/jubula/ Jubula] - does not record into scripts
| + | |
| − | ** WindowTester
| + | |
| − | ** Xored Q7 / Eclipse Command Language (ECL) - see above
| + | |
| − | | + | |
| − | == Next Steps ==
| + | |
| − | | + | |
| − | * Get in touch with more interested parties
| + | |
| − | * Collect very concrete use-cases
| + | |
| − | * Find candidate tools to look at in more detail
| + | |
| | | | |
| | + | If you are intersted, please see the official project homepage: http://eclipse.org/ease |
| | | | |
| | [[Category:E4|Scripting]] | | [[Category:E4|Scripting]] |
EASE integrates script language interpreters directly into your Eclipse application. It allows to automate common tasks, extend the IDE and to create dedicated dialects of a script language. You can write, execute, debug and integrate scripts in a single Eclipse instance.
