A node library for parsing SGF format game records into JavaScript and back again. Then use smartgamer to navigate and manipulate those game records.
For most projects, you'll just want to install smartgame locally and add it to your project's dependencies in package.json:
$ npm install --save smartgame
If you want (for whatever reason) to use smartgame anywhere, you can install it globally.
$ npm install -g smartgame
var sgf = require('smartgame');
var fs = require('fs');
// Grab an SGF file from somewhere
var example = fs.readFileSync('sgf/example.sgf', { encoding: 'utf8' });
var collection = sgf.parse(example);
// ... use the collection object however you want!
// ... when collection has been modified and you want to save it as an .sgf file
var collectionSGF = sgf.generate(collection);
fs.writeFileSync('new-example.sgf', collectionSGF, { encoding: 'utf8' });
Let's take a very simple SGF file as an example:
(;GM[1]FF[4]CA[UTF-8]SZ[19];B[pd];W[dp];B[pp](;W[dd])(;W[dc];B[ce];W[ed](;B[ch];W[jc])(;B[ci])))
The parse function would turn this into a JS Object that looked like this:
{
gameTrees: [
{
parent: <a reference to the parent object>,
nodes: [
{ GM: '1', FF: '4', CA: 'UTF-8', SZ: '19' },
{ B: 'pd' },
{ W: 'dp' },
{ B: 'pp' }
],
sequences: [
{
parent: <a reference to the parent object>,
nodes: [
{ W: 'dd' }
]
},
{
parent: <a reference to the parent object>,
nodes: [
{ W: 'dc' },
{ B: 'ce' },
{ W: 'ed' }
],
sequences: [
{
parent: <a reference to the parent object>,
nodes: [
{ B: 'ch' },
{ W: 'jc' }
]
},
{
parent: <a reference to the parent object>,
nodes: [
{ B: 'ci' }
]
}
]
}
]
}
]
}
You'll still have to read up a little bit on the way SGFs work, but the structure is a simple and straightforward representation of the SGF in JS form.
Want an easy way to navigate and manipulate that game? Check out smartgamer.
MIT
This parser began life as part of another project, but I thought it was useful enough to become its own module. Breaking it and the other components of that project out into individual modules has helped me improve the separation of concerns and make the project more approachable. It's the first NPM package I've written that's not a plugin for something else (ie, a Grunt plugin or Yeoman generator) and any criticisms or suggestions are welcome.