MesaScript | based language that provides a powerful way | Application Framework library

MesaScript is now available as a gem! Assuming you have the gem command up and running (you probably do, but if not, check out [RubyGems](https://rubygems.org) to get it up and running). Simply run. and you should be good to go. You’ll be able to include MesaScript in your ruby files with require 'mesa_script', and inlist2mesascript will be available to you from the command line to convert your existing inlists to mesascript files. If you want to edit the source or don’t want to use rubygems, clone or otherwise download the repository somewhere to your home directory with. or somewhere else to your liking. Then, either copy the file mesa_script.rb to somewhere along Ruby’s path, or set up another stand-in file that points to your mesa_script.rb file in Ruby’s path. To find Ruby’s path, type. in your terminal. If Ruby is properly configured, as it is on most modern Unix systems, you should see a list of possible directories. Either copy mesa_script.rb there or do what I do and make a new file called mesa_script.rb there and have it just be. This way, if you later update your repo via git pull, you won’t need to copy mesa_script.rb again. Also, if you’d like to use the included (optional) inlist2mesascript tool, copy that to somewhere along you system’s path ( echo $PATH). Then type inlist2mesascript -h to learn more about that tool. As you might guess, it takes an existing MESA inlist and converts it to a file in MesaScript that, if executed by Ruby should produce essentially the same inlist (good for moving a project to MesaScript). To check if Ruby can see the file, try doing ruby -e 'require "mesa_script"'. If no error occurs, it is working fine. Finally, you must have your MESA_DIR environment variable set for anything to work. The mesa_script.rb file generates all the necessary data it needs from the MESA source on the fly (this also makes it nearly MESA version independent).