I'm writing this message as a reaction to the video 'Sripting, baby - automating Eclipse' (http://youtu.be/FQw3eNYTgfI
). In this video you've been requesting possible use cases.
I've stumbled upon the EASE project during my search for an ideal modeling tool... Bit weird, I know, but hear me out:
I'm convinced that graphical modeling will play a major role in system (hardware, software) and process (business management, workflows) engineering. A picture is worth a thousand words! UML/SysML modeling with eclipse/topcased is great thanks to all the plugins being developed at the moment (transformations, cdo, model comparison). I've been testing several of all the features available and I really like them!
BUT eclipse doesnt really fit in the workflow. Currently I'm working as lightweight as possible, using a minimal but pleasant environment:
- ubuntu server
- 'awesome' window manager
- emacs as editor
- conkeror for web browsing
Using a heavy weight application as eclipse doesnt fit in... I've been looking for alternatives with similar functionalities but there simply are none! Some developers are doing effort to add modeling capabilities to emacs (CEDET Cogre), but they have a WHOLE road ahead of them...
What I need is some way for emacs to communicate with the components written for eclipse. Been thinking on using the eclipse plugins as standalone headless RCP apps but I returned from that road after web-search. An alternative solution would be to use eclipse components by communicating through scripts.
I would be great to generate diagrams, transform and compare models by executing scripts in emacs/other external programs and return the output to them:
-diagrams in an xemacs-buffer or an emacs org-mode latex/html export
-using the output of modelica model execution (uml models with modelicaML stereotypes)
-source code generation for ROS nodes using engines written in eclipse epsilon project.
-literate programming within emacs org and graphical execution in presentations.
These could a few possibilities. My MAIN request is simply not having to move back and forth between emacs and eclipse when I attempt integrate models within a project. If you are looking for co-developers for the use case I've described earlier, perhaps you could contact the development team behind EMACS cedet. I've posted a similar feature request to their mailing list. (Cedet-devel@xxxxxxxxxxxxxxxxxxxxx
The workflow described above is actually only one of the possible implementations of what could be one of the future goals: Using a headless eclipse RCP as middleware for software development components.
The intention would be to shift focus AWAY from all graphical UI.
In some sense I'd compare my view to a solution which is already available in robotics software development: the core components of ROS (robotic operating system) handle all communications in a standardized fashion between a very broad and distributed community of robotic software developers.
Eclipse is a component based application, but the core-components are not often used to fulfill non-IDE functionalities.
Having the eclipse core listening as server on port using minimal resources is a start. (network communication is already a requirement within Eclipse Advanced Scripting Environment project). Adding script based communication to create jobs which execute eclipse plugin functionality is great!
Eclipse is a great IDE, perhaps even the greatest when it comes to modeling. But if the user interface could be non-eclipse based, I think you'd attract alot of non-eclipse users.
I've posted a similar message to the emacs cedet development team (cedet-devel@xxxxxxxxxxxxxxxxxxxxx
) Perhaps this message could initiate communication.
What's your opinion on the subject?