For a while now, myself (and many others) in the ColdFusion community have been urging, begging, hell, pleading with developers to stop using UI tags in ColdFusion. Things like cfgrid, cfpod, etc, are easy to use, but in general lead to far more trouble than they are worth. I said this back in October of last year:
One of my favorite tools has just hit 3.0 - Edge Animate. New features in this release include:
I spent some time today converting an older ColdFusion site to static HTML (I'll talk more about that tomorrow) and I thought I'd share some tips that may help others.
I ran into this today while looking at Chrome's docs for storage APIs. If you enter chrome://settings/cookies into the address bar (sorry, "omnibox" just seems like a 1980s X-Man name) Chrome will give you a report of storage data for every site that has made use of any form of storage within your browser. This report covers cookies (obviously), local storage, WebSQL, IndexedDB, and AppCache.
Ok, I apologize, that title is complete link bait, but I figured I'm allowed to have some fun every now and then, right? At least I didn't call it, "This Developer tried AngularJS and you won't believe what happened next!" About three years ago I blogged about AngularJS and how I thought it was kind of cool. This was before the 1.0 release. When 1.0 came out... it had changed. I didn't like it. It was hard to describe why I didn't like it. It had definitely gotten more complex and I just had a hard time wrapping my head around it.
This is just a quick note to discuss something interesting a reader and I encountered last week. As you know (hopefully!), the input tag supports a pattern argument. The value of the pattern argument is a regular expression that is compared against the value of the input field. This allows for custom types of validation for data not covered by the host of new field types added in HTML5.
A few weeks ago I blogged about HarpJS, a static site builder that lets you have the benefits of a dynamic web app during development and the simplicity of a static site for deployment. I've been thinking about Harp, and tools like it, quite a bit since then (see my recent article for flippin' awesome) and I decided to try a few things during the break. What follows is a proof of concept, an experiment, please note that there are probably far better ways to do what I did, but on the off chance this may help others, I thought I'd share.
The final part of my series on IndexedDB was just published on NetTuts: Working with IndexedDB - Part 3.
Imagine you have some code that is being fired right before, or during, a click that leads you to another page. If you use the console than you are in luck. Both Chrome and Firefox have options to preserve the console on navigation. In case you've never seen it, here is the option in Chrome. You find this by opening the Dev Tools and clicking the gear icon in the lower right hand corner.