Patrick Wright wrote: > Per--sounds like Kawa's got some good code to build on top of. One > question would be how to structure the console (whether GUI or CLI) in > such a way that language implementors would not feel constrained, but > rather welcome and interested in plugging in their own language (e.g. > adaptor to a language's interpreter, context introspection, etc.). > ...
It isn't necessarily the perfect solution for everyone, but I'm using JSR-223 for language integration. It would be a good thing if all you language implementors would provide JSR-223 support in, and Maven repository availability, for your language implementations. I've just rolled the JSR-223 engine into Groovy and I've heard JRuby may do so as well. There are quite a few here: https://scripting.dev.java.net/ I've long dreamed of the perfect console, and my first go is IFCX Wings. Which unfortunately is definitely not the perfect console, but there are some bits that will carry forward into a web browser version. http://www.ifcx.org/ There is code in SVN (WebWings) that adapts the Wings evaluator to GWT RPC, although there's no front end yet. MathEclipse has a GWT front end, but is pretty limited as far as being a console. http://www.matheclipse.org/ Jim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to jvm-languages@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
