Hi Reto,
- Dependency on Sling. Mainly because the compiler needs to output the
class files into the repository.
Isn't compiling to the data-file area of the osgi bundle an option in
sling?
Probably. The convention is AFAIK to keep the compiled class files in
the repository under var/classes. I'm not sure if this is strictly
required and how this is handled by other scripting engines.
Could you give a norrower point to the things a cript-engine must do for
working with sling? I assume sling can work with a standard javax.script
complaint engine.
javax.script implementation should do. There is the issue with the ouput
directory from above.
We've implemented ScalaServerPages in a separate package
just adding a few more lines before passing it as script to the script
engine.
I've done away with that way of preprocessing. In the current version,
any script is also valid Scala. This way standard tools (IDE) can be
leveraged for these scripts. The downside is, that scripts feel a bit
less scripty that way ;-)
There are more requirements regarding the ceremony but they only applied
for scripts which should be used from within Sling.
Michael
- The variable bindings mechanism needs to be improved. I see there is some
effort in clerezza regarding this.
It's very raw at the moment but it should be possible to have an object
appearing to be of all the visible types on the scala side.
Reto
Michael
[1] http://svn.apache.org/repos/asf/sling/trunk/contrib/scripting/scala/
[2]
http://people.apache.org/~mduerig/scala4sling/scala4sling.pdf<http://people.apache.org/%7Emduerig/scala4sling/scala4sling.pdf>
