jPaq News November 24th, 2015 @ 1:09:44

YourJS is finally here to replace jPaq. August 1st, 2014 @ 4:58:25

I am finally getting back to working on jPaq!  One thing I realized is it is time to have a domain that is more appropriate for a JavaScript utility library that you design.  I'm happy to announce that jPaq is available via

Removing Color.random() July 28th, 2011 @ 1:14:43

One of the things that I am removing from jPaq is Color.random(). The reason I am removing this is because I am adding hue, saturation, and lightness support. In addition, I am making it so that the r(...), g(...), b(...), a(...), h(...), s(...), and l(...) functions will accept a range of two numbers so that a random number in that range will be picked. With these updates on the horizon, anyone that currently uses Color.random() will find that these updates make this function a thing of the past.

Examples April 4th, 2011 @ 6:39:17

I am happy to announce that I finally have an examples section for this site.  As of right now, there are still some features that I would like to add, but I think the current layout will suffice for the time being.  On each example page you will find a description of the example and the code.  In many cases, the code will be accompanied by an execute button which will allow you to execute the code directly on the page.  If you would like to know how to use jPaq, please check out the examples page.

Next Version of jPaq March 31st, 2011 @ 7:25:33

I have been working hard for the past two months on thinking of what should be added to jPaq and how these things should be implemented.  I finally have most of the functions coded.  The next version of jPaq will definitely introduce cool functions that do a lot with a little bit of code.  In addition, I am going to try to add more DOM support to the next version.  In order to do this, I plan on using John Resig's Sizzle selector engine.  This is supposedly the same selector engine that jQuery runs on in order to select DOM elements by using CSS (1-3) selectors.  As of right now, the plan is to allow you (the user) to choose whether or not you want the Sizzle Selector Engine.  If selected, all of the additional DOM functions, such as the event handling functions and attribute functions will be attached to the instance of the jPaq class that will be returned from the selector function.  When everything is said and done, this version of jPaq will be what JXtension should have been.  As usual, what makes all of this even better is the fact that you will still be able to pick and choose which features you want in your version of jPaq.

More News:  12