It’s hard to believe, but this year’s CFUnited will be the last. I had a chance to attend CFUnited a few years ago and found it to be fun and inspiring.
I urge my fellow ColdFusion developers to take advantage of CFUnited this year (while it’s..sniff…still here). As always the speaker and topic lineup is top notch.
I’m working on generating PDF reports in ColdFusion 8 using the quick and easy cfdocument tag, and discovered that I cannot open and close tables using cfdocumentitem headers and footers. Here’s what I would have liked to do…
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | <cfdocument attributecollection="#cfdocAttributes#"> <cfdocumentitem type="header"> <table border="5"> <tr> <th>ID</th> <th>Name</th> </tr> </cfdocumentitem> <cfdocumentitem type="footer"> </table> </cfdocumentitem> <cfoutput query="qPeople"> <tr> <td>#ID#</td> <td>#Name#</td> </tr> </cfoutput> </cfdocument> |
Apparently there is a work-around for this if one is using Open BlueDragon. If anyone out there has a ColdFusion 8 solution that they’d care to share I would appreciate it…and apparently so would fellow CF developer Renu Deshpande.
I’ve been immersed in a world filled with Model-Glue Framework, Oracle 10g and YUI since June and am loving every minute of it. One of my goals for 2010 is to dust off this blog and resume contributing to the developer community. See you next year!
Sean Cornfield posted a request for opinions regarding cfmail and cfquery support in ColdFusion 9. I suggested that they name the functions “writeMail” and “writeQuery” (to stick with the convention of the existing “writeOutput” and upcoming “writeLog” functions), and like the idea of the email and query bodies being attributes of their respective functions.
Why in the world would anyone want to take one line of code…
1 | <cfset variables.Gouda = "" /> |
and turn it into three?
1 2 3 | <cfscript> variables.Gouda = ""; </cfscript> |
ColdFusion developers have been getting by just fine without using cfscript for quite some time. Some prefer old-school CF syntax to cfscript. It’s true that cfscript cannot do everything that ColdFusion can do*. There are some situations where avoiding cfscript is the best path.
First an analyst at Gartner reaffirmed what I already knew, then I read that there are 750K ColdFusion developers out there (wow!) and then I read Ray’s post about all of the new goodies in ColdFusion 9, one of which is “full language support for CFSCRIPT”. This is indeed a good week for ColdFusion!
If you want to add a rich text editor to your forms in ColdFusion 8 it’s as easy as CFTEXTAREA richtext=”true”…
My associate Ryan is hiring a Senior ColdFusion Developer. I had a chance to meet Ryan and the team recently to discuss what they are working on and I can assure you that the work is exciting and that the team is friendly and supportive.
If you don’t know what an Application.cfc file is or how to use it I suggest that you start with this
excellent Application.cfc Tutorial & Reference over at Ben Nadel’s blog.
There are number of approaches for managing environment-specific variables for your applications. One is to store them into an external XML file. I would imagine that there is an increased processor overhead associated with this path (it may be marginal), and there is the extra code of parsing the XML data to get your variables. One approach that’s worked well for me is to define the variables for each of my applications environments in a function in my Application.cfc files. This function detects which environment it’s being run in and sets the variables accordingly. Peep this out…
Word up, dawgs? Consider the following code…