|
Recent
Articles |
What Facebook ToS Change Means For Developers
Facebook pulled the wildly popular music sharing Audio one week after it changed its terms of service. While this is a good for Facebook, it does put limits on what developers can put up as an application. Venture...
.NET - Beware Of The FileInfo.OpenText() Method
I'm a big fan of the System.IO.FileInfo object in .NET because it wraps the System.IO.File object nicely in a strongly typed way.
It makes it easier to work with files. The FileInfo class has a method called OpenText...
Return Format For ColdFusion Components...
One of the lesser publicized updates in ColdFusion 8 is the introduction of the returnFormat attribute for the cffunction tag. What does this do? ColdFusion Components, when executed remotely, will return...
Return Format For ColdFusion Components...
One of the lesser publicized updates in ColdFusion 8 is the introduction of the returnFormat attribute for the cffunction tag. What does this do? ColdFusion Components, when executed remotely, will return data wrapped in WDDX format. This is a problem if...
Getting The Value Of AJAX-ified Controls
I ran into a problem last night trying to use JavaScript to read the value of a rich text field. I had assumed I could use the normal syntax I'd use for a form field: document.forms[0].body.value or document...
|
|
 |
|
08.16.07
ColdFusion 8's Ajax Debug Works Well With Spry
By Raymond Camden
Wow - this was a surprise. I was trying to debug a Spry issue this morning and not having any luck at all.
I was using Spry's debug panel which you enable like so:
On a whim I decided to see if ColdFusion 8's debug window would show me more information as I was banging my head against the wall trying to figure out the solution.
The first thing I did was to enable the Ajax debug console in the ColdFusion Admin.
I then went to my test page with ?cfdebug=1 in the URL, but nothing showed up.
Turns out that the ColdFusion debug window will not show up unless ColdFusion thinks you are actually using Ajax - it's own Ajax. While I think that is a mistake on Adobe's part - it is very easy to work around.
Todd Sharp made this suggestion - just add an empty cfajaximport to your page, like so:
This line by itself will trick the window into working.
Now at this point you can use the normal ColdFusion debug items - or even use the Spry debug commands. But to use Spry's debug stuff, you must enable Spry debugging, which means you will have two debug windows on screen.
What is cool is that ColdFusion's window picks up and displays the same Spry debug information as Spry does - and will even show a spry "group" that you can filter by.
Comments
About the Author:
Raymond Camden, ray@camdenfamily.com
http://ray.camdenfamily.com
Raymond Camden is Vice President of Technology for roundpeg, Inc. A long
time ColdFusion user, Raymond has worked on numerous ColdFusion books
and is the creator of many of the most popular ColdFusion community web
sites. He is an Adobe Community Expert, user group manager, and the
proud father of three little bundles of joy.
|
