Thanks for this goes to Paul Irish. For a while now I've been trying to find a way to search for a value across multiple files that are loaded in a browser request. But every time I used the Search field in Chrome Dev tools, it would only search the current file. I'm talking about the highlighted search field below:

Yes - I know - my MSPaint skills suck. ;) As I said, that only searches the current file. If there are a bunch of JavaScript files in one request, you're screwed unless you feel like manually switching from one to another.

But it turns out there's another search form you can open with ctrl-shift-f (cmd-opt-f on OSX):

Not only will it search across all files (not just JavaScript), it supports case sensitivity and regex based searches as well.

Anyway - thanks again to Paul for sharing the tip and I hope it helps others.

Validating forms with JavaScript has been possible since the very beginning of time... or at least the introduction of LiveScript (the original name before the marketing drones got ahold of it). While it's not particular new or as exciting as Canvas based games, JavaScript form validation is one of the best uses of the language (imo) and something that can dramatically improve your user's experience. I recently had a reader ask how to do JavaScript form validation so I thought it might be nice to write up a simple tutorial. This is not meant to cover every possible way, of course, and will be a very manual approach (no frameworks or plugins!) to the problem. As always, I welcome folks comments and suggestions below.

I've done a few projects now that make use of PhoneGap's database support. Like most things in PhoneGap, it just plain works. But I've encountered a few things I thought could be done a bit easier, so I've built a simple utility class for my future projects. I thought I'd share it with folks and see if it would be useful for others.

The title says it all. The latest issue of Adobe's Inspire Magazine is out. There's lots of good content with the only low point being my own article (grin) on PhoneGap: Combining your web skills with PhoneGap to build mobile apps. Probably nothing new for folks who read my blog entries here.

Welcome to my third entry for my (what was at first) simple PhoneGap RSS reader. If you haven't yet, please be sure to read part 1 and part 2 so you have some context about how this application works. In this part, I'm going to tackle two enhancements suggested to me by my readers:

Passing on this job notice from Adobe. It is a contract position with the possibility of converting to full time.

We have an open contract position for a CF engineer that I was hoping you could post on your blogs.

Here are the requirements per the hiring manager:

• BS or advanced degree and 3+ years' experience, or equivalent knowledge.
• Experience in design and development of web applications with ColdFusion, Mach-ii, AJAX, JSON, XML
• Worked with and applied current web client-side technologies – JavaScript, CSS, HTML, etc.
• Experience working with highly trafficked, scalable web applications with product downloads
• Experience with Adobe AIR applications
• Knowledge of presentation, web, business and data access layers and their interactions
• Experience with web services protocols such as REST, SOAP, XML/RPC.
• Solid foundation in computer science fundamentals, object oriented, design techniques, + software engineering best practices
• Experience in Scrum/Agile software development methodology

Please send resumes to Kavitha Mattikalli kmattika@adobe.com

As a blogger, I write quite a few blog posts. I hate RTEs (Rich Text Editors) so I'll typically do most of any desired HTML by hand. Normally this isn't a big deal. My blogware can handle paragraphs and code formatting. I typically just worry about bold and italics. However, because I'm entering HTML manually, there's always a chance I could screw up. I've got a Preview feature on my blog but I rarely use it.

I'm a bit late to blog on this, almost three months late, but folks may want to check out Ryan Anklam's ColdFusion Koans. What are ColdFusion Koans? (Stealing this from his site...)

The ColdFusion Koans project is intended to teach ColdFusion syntax, techniques, structure, and tips and tricks through unit tests. Even if you are a seasoned ColdFusion developer the Koans can be a fun exercise to keep your skills sharpened. The Koans concept is nothing new, in fact, the Ruby Koans project is quite mature. Recently other languages, such as JavaScript, have also implement the technique.

Having recently taken a look at the Ruby Koans, I can attest to it being an extremely interesting way to learn a language.

I also encourage folks to take a look at this blog post from Grant Copley: (EDIT: Shoot, looks like his blog is down. Well, give it time and hopefully it will come back up.) How I Almost Ditched ColdFusion After 12 Years, Why I Wised Up, and What I'm Doing About It. It's a fascinating blog entry about a long-time CF developer who got frustrated, gave up on CF, and then came back.

I've had a simple CFGRID demo sitting in my local web server for a few months now and never got around to sharing it on the blog. Today I responded to user with another CFGRID question and figured it would be good to share them both in one example. (Plus, the code has been sitting in my test.cfm file all that time and I want to get rid of it. ;) So let's start with the first example - relating one cfgrid to another.

Yesterday I blogged my experiment with downloading files to a PhoneGap application. Today I decided to take my code and try it out on iOS. Along the way I discovered a little bug, and encountered the White List issue with iOS PhoneGap apps. As with the previous entry, please note that this could possibly be done better.