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"

< E4
Line 1: Line 1:
Doing easy customizations and automation of common workflows is the bread-and-butter of pretty much every advanced editor such as Emacs, vi, Slickedit, Textmate or others.
+
Scripting is about easy customization, and automation of common workflows.
Office products such as LibreOffice or the Microsoft suite provide scripting and macro recording as essential capabilities for easy extension.
+
JTAG debuggers such as Lauterbach Trace32 or Greenhills MULTI are even built around scripting.
+
  
At Eclipse, lots of efforts around scripting exist but it's very fragmented.
+
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.
 
+
This effort is about getting together to unify efforts.
+
  
 
== Mailing List ==
 
== Mailing List ==

Revision as of 04:50, 18 April 2012

Scripting is about easy customization, and automation of common workflows.

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.

Mailing List

Meetings

Use Cases

List of use-cases for scripting, most relevant ones first

Known Approaches

Known software that brings scripting to Eclipse, most interesting ones first

Copyright © Eclipse Foundation, Inc. All Rights Reserved.