README.md

grunt-nomnoml

This module provides a grunt multi-task generating images from nomnoml diagram sources.

If you generate HTML technical documention from textual sources, you may want to maintain only sources of UML diagrams in your repository and generate the pictures only during the documentation build. You will be able to do changes easily, without committing both diagram sources and pictures and sychronizing them manually.

If you want to just quickly convert a nomnoml source file to a picture, you can use the nomnoml-cli command-line tool, which this task is based on.

Installation

You need node >= 0.12, npm and grunt >= 0.4 installed and your project build managed by a Gruntfile with the necessary modules listed in package.json. If you haven't used Grunt before, be sure to check out the [Getting Started] guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may ensure native dependencies of this plugin and install it:

1. Install pre-requisites of the node-canvas module depending on your operating system

2. Install the Grunt task:

$ npm install grunt-nomnoml --save-dev

Configuration

Add the nomnoml entry with the nomnoml task configuration to the options of the grunt.initConfig method:

grunt.initConfig({
  nomnoml: {
    one: {
      files: {
        'dist/doc/images/diagram.png': ['doc/images/diagram.nomnoml']
      }
    },
    all: {
      src: ['doc/images/*.nomnoml']
      dest: 'dist/doc/images'
    }
  }
});

The configuration consists of key-value pairs with the output image path as a key pointing to the nomnoml input file. If you specify more source files by wildcards, the destination should be a directory; the source file extension wil lbe replaced by "png" in the output file name.

Then, load the plugin:

grunt.loadNpmTasks('grunt-nomnoml');

Build

Call the nomnoml task:

$ grunt nomnoml

or integrate it to your build sequence in Gruntfile.js:

grunt.registerTask('default', ['nomnoml', ...]);

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

• 2016-01-09 v0.2.1 Support wildcards in the source file input
• 2016-01-09 v0.1.1 Fix e-mail, update dependencies and copyright year
• 2015-08-08 v0.1.0 Initial release

License

Copyright (c) 2015-2016 Ferdinand Prantl

Licensed under the MIT license.