| [JS4EMF] goal of JS4EMF [message #683806] |
Tue, 14 June 2011 13:06  |
 Tristan Faure
Messages: 460
Registered: July 2009 |
Senior Member |
|
|
Hi all sorry if this question has been already asked.
What are the difference between JS4EMF and previous projects for script integration like Eclipse Monkey ?
|
|
|
|
| Re: [JS4EMF] goal of JS4EMF [message #683953 is a reply to message #683806] |
Tue, 14 June 2011 18:12  |
Eclipse User |
|
|
|
Originally posted by:
On 14.06.11 15.06, Tristan FAURE wrote:
> Hi all sorry if this question has been already asked.
> What are the difference between JS4EMF and previous projects for script
> integration like Eclipse Monkey ?
I believe Eclipse Monkey is for scripting the Eclipse workbench and
utilizing Eclipse API's in Javascript, whereas JS4EMF is "limited" to
EMF, and as such, independent of Eclipse. As Ed Willink writes, JS and
OCL both supports "internal" scripting, by embedding script code in
Ecore models and utilizing the delegate mechanism. In addition, JS4EMF
supports using Javascript for manipulating Ecore objects in general,
e.g. for ad-hoc queries, editing, transformations etc. Finally, we want
to integrate EMF UIs with scripting, e.g. support Javascript-based
content and label providers, so more of an EMF-based application can be
configured with scripts and models, rather than with generated and
modified Java-code.
Hallvard
|
|
|
Powered by
FUDForum. Page generated in 0.31470 seconds
] 
Search
Help
Register
Login
Home
