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.
Difference between revisions of "E4/Scripting/ESR Requirements"
(New page: This page gathers requirements from the interested parties of the Eclipse Scripting revival launched in August 2013. ==Functional requirements== ==Non-functional requirements==) |
(→Functional requirements) |
||
| Line 2: | Line 2: | ||
==Functional requirements== | ==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. | ||
| + | |||
| + | The Scripting Engine (SE) may: | ||
| + | * Support Groovy and Ruby. | ||
==Non-functional requirements== | ==Non-functional requirements== | ||
Revision as of 11:43, 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.
The Scripting Engine (SE) may:
- Support Groovy and Ruby.