- As a user, Inform's syntax is kind of batty and hard to predict. It only looks like English.
- As an implementor, I have no idea even where to start with an Inform7 parser.
Currently, there are five files that load up the test environment:
- World.js - the main Grue library, which implements the base prototypes and utility functions.
- BaseRules.js - contains the main parser vocabulary for my test game. This will eventually become a generic ruleset that people can build on.
- test.js - builds a small, familiar scene using Grue, as a way of testing the environment.
- almond.js - a small AMD loader by James Burke, used by Grue to load the base ruleset without strongly coupling them together.
- index.html - loads all of the above, and provides a retro-styled interface for the Grue console.
You can view a live version of the current Grue test environment by visiting the demo page.
My current approach is to write in test.js according to the API I want to see, then do work in the other files to make that API occur--a kind of test-driven development, I guess. I still have to do a bit more work before everything is stable, but at the moment it's enough to build rooms, populate them with objects, and connect them to each other.
this space intentionally left blank.