QuackFuzed.com is the personal ColdFusion coding blog of Matt Quackenbush. It exists primarily as a place for the author to learn, and hopefully to assist others in learning and/or avoiding some of the same pitfalls and mistakes. (Quack certainly makes enough mistakes daily to make up for the entire ColdFusion community.)
If you have not yet registered for cf.Objective(), hurry up and do so. Time is running out. If you have already registered, be sure to set your itinerary. Below is my tentative itinerary.
I've attended seemingly a million conferences over the years of my career, and had gotten to a point where they just really didn't do anything for me, so I quit attending. After about a 7 year break from any conferences, I decided to take a chance on cf.Objective(), because I felt that the material and the speaker lineup were stellar, and that the conference's primary agenda was education rather than corporate sales. I can unequivocally say that my assessment was 100% accurate. There is one conference and one conference only that is now on my calendar each year: cf.Objective().
Now hurry it up and get registered!
Several years ago I had a major hard drive crash, and lost my former "big name" IDE. After asking around to see what was available, I was repeatedly referred to CFEclipse. While it took some getting used to at first (what "new" thing doesn't?), I have been off and running with it ever since.
Luis Majano recently announced that ColdBox 2.5.2 and the new website has been released. Be sure to check out the What's New? guide for all of the new features.
Simply put, I continue to be amazed at how powerful a framework ColdBox is, and how pleasurable it is to build applications on it. Thank you again to Luis and Team ColdBox for all of your hard work!
Simple question: In terms of usage amongst the ColdFusion community, is Pownce dead? Sure seems to be to me. With CFCommunity, who needs it? I'm curious to hear your take on it.
While I've been writing ColdFusion for over 10 years now, I am a relative newcomer to the world of writing my own custom tags. I know, odd; but it is what it is. On occasion, I run into a particular behavior with <cfexit /> that perplexes me greatly, and I'm hoping that someone can help shed some light on it for me.
In my original post releasing the tag library I said that I'd post more as I had time to do so. I figured that today I'd take a short break from what I've been working on and write something up.
First, I should point out that there have been a couple of changes made, so the download has been updated. Be sure to get the latest files. The changes mostly involve textareas: (a) I had forgotten to output the provided value, and (b) I updated the fieldset.cfm and field.cfm files to trim() any content generated by the tags. (The trim() is not mission-critical, just cleans up the resultant HTML a little bit.)
So, without further ado, let's get to it.
ColdBox 2.5 now has native support for Adam Fortuna's ColdCourse project. Man, this stuff is totally awesome! Prior to the last few days of digging into 2.5, I had only had a chance to casually glance at ColdCourse. Thanks to Luis Majano and Russ Johnson for working hard to get ColdCourse implemented.
Now, instead of having a URL like this one...
If you have not yet taken a look at the latest ColdBox release, 2.5.1, I really recommend that you do. It is an especially exciting release for me personally, as it now permits each of the following:
1. external event handlers
2. "flash" memory on setNextEvent() / setNextRoute()
3. internal support for Adam Fortuna's ColdCourse project
There are, however, a couple of "gotchas" that I wanted to pass along.
Oooops! I left out one little piece of important code with the original demo zip file. For those who downloaded it prior to about 11PM Eastern on Sunday night (12/16/07), you'll need this little snippet added to your form page so that it'll render properly in IE6 and below.
If you hadn't previously downloaded, the new zip file has the code plugged into the index.cfm file.
