Bump text

Author: monkstone

Diff for: _projects/jruby_art.md

@@ -8,11 +8,11 @@ keywords: 'propane, JRubyArt'
 
 ### Java
 
-We strongly recommend you use [AdoptOpenJDK][adopt] binaries.
+If you run in to trouble use [AdoptOpenJDK][adopt] binaries, there eas once an issue with OpenGL with some JDKs but that seems to have been resolved.
 
 ### JRuby
 
-With JRubyArt, there is the possibility of installing jruby-complete (using k9 --install), rather than install jruby on your system, you will need a vanilla ruby install and to configure `~/.jruby_art/config.yml` to run sketches. Otherwise install jruby (you do not need rvm or rbenv to this as jruby binary gets called directly).
+With JRubyArt, there was the possibility of installing jruby-complete (using k9 --install), rather than install jruby on your system, you will need a vanilla ruby install (but current MRI ruby may have compatability issues) and to configure `~/.jruby_art/config.yml` to run sketches. Otherwise install jruby (you do not need rvm or rbenv to this as jruby binary gets called directly).
 
 
 ## Understanding A JRubyArt Sketch
@@ -79,7 +79,7 @@ module Processing
 
     def draw
       # draw loop
-    end    
+    end
     # end bare sketch ###########################################
   end
   Sketch.new
@@ -88,7 +88,7 @@ end
 
 ### class_sketch.rb
 
-An explicitly class wrapped sketch can actually be run directly with `jruby`, but you should prefer [propane][propane] for that.
+An explicitly class wrapped sketch can actually be run directly with `jruby`, but you should prefer [propane][propane] or PiCrate for that.
 
 ```ruby
 # frozen_string_literal: false

Diff for: _projects/picrate.md

@@ -8,15 +8,15 @@ keywords: picrate, JRubyArt
 
 ### Java ###
 
-Unlike vanilla processing, we do not distribute a java environment with our projects. It is the expectation that you will use the default openjdk11 suplied with Buster on the RaspberryPI3B+ or RaspberryPI4.
+Unlike vanilla processing, we do not distribute a java environment with our projects. It is the expectation that you will use the default openjdk11 suplied with RaspberryPI OS or Manjarao ARM on the RaspberryPI3B+ or RaspberryPI4.
 
 ### JRuby ###
 
-With picrate you need to install jruby on your system (you do not need `rvm` or `rbenv` to do this since you call the jruby binary directly).
+With picrate you need to install jruby on your system (you do not need `rvm` or `rbenv` to do this since you call the jruby binary directly). On Manjaro ARM you can use pacman to do this.
 
 ## Understanding A picrate Sketch ##
 
-How you might write a picrate sketch, including the `shebang` makes it easier to run the sketch using `script` in the `atom` editor, but assumes you have jruby available at `/usr/bin/jruby` or more likely via symbolic link (yet another reason not to use `rvm` or `rbenv` since they futz with your environment).
+How you might write a picrate sketch, including the `shebang` which makes it easier to run the sketch using `script` in the `atom` editor, but assumes you have jruby available at `/usr/bin/jruby` or more likely via symbolic link (yet another reason not to use `rvm` or `rbenv` since they futz with your environment). However you will likely use geany or vim on your RaspberryPI (atom is not available).
 
 ### my_sketch.rb ###
 
@@ -73,8 +73,8 @@ module Processing
 
     def draw
       # draw loop
-    end    
-  end  
+    end
+  end
 end
 
 # NB: If you use this explicit form need to use PiCrate::MyApp.new to run sketch

Diff for: _projects/propane.md

@@ -8,7 +8,7 @@ keywords: propane, propane
 
 ### Java ###
 
-We recommend you use [AdoptOpenJDK][adopt] binaries.
+Most openjdks 11+ will now probably work. We recommend you try [AdoptOpenJDK][adopt] binaries if you run into problems.
 
 ### JRuby ###
 
@@ -73,8 +73,8 @@ module Propane
 
     def draw
       # draw loop
-    end    
-  end  
+    end
+  end
 end
 
 # NB: If you use this explicit form need to use Propane::MyApp.new to run sketch

Diff for: _testing/testing.md

@@ -5,17 +5,17 @@ title:  "Testing"
 
 ### Continous Integration ###
 
-[travis ci][travis], we are all set up to go and this would actually work if only the current version of processing was available from maven central
+[travis ci][travis]
 
 ### Platform Testing ###
 
-* Currently only linux64 bit gets proper testing (Archlinux and Debian/Mint)
-* Must be working on macOS (volunteers required), I know there are users and no-one complains
-* Windows I can only guess (no-one complains)
+* Currently only linuxAMD64 bit gets proper testing (Archlinux and Debian/Mint) for JRubyArt art and propane
+* RaspberryPI OS and Manjaro ARM also get full testing
+* Volunteers are required for Windows and MacOS, thought he probably work (_at least no-one complains_)
 
 ### Testing code ###
 
-In a sense every example sketch is a test, if the sketch runs (and they all have run at least once) then the tests are passing. In general sketches are not formally tested, but it would be no bad thing to create tests before [re-factoring][99]. There are _in the main_ tests written into ruby-processing projects, and we favor [minitest][minitest] over [rspec][rspec]. Note that if you are going to use rspec you should probably use `jruby -S rspec` to run your tests and include `require 'java'` in your specs. Static tests such as rubocop can also be useful, but you should be wary of some of the suggested changes to `working code`, there's some funky stuff hidden in JRubyArt code.
+In a sense every example sketch is a test, if the sketch runs (and they all have run at least once) then the tests are passing. In general sketches are not formally tested, but it would be no bad thing to create tests before [re-factoring][99]. There are _in the main_ tests written into ruby-processing projects, and we favor [minitest][minitest] over [rspec][rspec]. Note that if you are going to use rspec you should probably use `jruby -S rspec` to run your tests and include `require 'java'` in your specs. Static tests such as rubocop can also be useful, but you should be wary of following all the suggested changes to `working code`, there's some funky stuff hidden in JRubyArt code.
 
 [99]:http://www.sandimetz.com/99bottles/
 [minitest]:https://github.com/seattlerb/minitest/

Diff for: _welcome/welcome.md

@@ -3,7 +3,7 @@ layout: post
 title:  "The Ruby-Processing Group Site"
 ---
 
-This site is the home of the ruby-processing group, which exists to collect together projects that have evolved from the original [ruby-processing][ruby-processing] see about. New members are always welcome, but preferably leave any opinionated frameworks behind, this is emphatically not a __rails project__, and does not require __bundler__, __rvm__ or __rbenv__, use these tools (crutches) locally if you must (but don't blame me when they screw up, __as well they might__, just take a look at the screwy travis-ci stack traces of any build using jruby). At the simplest level there is always scope for developing spiffy new examples (ruby), but the recently created atom projects could also use some love (javascript / cson), where the possibilities far exceed my limited abilities. To develop [JRubyArt][jruby_art] or [propane][propane] a knowledge of java and polyglot maven builds would come in handy. Knowledge of current javascript (since coffeescript is slipping out of favor) would be handy to improve [atom-k9][atom-k9] and [language-jruby-art][language-jruby-art], atom is fast becoming the editor of choice for JRubyArt, propane etc. In general unit testing (minitest/JUnit) is preferred to rspec etc.
+This site is the home of the ruby-processing group, which exists to collect together projects that have evolved from the original [ruby-processing][ruby-processing] see about. New members are always welcome, but preferably leave any opinionated frameworks behind, this is emphatically not a __rails project__, and does not require __bundler__, __rvm__ or __rbenv__, use these tools (crutches) locally if you must (but don't blame me when they screw up, __as well they might__, just take a look at the screwy travis-ci stack traces of any build using jruby). At the simplest level there is always scope for developing spiffy new examples (ruby), but the recently created atom projects could also use some love (javascript / cson), where the possibilities far exceed my limited abilities. To develop [JRubyArt][jruby_art] or [propane][propane] a knowledge of java and polyglot maven builds would come in handy. Knowledge of current javascript (since coffeescript is slipping out of favor) would be handy to improve [atom-k9][atom-k9] and [language-jruby-art][language-jruby-art], atom is the editor of choice for JRubyArt, propane etc. In general unit testing (minitest/JUnit) is preferred to rspec etc.
 
 [ruby-processing]:https://github.com/jashkenas/ruby-processing
 [jruby_art]: https://ruby-processing.github.io/index.html

Diff for: about.md

@@ -14,7 +14,7 @@ There are three main projects [JRubyArt][jruby_art], [PiCrate][picrate] and [pro
 
 [Propane][propane] is a configuration free, complete version of ruby-processing (_does not require installed vanilla processing_) that depends on an installed jruby (_is slightly more experimental however since a modified PApplet is required with jdk9+ propane may take over in future_). Since propane-3.2.0, propane is compiled with jdk11, and thus jdk11 is a requirement.
 
-[PiCrate][picrate] is a standalone version targetting the [RaspberryPI][rpi], but it can be developed and run 64 bit linux.
+[PiCrate][picrate] is a standalone version targetting the [RaspberryPI][rpi], but it can be developed and run 64 bit linux, tested with Raspberry OS (32 bit) and Manajaro Arm (64 bit). Needs at least RaspberryPI3B+, currently works best on RaspberryPI4. Suggested ide geany.
 
 Other projects include the pbox2d gem (a gem wrapper around [jbox2d]), toxiclibs gem (a gem wrapper around [toxiclibs]) and geomerative gem (a gem wrapper around [geomerative]).
 

Diff for: gems.md

@@ -6,7 +6,7 @@ title:  "Gems"
 RubyGems is a package manager for the Ruby programming language that provides a standard format for distributing Ruby programs and [libraries][libraries] (in a self-contained format called a "gem"), a tool designed to easily manage the installation of gems, and a server for distributing them. In the main you can use most of these gems in ruby-processing projects, though some built with native extensions may not be usable with jruby, there are usually good and sometimes better java alternatives (including [gems built for jruby][jgem]). But there's more there are [gems][gems] that have been build exclusively for use with jruby-projects, that make it even easier to use processing libraries in JRubyArt and propane. There are gems to help with maven builds, publish web-pages (_jekyll and its github flavors_) that are used to bring you this content etc.
 
 #### Building a gem for use with JRubyArt / Propane ####
-The [arcball.gem][arcball] for propane, is a reasonable template for producing your own standalone processing library, that can be installed as a gem. You may also found my [guide to creating jruby-extensions][extensions] useful if you wish to stick to the 'jruby-extension convention' (my extensions and those created by jruby guys are sublety different we use `implements Library`, whereas proposed convention is to use `implements BasicLibraryService`). You could also look at other [gems built for jruby][jgem], which include more advanced features, there is no requirement to stick to convention, since both forms are likely to continue to be supported.
+The [arcball.gem][arcball] for propane and PiCrate, is a reasonable template for producing your own standalone processing library, that can be installed as a gem. You may also found my [guide to creating jruby-extensions][extensions] useful if you wish to stick to the 'jruby-extension convention' (my extensions and those created by jruby guys are sublety different we use `implements Library`, whereas proposed convention is to use `implements BasicLibraryService`). You could also look at other [gems built for jruby][jgem], which include more advanced features, there is no requirement to stick to convention, since both forms are likely to continue to be supported.
 
 [extensions]:https://github.com/jruby/jruby-examples
 [arcball]:https://github.com/ruby-processing/ArcBall