Due to a problem back home, I have to leave the conference early. I'm giving my Mobile Web Debugging session in the first slot this morning (this schedule change will be announced this morning). Dave Ferguson will be covering my CF10+HTML5 session and Matt Gifford will be covering my PhoneGap session.

Passing it on... My name is Derek Bowes and I used to run whousescoldfusion.com and twitter is @whousescf. I am currently working for healthendeavors.com and our Health Care application uses CF10 with SQL 2008. We need more CF developers and are having a hard time finding good ones. They need to be on site in our Scottsdale, AZ office and we would be willing to pay to relocate the right candidate (US relocation only). Need someone mid-senior, with jQuery and JavaScript. If you could put the word out, it would be greatly appreciated. I can be reached at derek@healthendeavors.com.

I've come across multiple people lately who have been bitten by this so I thought a quick blog post would be useful for me readers. If you've recently upgraded your ColdFusion server or patched it, you may find some forms return an error when submitted. Here is an example: To cause this error, I simply created a form with 101 fields like so: If you modify the loop to go to 100 instead of 101, it works fine. People using ColdFusion 10 or a recently patched ColdFusion 9 will encounter this. The cause is a recent security fix. You can read the details here (Adobe ships patch for ColdFusion flaw that could lead to DoS attacks), but most likely you are only concerned about how to get around this. In the ColdFusion 10 Administrator, under Settings, way at the bottom, you will find this new setting: You can tweak this to a value that makes sense for your form. For folks using ColdFusion 8 and 9, you have to edit a bit of XML to handle this. Details may be found here: ColdFusion Security Hotfix

Ok, maybe "poetic" is a bit much... but you can listen to my Nerd Radio interview here: MAX Day 3: Ray Camden and Stupid Questions Ray Camden, Adobe Creative Cloud Evangelist, talks with us about his sessions at MAX covering topics like PhoneGap Build and web development tools. Thanks to Leif and and Garth for inviting me!

It has been a few weeks (ok, a few months) since my last blog post on JavaScript design patterns. I'd apologize, but frankly, it will probably be a few more weeks until I blog on this subject again, so hopefully people aren't expecting a fast series here (grin). As a reminder, the idea behind this series is to create real, practical examples of various JavaScript design patterns based on the book, "Learning JavaScript Design Patterns" by Addy Osmani. (See my review here.) In this blog entry I'll be discussing the Revealing Module pattern.Addy Osmani describes the Revealing Module pattern as: The Revealing Module pattern came about as [Christian] Heilmann was frustrated with the fact that he had to repeat the name of the main object when he wanted to call one public method from another or access public variables. He also disliked the Module pattern's requirement of having to switch to object literal notation for the things he wished to make public. There's two main issues here. First, the concept

This year was my second MAX as an employee and was both exciting - and pretty tiring. If you weren't able to make it though there is an easy way to catch what you missed.Keynotes Monday's keynote was focused on our product announcements and featured our first hardware announcements ever - Mighty and Napoleon. If you haven't heard yet, Creative Suite is now Creative Cloud. You can find out more at the FAQ or feel free to just ask me. By the way - the hardware announcements were a complete surprise to me! Tuesday's keynote was cool as well. It focused on four different creatives discussing their process and showcasing their work. Sneaks There isn't a filtered list of the sneaks yet, and it looks like they aren't even all online (there were 12 total), but if you go to the AdobeCreativeCloud channel on YouTube, you can find a playlist called Adobe Max 2013. In this playlist are 6 of the 12 sneaks. Unfortunately, both of the Brackets sneaks are not there. I'm going to do a separate blog po

As a User Experience (UX) designer, I spend a lot of time with pen and paper, sketching interfaces, testing ideas, and fleshing out use-case workflows. I work exclusively in grayscale. This holds true for both sketching and digital prototyping. On paper, I use a black pen (Pilot Precise Grip, Bold) on white, unruled paper; on the computer, I use a single font-face (Helvetica Neue LT Std) and about 5 different shades of gray. ... Read More »

Oddly, the last of my Adobe MAX sessions is available online now but none of my earlier ones. I assume they will show up in the next day or so. But for now, enjoy my eloquent presentation on the more advanced aspects of using PhoneGap Build. You can download the source code for the sample apps and slide deck as well. As always, I hope this is helpful!

Someone came up to me after my MAX session on web development debugging and asked for some advice on how to 'sell' unit testing to his clients. This was my response: Simple. Tell the client you feel unit testing is so important that you're willing to talk about it with him face to face. In fact, you'll even fly him to your location. In order to save money though you're going to use a budget airline that skips testing.

Many moons ago I blogged about a proof of concept I built that allowed you to view Edge Inspect screen shots via a nice web interface. This was built in Node using the Express framework. I've finally gotten around to doing some updates to it as well as pushing it up to Github.First, I applied the Topcoat UI framework. This is an open source UI framework for desktop and mobile available for forking on Github. Here is a screen shot of the app in action: And here is a shot of the detail view (I'd like to add a bit more detail here): New features include the ability to filter by operating system or device. Here's a filter on Android: So, like it? As I've said before, I'm still rather new to Node so take this code with a grain of salt. You can download (or fork and improve!) here: https://github.com/cfjedimaster/inspectviewer