I had a look at the scripting interface of the new api. It lacks some sort of function pointers: Java proxies for calling script functions.
I think xswt has a mature scripting interface. Why not adapting it? Or at least, there are other frameworks/specs for enabling scripting in java: jsr223, or the bean scripting framework (bsf, apache). 2008/12/22 Boris Bokowski <[email protected]> > Hi Michael, > > There is some "groundwork" but it is very preliminary. I would be very > interested in others trying to plug in new languages - the earlier we do > this, and the more languages we support, the better it gets (and the less we > will end up with API that can only be called/used from certain languages). > > If you look at the e4 photo demo app (psf files should be in the releng > project) you will find an extension point "org.eclipse.e4.languages" defined > by one of the plugins (I believe org.eclipse.e4.core.services) and an > extension that adds JavaScript support. There are some example scripts in > the photo demo application plugin, under "scripts", but they are not > referenced from the checked in Application.xmi. You can change one of the > URIs for the handlers to > platform:/plugin/org.eclipse.e4.demo.e4photo/js/scripts/newproject.js (the > "js" in this path has to match the extension id) and it should work. > > I am writing this from my vacation, without checking the code, so actual > plugin/extension point/script names may be inaccurate. Let me know if these > pointers are not enough to get you started and you need more help. > > Boris > > Michael Spector wrote on 12/18/2008 03:09:17 AM: > >
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
