1
0
Fork 0
mirror of https://github.com/rubyjs/therubyracer synced 2023-03-27 23:21:42 -04:00
Embed the V8 Javascript Interpreter into Ruby
Find a file
2012-06-19 02:37:22 -05:00
ext/v8 move object access to the class layer. 2012-06-15 09:57:42 -05:00
lib proper fix for bigdecimal and bignum conversion. 2012-06-17 02:42:23 -05:00
spec proper fix for bigdecimal and bignum conversion. 2012-06-17 02:42:23 -05:00
.gitignore ignore rbx cache and .rvmrc 2012-05-09 14:46:05 -05:00
.travis.yml update travis to include rubinius 2012-05-10 10:09:59 -05:00
benchmarks.rb support for accessors, equivalence classes 2012-05-22 12:12:08 -05:00
Changelog.md document changes since last version. 2012-06-16 12:50:12 -05:00
Gemfile move stuff into the gemfile in order to enable rbx 2012-06-16 08:42:12 -05:00
Rakefile don't run memspecs as part of CI build. 2012-06-15 10:22:51 -05:00
README.md update README to describe new build steps 2012-06-19 02:37:22 -05:00
thefrontside.png add README 2012-06-16 08:47:01 -05:00
therubyracer.gemspec move stuff into the gemfile in order to enable rbx 2012-06-16 08:42:12 -05:00

therubyracer

DESCRIPTION

Embed the V8 Javascript interpreter into Ruby.

FEATURES

  • Evaluate Javascript from with in Ruby
  • Embed your Ruby objects into the Javascript world
  • Manipulate JavaScript objects and call JavaScript functions from Ruby
  • API compatible with the The Ruby Rhino (for JRuby: http://github.com/cowboyd/therubyrhino)

SYNOPSIS

gem install therubyracer

then in your ruby code

require 'v8'
# or if using bundler (as with Rails), add the following to your Gemfile
gem "therubyracer", :require => 'v8'

evaluate some simple javascript

cxt = V8::Context.new
cxt.eval('7 * 6') #=> 42

embed values into the scope of your context

cxt['foo'] = "bar"
cxt.eval('foo') # => "bar"

embed ruby code into your scope and call it from javascript

cxt["say"] = lambda {|this, word, times| word * times}
cxt.eval("say('Hello', 3)") #=> HelloHelloHello

embed a ruby object into your scope and access its properties/methods from javascript

class MyMath
  def plus(lhs, rhs)
    lhs + rhs
  end
end

cxt['math'] = MyMath.new
cxt.eval("math.plus(20,22)") #=> 42

make a ruby object be your global javascript scope.

math = MyMath.new
V8::Context.new(:with => math) do |cxt|
  cxt.eval("plus(20,22)") #=> 42
end

you can do the same thing with Object#eval_js

math.eval_js("plus(20,22)")

Different ways of loading javascript source

In addition to just evaluating strings, you can also use streams such as files.

evaluate bytes read from any File/IO object:

File.open("mysource.js") do |file|
  cxt.eval(file, "mysource.js")
end

or load it by filename

cxt.load("mysource.js")

Safe by default, dangerous by demand

The Ruby Racer is designed to let you evaluate javascript as safely as possible unless you tell it to do something more dangerous. The default context is a hermetically sealed javascript environment with only the standard javascript objects and functions. Nothing from the ruby world is accessible at all.

For ruby objects that you explicitly embed into javascript, by default only the public methods below Object are exposed by default. E.g.

class A
  def a
    "a"
  end

  def to_s
    super
  end
end

class B < A
  def b
    "b"
  end
end


V8::Context.new do |cxt|
  cxt['a'] = A.new
  cxt['b'] = B.new
  cxt.eval("a.a") # => 'a'
  cxt.eval("b.b") # => 'b'
  cxt.eval("b.a") # => 'a'
  cxt.eval("b.to_s") # => #<B:0x101776be8> (because A explicitly defined it)
  cxt.eval("b.object_id") #=> undefined, object_id is on Object
end

If needed, you can override the Ruby Access to allow whatever behavior you'd like

More documentation can be found on the github wiki

PREREQUISITES

For platforms for which there is a binary version of therubyracer gem available, there are no dependencies other than ruby and rubygems.

If there is not a binary version for your system, then you will need to compile it from source. To do this, you must have v8 >= 3.11.8 installed somewhere on your system. There are several ways of doing this. For both you will need a C++ compiler.

The first method involves using a version of the v8 source which is maintained as a rubygem called libv8. To use it, all you have to do is add the following to your Gemfile:

gem 'libv8', '~> 3.11.8'

This will download and build v8 from source for you as part of the gem installation process. When therubyracer is installed, it will find this gem if it is present and link against the v8 binaries contained therein.

If you cannot, or do not wish to use the libv8 rubygem, then you can either install libv8 with you operating system's packaging system or you can build it from source. If you build from source, be sure to set the library=shared option. Also, if you install this shared library into a place that is not on your standard lib and include paths, then you can pass your non-standard locations to therubyracer using the --with-v8-include and --with-v8-lib configuration options.

DEVELOP

git clone git://github.com/cowboyd/therubyracer.git
cd therubyracer
bundle install
rake compile

Sponsored by

The Frontside

LICENSE:

(The MIT License)

Copyright (c) 2009,2010,2011,2012 Charles Lowell

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.