JavaScript

I came across this article from the jQuery blog, talking about future updates to version 1.9 and 2.0. jQuery 1.9 (early 2013): We’ll remove many of the interfaces already deprecated in version 1.8; some of them will be available as plugins or alternative APIs supported by the jQuery project. IE 6/7/8 will be supported as today. jQuery 1.9.x (ongoing in 2013 and beyond): This version will continue to get fixes for any regressions, new browser bugs, etc.

Rounded Intro

So you’re all grown up and want Rounded Corners on your site. There’s just one small problem: the normal rounded corners implementation comes with tons of divs used for styles and you’ve got your fellow web developers screaming down your neck about web semantics.

So what’s this funky semantics thing? Basically, we’re looking for a separation of styles and data. We want to keep all the styles in the CSS style sheets and all the data in the XHTML files. Now, I’ve been known to be flexible on this a bit, however it is a great idea with a purpose and in this case, it actually helps us out a ton.

Ignore Me - Take The Easy Way Out

There are two jQuery plugins that can do this instantly, aptly named jQuery Corners and jQuery Corner. Yeah, I know totally different, right? They vary slightly in terms of their capabilities (anti-aliasing, background images, etc.). So if you’re not up to the heavy lifting or your requirements are very light (just basic rounding) these plugins more than fit the bill.

Now, it’s no secret that I can be a moron sometimes, but I’d like to put it on record that it was all me and not WordPress 2.7 that had the issue. So I’m sitting here last night minding my own business and Chris Coyier sends out a tweet talking about how it took him 10 minutes to upgrade. So I figure, why not? I already had the WordPress Automatic Upgrade plugin ready to go, so I figured it would be a breeze.

Introduction Before I even start, let me state that I’m a JQuery fan. Ever since I’ve started with JavaScript frameworks I’ve weighed the pros and cons, and trust me there are a lot. You’ll always find people arguing Prototype, JQuery or MooTools. I went with JQuery because it could do all that I wanted with the least amount of bloat. I’m sorry, Prototype may do a hell of a lot, but I don’t think that I could make enough use or that 100 KB to justify it.

One of the nice things about CakePHP is that it includes ready to use CSS compression. Granted, compressed CSS can be buggy at times, but for the most part it works just fine. I’ve always wondered why no one has included something like this for Javascript, since that’s usually the bigger culprit when we’re talking about document size. I’ve tried using Minify in the past. However, it took a lot to get it working right.

One thing which I usually find quite annoying is using input boxes in forms for user entered dates. Having the user manually enter date, day, month, year seems so 1997 to me. However in the interest of time, this is what most programmers slap into the web applications simply because it’s easier to produce and easier to maintain. Well here’s a handful of solutions that can solve that problem for you.