Ruby Java
Switch branches/tags
Nothing to show
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
assets
bin
lib
package/classes/java
spec
src/org/rubyforge/rawr
.document
.gitignore
.rspec
.ruby-gemset
.ruby-version
Gemfile
LICENSE.txt
OpenAL32.dll
README.rdoc
Rakefile
build_configuration.rb
liblwjgl.jnilib
lwjgl.dll
openal.dylib

README.rdoc

waves

This is just some JRuby(jruby.org/) and jMonkeyEngine(jmonkeyengine.org/) fun. Currently these are all samples from the jMonkeyEngine Hello tutorials re-written in JRuby. There are a few small modifications.

Installation

install jruby-head
git clone git://github.com/jwoertink/Waves.git
cd Waves

You should be good at this point.

Running Waves

The main application can be run by

jruby bin/waves

You can view other samples by passing the sample number as an argument

jruby bin/waves 8

Normal camera operations use W A S D to move. To exit just hit esc. Some examples use space bar, or J and K keys. Read sample file in lib/samples for more info.

Requirements

OSX 10.8.0+ / Windows 7+
A decent graphics card
JRuby 1.7+

jMonkeyEngine

hub.jmonkeyengine.org/wiki/doku.php/jme3🔰hello_simpleapplication

Other Notes

The Nifty-gui must be implemented in Java (for now) to work. This requires taking the lib/samples/nifty/StartScreenController.java and compiling it into the package/classes/java/StartScreenController.class file. If this file is missing, then to compile, run

javac -classpath vendor/jme3_2014-3-31.jar  lib/samples/nifty/StartScreenController.java
mv lib/samples/nifty/StartScreenController.class package/classes/java

Current (known) Issues

  • Not tested in any other OS

  • Nifty/JRuby example (sample 13a) throws nasty exception

  • Rag-doll sample loads, but isn't useable

  • Sample 16 isn't working

  • Sample 17 is missing some stuff

Contributing to waves

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet

  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it

  • Fork the project

  • Start a feature/bugfix branch

  • Commit and push until you are happy with your contribution

  • Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.

  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

Copyright

Copyright © 2014 Jeremy Woertink. See LICENSE.txt for further details.