File: extlib/waitForImages/

Recommend this page to a friend!
  Classes of Emmanuel Podvin  >  iFSM Animation  >  extlib/waitForImages/  >  Download  
File: extlib/waitForImages/
Role: Auxiliary data
Content type: text/markdown
Description: Auxiliary data
Class: iFSM Animation
Animate elements with parameters from attributes
Author: By
Last change: Update of extlib/waitForImages/
Date: 1 month ago
Size: 2,056 bytes


Class file image Download


Important notes

Please don't edit files in the dist subdirectory as they are generated via grunt. You'll find source code in the src subdirectory!

Code style

Regarding code style like indentation and whitespace, follow the conventions you see used in the source already.


While grunt can run the included unit tests via PhantomJS, this shouldn't be considered a substitute for the real thing. Please be sure to test the test/*.html unit test file(s) in _actual_ browsers.

See the Why does grunt complain that PhantomJS isn't installed? guide in the Grunt FAQ for help with installing or troubleshooting PhantomJS.

Modifying the code

First, ensure that you have the latest Node.js and npm installed.

Test that grunt is installed globally by running grunt --version at the command-line. If grunt isn't installed globally, run npm install -g grunt to install the latest version. _You may need to run sudo npm install -g grunt._

_Note that in Windows, you may have to run grunt.cmd instead of grunt._

  1. Fork and clone the repo.
  2. Run `npm install` to install all dependencies (including grunt).
  3. Run `grunt` to grunt this project.

Assuming that you don't see any red, you're ready to go. Just be sure to run grunt after making any changes, to ensure that nothing is broken.

Submitting pull requests

  1. Create a new branch, please don't work in your `master` branch directly.
  2. Add failing tests for the change you want to make. Run `grunt` to see the tests fail.
  3. Fix stuff.
  4. Run `grunt` to see if the tests pass. Repeat steps 2-4 until done.
  5. Open `test/*.html` unit test file(s) in actual browser to ensure tests pass everywhere.
  6. Update the documentation to reflect any changes.
  7. Push to your fork and submit a pull request.