noty is a jQuery notification plugin that makes it easy to create alert - success - error - warning - information - confirmation messages as an alternative the standard alert dialog.
JavaScript HTML CSS
Latest commit 6fe2cf8 Jan 11, 2016 @needim fix for #302
Permalink
Failed to load latest commit information.
demo fix for #302 Jan 11, 2016
js/noty fix for #302 Jan 11, 2016
.gitignore MaxVisible option for all layouts. Jul 3, 2013
Gruntfile.js v2.3.7 Sep 14, 2015
LICENSE.txt Added license file. Apr 27, 2012
README.markdown Fix logo url in README.markdown Dec 25, 2014
bower.json v2.3.7 Sep 14, 2015
composer.json v2.3.5 Apr 6, 2015
noty.jquery.json fix for #302 Jan 11, 2016
package.json fix for #302 Jan 11, 2016

README.markdown

noty - A jQuery Notification Plugin

noty v2 logo


Hi

noty is a jQuery plugin that makes it easy to create alert - success - error - warning - information - confirmation messages as an alternative the standard alert dialog. Each notification is added to a queue. (Optional)

The notifications can be positioned at the; top - topLeft - topCenter - topRight - center - centerLeft - centerRight - bottom - bottomLeft - bottomCenter - bottomRight

There are lots of other options in the API to customise the text, animation, speed, buttons and much more.

It also has various callbacks for the buttons, opening closing the notifications and queue control.


Documentation

Documentation and examples are here: http://needim.github.io/noty


Pull Requests

  1. Fork the project, clone your fork, and configure the remotes:

    # Clone your fork of the repo into the current directory
    git clone https://github.com/<your-username>/noty.git
    # Navigate to the newly cloned directory
    cd noty
    # Assign the original repo to a remote called "upstream"
    git remote add upstream https://github.com/needim/noty.git
  2. If you cloned a while ago, get the latest changes from upstream:

    git checkout master
    git pull upstream master
  3. Create a new topic branch (off the main project development branch) to contain your feature, change, or fix:

    git checkout -b <topic-branch-name>
  4. Commit your changes in logical chunks. Please adhere to these git commit message guidelines or your code is unlikely be merged into the main project. Use Git's interactive rebase feature to tidy up your commits before making them public.

  5. Locally merge (or rebase) the upstream master branch into your topic branch:

    git pull [--rebase] upstream master
  6. Push your topic branch up to your fork:

    git push origin <topic-branch-name>
  7. Open a Pull Request with a clear title and description against the master branch.

IMPORTANT: By submitting a patch, you agree to allow the project owners to license your work under the the terms of the MIT License.