🔥 A DSL for the DragonRuby Game Toolkit.

A DSL is a "domain-specific language": code that lets you express something more effectively or concisely.

A Maw program starts with Maw!, which adds Maw's tick, init, and helper methods, as well as setting the output globals described above.

Maw encourages $state, $outputs, $gtk as the primary way to use GTK's args.state, args.outputs, and args.gtk, respectively.

These have been part of DragonRuby since at least version 2. They are easy to type, quicker to access, and stand out against other variables / method calls in your code

Maw adds shortcuts for the various output types:

$solids = $outputs.solids
$static_solids = $outputs.static_solids
$borders = $outputs.borders # etc

Previously, Maw added methods for each of these outputs: solids, borders, etc.

But $solids << foo, $state.hey = 123 is now the recommended way to use Maw.

Maw comes with a simple tick/init mechanism which offers a couple of benefits:

1. It does not need to receive args 🙃
2. It is block based, and lets you express your init and tick in a way that stands out from other code.
3. Pass a block to init to define logic that will execute on first tick, on reset, and any time you call init without a block in the future.
4. It offers this while being fully optional and backwards compatible with regular DR code!

Maw!

controls.define :reset, keyboard: :r

init {
    $state.background = [grid.rect, rand(255), rand(255), rand(255)]
}

tick {
    init if controls.reset_down?
    solids << $state.background
}

Maw offers Controls which lets you map keyboard, mouse and controller binds to action names, then check their state in a convenient way:

controls.define :quit, keyboard: :q
controls.define :debug, keyboard: :back_slash if development?
controls.define :attack, keyboard: :e, mouse: :button_left, controller_one: :x

Once you have defined :attack, now you can check e.g. controls.attack?, controls.attack_down?, controls.attack_held?, controls.attack_up?, controls.attack_latch?.

Checking the state of a control which hasn't been defined is considered normal.

Controls will create a stub (with no inputs bound), then:

• In development, log to help you discover and bind the action.
• In production, do nothing, assuming you have intentionally disabled it.

Maw!

time_ticks! # will print min, max, avg tick times every 5s

tick {
  sleep 0.005
}

Maw adds some helper methods, for example desktop?, development? (dev?), production? (prod?), tick_count.

A prominent helper is controls, which lets you define global controls without any ceremony:

Maw!

controls do
  define :quit, keyboard: :q
  define :jump, keyboard: :space
end

tick {
    exit if controls.quit?
    
    if controls.jump?
    end
    
    # This won't break the game, but will log to the console in dev
    # so you can prototype more quickly
    if controls.some_new_action?
    end
}

I recommend cloning, forking or downloading the MawStarter project to get started.

If you are using Smaug, you can "smaug run" inside the directory to run the game.

Don't forget to rename it to YourAwesomeProject first!

Otherwise, it can run like a regular DragonRuby project from inside dragonruby-folder/mygame.

To use Maw in an existing Smaug project, do smaug add maw.

Next, ensure your main.rb loads smaug.rb before any of your game code, e.g.:

require 'smaug.rb'
require 'app/requires.rb' # recommended place for any other requires (optional)
require 'app/game.rb'     # placing this last ensures deps load before game code

If you have any game code in main.rb already: move it to game.rb, cut and paste its requires into app/requires.rb then create a main.rb similar to the above in its place.

Then, add Maw! to the top of your app/game.rb

Your game should work as normal! But now you can get to work purging dropping annihilating every little args and args.outputs. in sight :-)

To use Maw in an existing non-Smaug DragonRuby project, first install Smaug (I'm kidding, but it would be your friend :-)...

Just copy lib/maw.rb into your game directory, then require it before your game code.

To do this, you might like to rename main.rb to game.rb, then put the following in main.rb's place:

require 'lib/maw.rb'
require 'app/game.rb'

Next, add Maw! to the top of app/game.rb. Your game should work as normal!

Now you can simplify your game code, dropping the need for args.

Simply update any references to args.outputs.foo to $foo, args.tick_count to tick_count, etc

If the args object is required, use $args, and drop the parameter.

Better yet:

def render_player(args)
  args.outputs.sprites << { ... }
end

# can become

def render_player
  $sprites << { ... }
end

If you have any questions about using Maw, message mooff on the DragonRuby GTK Discord and I'll be happy to help.

Maw is MIT licensed. A copy of the license is available in the root of the repository. If Maw is useful to you, consider becoming a GitHub Sponsor.

❤️‍🔥