Difference between revisions of "Ruby"

From RogueBasin
Jump to navigation Jump to search
 
Line 17: Line 17:
As people begin to use Ruby for RL development, code will surface. There are already a few algorithms implemented and put up at RogueBasin.
As people begin to use Ruby for RL development, code will surface. There are already a few algorithms implemented and put up at RogueBasin.


Cross-platform, true curses support can be achieved using <b>ncurses</b> (see below)
Cross-platform, true curses support can be achieved using [[NCurses]] (see below).


==Okay, I'm going to use Ruby. What now?==
==Okay, I'm going to use Ruby. What now?==

Revision as of 19:24, 18 May 2009

Ruby

Ruby is still coming of age in the roguelike field -- there are no roguelike libraries and only a few finished games in the language. That said, Ruby is very powerful, combining an elegant syntax with an incredibly dynamic object system. It's also incredibly fun to code with. But beware! Many dangers lurk within beneath its alluring facade!

Reasons not to use Ruby

  • Speed: Ruby 1.8 measures far below Python in terms of performance. This is mostly due to Python having a bytecode compiler. On the other hand, Ruby 1.9 has JIT compilation and out-performs Python.
  • Documentation: The language is not well documented in relation to other languages, but this is getting better all the time. There are quite a few gotchas (like using setter= methods inside of classes).
  • Libraries: Ruby has no roguelike library, nor are there many (if any) roguelike sources to borrow from. Built-in Curses support has no colors under Windows and is generally a mess.

But!

The first two of these issues will be fixed by the time your roguelike is finished :)

As people begin to use Ruby for RL development, code will surface. There are already a few algorithms implemented and put up at RogueBasin.

Cross-platform, true curses support can be achieved using NCurses (see below).

Okay, I'm going to use Ruby. What now?

You'll need to install a copy of Ruby 1.8 from http://www.ruby-lang.org/ (I recommend the one-click installer) or your package manager (apt-get install ruby). Then acquaint yourself with the Ruby tools: irb, ri and rdoc. A good version of the standard library API can be found at http://www.noobkit.com/

ncurses-ruby

It is possible to use the built-in curses on linux and other platforms, and interface with the Win32 console via the Win32 API for Windows support. However, this is a relative pain. Instead, install the non-standard ncurses-ruby package!

On Windows:

  • Download ncurses-ruby1.8-0.9.1-i386-mswin32.zip from http://ncurses-ruby.berlios.de/
  • Copy lib/ncurses.rb and ncurses.so into your code directory (don't copy the lib directory itself!)
  • In your script, require 'ncurses'

That's it! You can now use ncurses (see the zdennis's ncurses examples at http://github.com/zdennis/ncurses_examples/tree/master or the C API, which is very similar). At some point an example roguelike using ncurses will be uploaded.

Field of View

A few field of view algorithms have been implemented in Ruby

Bitfields

For certain intensive operations it may be prudent to use a Bitfield. One example is storing which map tiles have been visited by your player (and will be drawn).

Using this library, it is easy to add methods to your Map class for FOV calculation:

def initialize(map)
    ....
    @visited = BitField.new(@width * @height) # visited by player (drawn in grey)
    @lit = BitField.new(@width * @height) # seen by player this round (drawn in white)
end

# Return true if the square is lit (seen by player)
def lit?(x, y)
    @lit[y * @width + x] == 1
end

# Returns true if square has been visited by player
def visited?(x, y)
    @visited[y * @width + x] == 1
end

# Set lit status for square. Also visits the square
def light(x, y)
    idx = y * @width + x
    @lit[idx] = @visited[idx] = 1
end

# Unlight everything (call after doing FOV calc + map draw)
def reset_light
    @lit.clear
end