On Sep 5, 2:53 pm, "Furash, Gary F. \(US - Costa Mesa\)" <[EMAIL PROTECTED]> wrote: > Have any of you seen the jslibs project? How does it compare with rhino? > > Gary Furash, PMP > Technology Integration/Public Sector > Deloitte Consulting LLP > > Mobile: + 1 714 478 3826 > [EMAIL PROTECTED]
It's difficult to compare jslibs (a library) with Rhino (a JavaScript engine). But the point is valid: SpiderMonkey is to Rhino as jslibs is to ...? For client side development there seem to be two directions (both dependent on the JavaScript engine): 1. SpiderMonkey (C implementation) then wrapping C libraries to produce an enhanced JavaScript Environment (jslibs). 2. Rhino (Java implementation) then wrapping Java libraries to produce an enhanced JavaScript Environment (...). The first is sort of 'traditional' in the sense that most linux based scripting languages follow this path, Ruby and Python spring to mind - the SWIG tool was also developed for this purpose. Obviously, they can also be moved (with some effort) to Windows. The second, since it is Java based, is in theory OS independent, but of course inherits the same problems that Java has. This usually has to do with the OS dependent JVM implementation, but I'm also thinking about the Swing GUI, which hasn't been all that successful. Also there doesn't seem to be a 'generic' library for Rhino, similar to jslibs for SpiderMonkey, but I may be wrong. I have done some work on this, resulting in a fledgling project towards this goal, called Crash. (http://code.google.com/p/crash/) It leverages a few of the Java libraries, and could do more of course. However, there will be the same difficulty adding traditional C libraries in this scenario as there is in Java itself - damn difficult - the JNI has not been a wild success either. Hope that helps, John _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
