jmontoyaa 0030835069 move assets to public new symfony structure		7 년 전
..
dist	0030835069 move assets to public new symfony structure	7 년 전
libs	0030835069 move assets to public new symfony structure	7 년 전
src	0030835069 move assets to public new symfony structure	7 년 전
test	0030835069 move assets to public new symfony structure	7 년 전
.bower.json	0030835069 move assets to public new symfony structure	7 년 전
.gitignore	0030835069 move assets to public new symfony structure	7 년 전
.jshintrc	0030835069 move assets to public new symfony structure	7 년 전
Gruntfile.js	0030835069 move assets to public new symfony structure	7 년 전
LICENSE-MIT	0030835069 move assets to public new symfony structure	7 년 전
README.md	0030835069 move assets to public new symfony structure	7 년 전
ajaxQueue.jquery.json	0030835069 move assets to public new symfony structure	7 년 전
package.json	0030835069 move assets to public new symfony structure	7 년 전

jQuery Ajax Queue

Which files to use?

The release version of the code is found in the dist/ directory.

In your web page:

<script src="jquery.js"></script>
<script src="dist/jquery.ajaxQueue.min.js"></script>
<script>
jQuery.ajaxQueue({
	url: "/ajax",
	dataType: "json"
}).done(function( data ) {
	// ...
});
</script>

Documentation

`jQuery.ajaxQueue( options )`

Takes the same parameters as jQuery.ajax, returns a promise. Note that the return value is not a jqXHR, but it will behave like one. The abort() method on the return value will remove the request from the queue if it has not begun, or pass it along to the jqXHR's abort method once the request begins.

Examples

(Coming soon)

Release History

v0.1.1 - 2013-01-16
- Changed keywords in package file
v0.1.0 - 2013-01-16
Started as an answer on Stack Overflow.

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.

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.
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.

PhantomJS and Mac OS X
PhantomJS Installation (PhantomJS wiki)

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

README.md