Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "E4/Scripting/ESR Requirements"

< E4‎ | Scripting
(Functional requirements)
Line 9: Line 9:
 
* Be callable through the network.
 
* Be callable through the network.
 
* Provide means to simplify the access to Eclipse API so that non-Java-aware users can call easily the commands they need.
 
* Provide means to simplify the access to Eclipse API so that non-Java-aware users can call easily the commands they need.
 +
* Provide modern edition capabilities, including colorization and auto-completion.
 +
* Provide the mean to specify where (tool bar menu, pop up menu) and when (type of the selection, number of objects selected) the scripts are proposed to the user in the Eclipse UI.
 +
* Provide standard debugging capabilities.
  
 
The Scripting Engine (SE) may:
 
The Scripting Engine (SE) may:
 
* Support Groovy and Ruby.
 
* Support Groovy and Ruby.
 +
* Provide macro-recording capabilities.
 +
  
 
==Non-functional requirements==
 
==Non-functional requirements==

Revision as of 11:58, 2 September 2013

This page gathers requirements from the interested parties of the Eclipse Scripting revival launched in August 2013.

Functional requirements

The Scripting Engine (SE) shall:

  • Provide capability to call any Eclipse API.
  • Be agnostic in term of scripting language.
  • Support at least Javascript and Python.
  • Be callable through the network.
  • Provide means to simplify the access to Eclipse API so that non-Java-aware users can call easily the commands they need.
  • Provide modern edition capabilities, including colorization and auto-completion.
  • Provide the mean to specify where (tool bar menu, pop up menu) and when (type of the selection, number of objects selected) the scripts are proposed to the user in the Eclipse UI.
  • Provide standard debugging capabilities.

The Scripting Engine (SE) may:

  • Support Groovy and Ruby.
  • Provide macro-recording capabilities.


Non-functional requirements

Back to the top