README.md in jruby_art-0.2.0.pre vs README.md in jruby_art-0.2.1.pre
- old
+ new
@@ -1,11 +1,11 @@
## JRubyArt
+[](http://badge.fury.io/rb/jruby_art)
+Is a development fork of [ruby-processing][] that has a somewhat independent existence, see [processing-core][] at least in the short term. Plan was that JRubyArt releases (pre-releases) would use jruby-9.0.0.0 from the start, but now I think it might be more sane to start with jruby-1.7.18. Version 0.2.0.pre is now available from rubygems. To build from repo:-
-Is a development fork of [ruby-processing][] that may soon have a somewhat independent existence, see [processing-core][] at least in the short term. Plan was that JRubyArt releases (pre-releases) would use jruby-9.0.0.0 from the start, but now I think it might be more sane to start with jruby-1.7.19. However until that time:-
-
You should (like ruby-processing) install [processing-2.2.1][]
Then create a `~/.jruby_art/config.yml` config file, here is
what mine looks like on arch-linux
@@ -55,11 +55,12 @@
k9 setup install # requires wget (Now also downloads examples to users home)
```
To run sketches with jruby-complete (rather than installed jruby)
```bash
-k9 run my_app.rb # NB: k9 setup install, is a one-time install to gem procedure
+k9 run my_app.rb # NB: k9 setup install, is a one-time 'install to gem' procedure
+that also downloads and install samples in examples folder in users directory
```
[Contributing][]
[License][]
@@ -70,10 +71,14 @@
[CHANGELOG][]
###Ruby Versions
-jruby-9.0.0.0.pre1+ (when sketches run with jruby command)
+jruby-1.7.18 (when sketches run with jruby command)
+
+jruby-9.0.0.0.pre1 also seems to work
+
+or
ruby-2.1.2+ (when sketches are run using k9 command, ie using jruby-complete)
[Acknowledgements]:ACKNOWLEDGEMENTS.md
[CHANGELOG]:CHANGELOG.md