jQuery is great. It provides solid core features that let you do magic while serving as the foundation for the simplest or most complex plugin. It's no surprise then that there are countless plugins out there, for free, which are supposed to save you time and headaches. I gotta say though that I've never gone wrong in rewriting my own plugin from scratch to meet my specific needs. Why? Because most jQuery plugins try to do too much - they take too many options, support too many use cases, and, as a consequence, are bloated, slow and hard to change.
I'm not saying these plugins are bad (the official jQuery UI or any other). No doubt they handle a bunch of things that I haven't even considered, including accessibility, cross browser support, multiple languages and so on. But oftentimes you don't need all that stuff, or at least not most of it. A plugin that supports 45 languages and is fully accessible isn't worth much to me if its painfully slow and I just care about english.
This is why I don't generally make my plugins available, unless I'm specifically asked. For me, plugin development is fun and relatively easy..so why not spend 3 hours building the perfect grid specifically for my system if the outcome is massive performance increases on some of our clients low end desktops?
There's 1 plugin type I told myself I'd never write: date picker. But I needed something to pick a range for the reporting UI of mogade, and I thought to myself, I might as well try and write it myself (in the past I've used and been happy with this one). It ended up being easier than i thought for my very simple needs. It works in Chrome, Firefox and IE 8. Does it work in IE 6, 7 or 9? I don't know nor do I care. Does it support X or Y or Z? No.
What it does do is provide the most basic components of a date range picker. To me, this is how plugins should be. Rather than add every feature imaginable and making it difficult for developers to change the behavior to meet their needs, build a smaller and more focused core and let developers add to it as needed. A visual plugin, to me, is like a design pattern...it should be a start.
So the datePicker is available on github. And here's what it looks like:
Date constructor is clever about things like day 0 or month 12. So if you are on month 11 (December, 0 based) and you want to get the 1st of the next month, you can just do new
Date(currentDate.getFullYear(), currentDate.getMonth()+1, 1); and the year will roll over. Getting the last day of a month is as simple as:
Date(currentDate.getFullYear(), currentDate.getMonth()+1, 0). Also, I forgot that IE doesn't let you set the
innerHTML of table/tr/td elements. That's just stupid. And, for the first time ever, I had a jQuery selector not work in IE but work fine in all browsers:
td:not([colspan]) always returns an empty set in IE...I saw other posts which seem to confirm the issue.
Anyways, enjoy, and remember, favor plugins that let you add the features you want rather than those which tried to anticipate your every need.