Re: [e4-dev] Integration of Scripting Languages

[Simon Kaegi <Simon_Kaegi@xxxxxxxxxx>]

I agree some sort of abstraction like BSF / javax.scripting is worth looking at to avoid everyone having to roll their own "initialization" or script engine discovery story. On the other hand a good API for script execution and other integrations is much harder and I'm in the same boat as Hallvard and Hiroki and am using the native Rhino APIs to provide modularity inline with OSGi, debug and source lookup. Another concern I have specifically with using javax.scripting for _javascript_ is that by default we'd end up using the Rhino fork Sun packaged in the JRE and this version unfortunately has problems I cannot work around in it. With that said if you have concrete ideas why not open a bug. I'd be interested in working on the "script engine" discovery part of this problem.
-Simon


Hiroki Kondo ---11/29/2009 10:13:03 PM---Hi, e4 dev team. I agree Hallvard's comment!

From:	Hiroki Kondo <kompiro@xxxxxxxxx>
To:	E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>
Date:	11/29/2009 10:13 PM
Subject:	Re: [e4-dev] Integration of Scripting Languages
Sent by:	e4-dev-bounces@xxxxxxxxxxx

---

Hi, e4 dev team.

I agree Hallvard's comment!

Because how do you think about Scripting Engine's native feature like 
"readline history" and content completion feature. JRuby runtime engine 
is supported both features.But these features are not supported in BSF 
and and JSR 233 "javax.scripting" packages.
So,I need to support language-specific integration.

Regards,

Hallvard Trætteberg wrote:
> Tom Schindl wrote:
>>
>> This way not only _javascript_ (mostlikely the Rhino implementation) can
>> be used to create and run scripts for Java applications and Java
>> frameworks, but *any* of the many scripting languages for which script
>> engines have been written for BSF 3.0/"javax.script" and listed e.g. at
>> <https://scripting.dev.java.net/> with no real additional effort on the
>> side of the Java application and framework implementors.
>>
>> ...
>>
>> What I'd like to propose is that instead of using Rhino-Directly in
>> JSContributionFactory to go through the BSF and hence support various
>> scripting frameworks out of the box.
>
> I completely agree that we should go through javax.scripting/Apache 
> BSF for basic scripting support.
>
> Still, we should remember that there are different levels of 
> integration desired, that may require language-specific integration. 
> With javax.scripting you can execute scripts in a scope, lookup 
> variables in a scope, etc. Often you want to go further than that, by 
> exploiting specific language features. E.g. in the _javascript_ support 
> for EMF a richer API is provided that exploits _javascript_'s function 
> objects.
>
> Hallvard
> _______________________________________________
> e4-dev mailing list
> e4-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/e4-dev
>

_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev