Short of finding a full debugging tool for IE (VS.NET or VWD supply this but may not work well for your project) or creating your own robust object inspector, I'd say simply serializing your object like that in JSON is about the quickest way to get the debug info you really need.

On 8/14/06, Sam <[EMAIL PROTECTED]> wrote:
I have code and objects which work great in Firefox, and blow up in IE.  I don't have an object inspector in IE comparable to Firefox's Firebug and am contemplating finding a function call to layout an object in text format so I could read it from my own debug console.
 
I'm considering using a function to convert the object to JSON for display.
 
What other solutions might be better?
 
Sam
 

_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs



_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs

Reply via email to