Wonders of CFChart
I just have to say that I'm loving ColdFusion more and more every day. I've been working on a charting application using CF's CFCHART tag, and by golly that's some sexy stuff. If you've never messed with, do...
It's possible to create either PNG or Flash charts with one simple tag. You can even build drill down pages to get more detail as you go. I'm hoping to have a demo of the charting app I'm working on and running in about a week :).
Just to get your rolling, here's a simple code block for building a chart:
<cfchart format="png" chartheight="300" chartwidth="400"> <cfchartseries type="bar" seriescolor="##003366" serieslabel="ColdFusion"> <cfchartdata item="Nov Cool Factor" value="50"> <cfchartdata item="Dec Cool Factor" value="75"> <cfchartdata item="Jan Cool Factor" value="100"> </cfchartseries> <cfchartseries type="bar" seriescolor="##FFFFCC" serieslabel="ASP VBScript"> <cfchartdata item="Nov Cool Factor" value="100"> <cfchartdata item="Dec Cool Factor" value="75"> <cfchartdata item="Jan Cool Factor" value="50"> </cfchartseries> </cfchart>
This chart plainly shows the affect of ColdFusion on ASP VBScript's cool factor.
ColdFusion Scheduled Tasks
If you're running your own CF server, or are hosting with a host who's willing to do a little extra work for you, you're going to love ColdFusion scheduled tasks. It's basically a way to tell CF to run a particular file at a set interval. The called file can run a report, update a database, do an XML grab, anything you want. And then you can tell CF that you want it to save the results of the file somewhere else.
I used this to great effect today, hence my post :). MM.com changed their DesDev feed, so the XSL I slaved over in VBScript wasn't doing the trick for me, and I didn't feel like writing a new one :). So I built a CF page to consume the XML feed and do it's wonders. Well that's all fine and good, but DWfaq is built in asp, so I couldn't call the CF page from my ASP application files. Scheduled tasks to the rescue :D
I set up a scheduled task to run my des dev parser once every 4 hours. When the parser runs it saves the result as a plain old HTML file which I can then include into my .asp pages. This means I don't have to parse the XML feed everytime someone hits my site, and I don't even have to worry about the MM server not being responsive but once every 4 hours (a pretty decent gamble given that I'm error checking things anyway).
The moral of the story? Scheduled tasks can make it easy to stash pages that don't change very often as static HTML files which you can then use throughout your application without worrying about your page overhead. Definitely tasty...
Certified again
I took the Dreamweaver MX 2004 certification this morning, and I'm now certified again. I only scored 88% this time, but then again I finished the 90 minute test in 20, had a client meeting I had to get to (I'm blaming poor scheduling on my part).