Another two-do list for your brower's "new tab" feature, this with a list of things you should not do. #complete http://priorities.elfsternberg.com/
Go to file
Elf M. Sternberg f09acdbf9b Pretty much the final product. 2012-07-16 11:20:23 -07:00
assets Pretty much the final product. 2012-07-16 11:20:23 -07:00
bin Starting the styling. 2012-07-14 18:03:03 -07:00
src Pretty much the final product. 2012-07-16 11:20:23 -07:00
test Fixing test order. 2012-07-10 10:14:47 -07:00
.gitignore gruntjs written in coffee. Nice. 2012-07-14 10:43:43 -07:00
LICENSE-CC-Attribution-NonCommercial-ShareAlike Initial check-in; some gruntwork. 2012-07-09 13:16:06 -07:00
PriorityIgnore.json Initial check-in; some gruntwork. 2012-07-09 13:16:06 -07:00
README.md Initial check-in; some gruntwork. 2012-07-09 13:16:06 -07:00
grunt.coffee Pretty much the final product. 2012-07-16 11:20:23 -07:00
grunt.js Pretty much the final product. 2012-07-16 11:20:23 -07:00
package.json A *bad* workaround for dealing with Zombie's sizzle monkeypatch by specifying discordant JSDom versions. But no alternative other than specifying JSDom outside the package.json makes sense. 2012-07-10 10:00:49 -07:00

README.md

Priorityignore

A simple program to show/hide priorities.

Getting Started

Download the production version or the development version.

In your web page:

<script src="jquery.js"></script>
<script src="dist/PriorityIgnore.min.js"></script>
<script>
jQuery(function($) {
  $.awesome(); // "awesome"
});
</script>

Documentation

(Coming soon)

Examples

(Coming soon)

Release History

(Nothing yet)

License

Copyright (c) 2012 Elf M. Sternberg
Licensed under the CC-Attribution-NonCommercial-ShareAlike license.

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.

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!

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.

Installing grunt

This assumes you have node.js and npm installed already.

  1. Test that grunt is installed globally by running grunt --version at the command-line.
  2. 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.
  3. From the root directory of this project, run npm install to install the project's dependencies.

Installing PhantomJS

In order for the qunit task to work properly, PhantomJS must be installed and in the system PATH (if you can run "phantomjs" at the command line, this task should work).

Unfortunately, PhantomJS cannot be installed automatically via npm or grunt, so you need to install it yourself. There are a number of ways to install PhantomJS.

Note that the phantomjs executable needs to be in the system PATH for grunt to see it.