Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-scripting-dev] Reviving Eclipse Scripting project

Hi Christian,


As you may know we are also working on a scripting solution. Do you think it would be possible to organize a telephone conference in order to discuss the objectives of our respective projects?

We would like to discuss the following matters in order to validate we have the same point of view on those:


è Open Source

è Eclipse Foundation

è Contributors

è Dead Lines

è Etc…


If you agree let me know I will organize it.





Arthur Daussy



+33 5 34 36 32 90






De : eclipse-scripting-dev-bounces@xxxxxxxxxxx [mailto:eclipse-scripting-dev-bounces@xxxxxxxxxxx] De la part de Christian Pontesegger
Envoyé : samedi 17 août 2013 07:15
À : Discussions about scripting Eclipse.
Objet : Re: [eclipse-scripting-dev] Reviving Eclipse Scripting project


Hi Martin,

Just in case it does not work out with TOPCASED:
I've implemented scripting for eclipse in a similar project:

If you look at the sample script

Basically I am wrapping Java calls to script commands (currently for _javascript_, JRuby and Groovy - Jython is rather experimental so far).

Opening a remote port to accept commands would take approx 20 minutes to implement.

Let me know if you are interested

best regards

Am 09.08.2013 18:02, schrieb Oberhuber, Martin:

Hi all,


We are interested at WindRiver.

I’m going to mark Aug 20 in my calendar.


Our main interest is scripting on a very very coarse granularity: simple UI commands such as “open-view xxx” , “open-perspective yyy” as well as project model commands such as “create-project x,y,z” . It’s designed for interactive use, as well as mini-scripts that automate interactive use. Commands need to be executed either from inside Eclipse or from a network connection (ie script running outside Eclipse).


We have implemented a proof-of-concept from scratch, which I could demo in a meeting if there is interest. Compared to Monkey, I think our DOM’s are simpler since designed for interactive use, and simple sequential operations more than elaborate scripting. The “new” capability is the remote access, currently via simple JSON TCP/IP but we’re also looking at TCF for the communication. The remote capability is interesting since it allows for very simple integrations with command-line tools.


More details on the call (I’m going to be out of office next week),





Martin Oberhuber, SMTS / Product Architect – Development Tools, Wind River

direct +43.662.457915.85  fax +43.662.457915.6


From: eclipse-scripting-dev-bounces@xxxxxxxxxxx [mailto:eclipse-scripting-dev-bounces@xxxxxxxxxxx] On Behalf Of GAUFILLET, PIERRE
Sent: Wednesday, August 07, 2013 2:22 PM
To: eclipse-scripting-dev@xxxxxxxxxxx
Cc: polarsys-iwg@xxxxxxxxxxx; 'Eclipse Management Organization'
Subject: [eclipse-scripting-dev] Reviving Eclipse Scripting project


Dear all,


An essential piece of TOPCASED modelling environment is the scripting engine, used by model designers to automate some project-specific or boring activities like modifying the font of some elements in all diagrams. As described on the Scripting wiki, it is heavily based on EclipseMonkey and PythonMonkey, adding mainly some DOM to make model scripting easier and some related example scripts.


We are now about to start the migration of the major components of TOPCASED to Eclipse and PolarSys, including the scripting feature: I think it is a chance to revive the Eclipse scripting project. It also means that it is the moment to discuss and decide project organization, functional/technical needs and architecture.


So the question is: beyond ATOS and AIRBUS, directly involved in this part of TOPCASED migration, who is interested in resurrecting the scripting project at Eclipse and participating as a committer or contributor? As our deadline for the migration is October/December 2013, we need to start very soon: I would therefore like to organize a telcon with most interested parties around August 20th to initiate the process. Meanwhile, it would be great if you could expose your vision, proposals and potential involvement on this mailing list.


Of course, Arthur Daussy (ATOS) and I would be pleased to answer the questions you may have J.



Software Engineering Specialist

Avionics and Simulation Products Software - EYYW


Mailto: pierre.gaufillet@xxxxxxxxxx

Polarsys Industrial Working Group:



The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.

eclipse-scripting-dev mailing list


Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos ne pourra être engagée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être engagée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Back to the top