So,
In other words,
If you have yet to use this remarkable tag, do so, quickly. But one point to keep in mind,
So,
In other words,
If you have yet to use this remarkable tag, do so, quickly. But one point to keep in mind,
The label= attribute is very useful too so you can annotate the dump output:
[cfdump label="session scope before call to foo()" var="#session#"]
[cfset foo()]
[cfdump label="session scope after call to foo()" var="#session#"]
I just wish that cfdump’s output displayed better then using a standards complient html doctype. I have found that I use the coloration of the cells of the output. Other then that cfdump rocks!
Is there a particular reason that the CSS for the object type is white text?
Most pages I work with I have a white background, and I can never see the object type unless I highlight the the page’s text. I’ve heard about ways to make it change, but its my understanding that they entail making changes that aren’t allowed under the CF license.
yeah ive been wondering why they encrypted the code for cfdump and a few other things.
a tool you can customize to suit your needs is a much better tool.
FYI, you can get a modified version of cfdump here:
http://www.camdenfamily.com/morpheus/blog/index.cfm?mode=entry&entry=395FBDF1-B095-E6F0-1C0D45520E77684D
It allows you to dump an array or query and display only the top N items. You can also filter by columns or struct keys.
Thanks Raymond, I’ll take a look at it.
Is there any better way to dump CFC objects? Dumping an object only shows the methods in it, is there any way to display member variables as well (i.e. those defined outside of a method)? (or if there is I’ve completely missed it)
Ben, I have a doubt here:
Do you remember that in the CF 5 the cfdump tag doesn’t works with the scope variables?
I remember that I had to make some modifications to dump my crated variables because it doesn’t work.
Was it a bug?
Regards,
Marcos Placoná
Marcos, in earlier versions of CF the scopes were not structures, but now they all are.
On the cell coloration, the tag does not put a # in front of the color numbers. Adding that character to the color fixes the problem in IE.
The tag would be easy to fix…if it weren’t encrypted. I guess MM changed their mind, since an earlier blog entry indicated they were not.
Leave a Reply